다음을 통해 공유

More bugs to comment on

  • 아티클

From Martin: When we work on an ASP.Net project that is kept under Source Control
(VSS), occasionally you lose the IDE from the taskbar if you minimize the IDE. Oh
sure, the button is sitting right there, but you can't Alt-Tab to get it back up.
Right clicking the taskbar button won't give you a menu. The only way to get back
in is to use the Task Manager and do a "Switch To" in the applications tab.

This should be fixed in 2003.  I haven't seen it happen since then and we did
some wrk to remove the old code that was causing this that was there to support an
older window management model. If anyone still sees this I'd like to hear your repro
cases.   Your proxy settings should have nothing to do with this.  

Travis complained more about our "Abuse" of users HTML code.  My comment remains
the same. We are working to reduce/remove this in whidbey.  Sorry I don't have
a better answer.  I agree. I use frontpage/notpad to do HTML work. :-)

Nicole has Issues with the Task List:

A couple of other
task list ones (beside the lack of TODO display across the whole project): 1. No option (or at least none that I've found) for showing all tasks (or whatever
subset one might prefer) by default. 2. When double-clicking a task (user-defined or compiler error/warning) to navigate
to the associated line, if the line is in a collapsed region, the region is not expanded.
One "lands" on the collapsed region definition rather than the target line. This is
particularly annoying when working with long regions and/or nested regions.

We are doing some work around this soon in whidbey and I'll send your comments along
to our PM. I'll try to ensure I let you know what happens here.  Thanks!

And from Kiwi: Provide a history of command line parameters
in the Debugging category of project properties. There's a combobox now, but it expands
to one-item list wih 'Edit...'. I frequently run command-line apps with few sets of
paramters, and have to retype it all the time.

I sent this along to the debugger team. I'll let you know their response. 

This request yeilded a bunch more reponses than I anticipated and I appreciate you
all for taking the time.  I can also let you know that we are working to make
reporting bugs to our teams much easier in the future.  :-) 

Thanks,

josh

Comments

  • Anonymous
    September 26, 2003
    Over on WindowsForms.Net, they have a forum dedicated to a wishlist. It would be nice to see more of these, for the different aspects of the managed code world (the CLR, BCL, VS.Net, ...).
  • Anonymous
    September 26, 2003
    Ok, this post happened to be immediatly after yours... and it doesn't seem that it would be undoable:http://blogs.gotdotnet.com/craigs/commentview.aspx/91d30cde-e495-4f75-b8bb-0c4521467503What do you think? Doable or not?
  • Anonymous
    September 26, 2003
    It's software, anything is possible and it's a neat request to send over the Language Runtime people. I don't see us supporting this senario in VS officially in the near future. The is currently a debate about what percentage of customers even do mixed language solutions, let alone mixed language code files. I'll also put my testing hat on for a second and say. "Wow, looks cool, but you better give me a lot more QA heads to test it. :-) "
  • Anonymous
    September 26, 2003
    Remember that when I say something like "I don't see us supporting this senario in VS officially in the near future." thats IMO and not to be taken as the official Visual Studio product team statement. I just think it's unlikely. :-)
  • Anonymous
    September 26, 2003
    I'm not too interested in cross language source files. I'm more interested in a library capability. Right now, I have a code file sitting in the root of the VS Projects folder that has snippets that I tend to add to every project. I add a copy of that file to new projects and then modify it as needed.The biggest thing is that I can never seem to remember the exact syntax to use in a connection string. (I always end up doing a Dim X As New SqlConnection("") and then later fill in the right string, usually after trying to run the project once).
  • Anonymous
    September 26, 2003
    Two pet peeves for me. Working in VB.NET all the time I've noticed numerous times when I will select a form file in the Solution Explorer and the button bar in the Solution Explorer will go blank. Since I typically select the form and hit the show code button it's gotten quite annoying. Now I'm just getting in then habit of right-clicking the file and selecting show code but I'd much rather hit the button. I don't remember if I've seen it happen in 2003 but it happened all the time in 2002.Sometimes when I right-click References in the Solution Explorer and select Add Reference - nothing happens. I've discoved that I can fix it by selecting Tools/Add In Manager and then hitting Cancel on the manager window. After that Add Reference works. This happens often enough to be quite annoying. I had hoped 2003 fixed it but I still encounter it quite often. I'm sure I'd see it even more often if I added refereneces a lot - seems like most of the times I've had to add a reference it does this.If you aren't aware of either of these I will try to come up with a repro case for you - they are intermittent problems but I might be able to repro them reliably if I really tried.Great Blog, by the way.
  • Anonymous
    September 26, 2003
    Steve: I can't seem to get iether of these to repro here with 2003. If you have a machine where these happen consistently let me know what the steps are and give m some more information about the machine so i can try some more. I may also be able set up a remote debugging session on your machine if you'd like a deeper look. josh