NickThissen
Nov 10th, 2009, 02:23 PM
Hey,
I have installed Visual Studio 2008 Professional on Windows 7 (beta) a while ago, and after going back to my XP (dual boot) for a while, I'm now back on 7.
I notice now that Visual Studio appears to behave a little differently as it does on XP (although I don't think that is part of the issue).
The difference is that in XP, I am sure my Visual Studio used a 'background compiler' (not sure how to call it) when I was working in C# projects. When I make a typo, it would highlight it as an error as soon as I moved to a different line.
Now however, on Windows 7, it doesn't do that anymore. It only lists the error after I try to build the solution. This is really annoying as I tend to make a lot of typos, and I am used to VB.NET where those errors are also instantly noticed. Now, when I try to debug, I will find myself fixing typos for 5 minutes first, because I simply missed them while typing.
It also does this the other way around: when I'm fixing typos, it still lists them as an error even though I already fixed it. I need to rebuild for it to 'catch up'. So it's very hard for me to see quickly which typo's I've fixed already and which I haven't. So that often takes a few builds before I get them all.
Another thing (nit-picking here) is the Output window. I've never even seen it on the XP installation of VS. But now when I build the solution, it comes up (only when working in a C# project, not in a VB project) and for some reason always on top of the Error List. It shows some compile information probably. I think this is really annoying as I like to watch the error list while building so I can quickly see if an error occured or not. Granted, whenever an error does occur, it seems that the Error List window gets 'priority' and jumps in front of the Output window, but the Output window is still behind it. I know, the Output window can tell me probably more about the compilation than the Error List window, but it's just what I'm used to and it's a little annoying now :)
I tried simply closing it, but it just re-opens when I build. I tried checking it in the View menu, but it seems it doesn't work as a checked item but simply opens the window. How do I get it to stop showing?
I was wondering perhaps this has to do with the very first setting you have to specify when you start Visual Studio for the first time? The one where you choose to be a Visual Basic developer, or C# developer, or web, or General developer. I can't remember which I've picked on both installs... Can I change that now?
Or if that's not it, perhaps I installed some add-on that does this? I am pretty sure I'm only using Coderush Express on XP, but not (yet) on Windows 7, but I think that is not the cause for the background compiling in C# in the XP install; I'm pretty sure it did that before installing that.
How do I 'enable' this on my Windows 7 install? I like to think of myself as finally getting more and more knowledgeable of the awesome features Visual Studio has to offer, but somehow I can't figure out why I'm getting different behavior on two installs here...
Thanks!
I have installed Visual Studio 2008 Professional on Windows 7 (beta) a while ago, and after going back to my XP (dual boot) for a while, I'm now back on 7.
I notice now that Visual Studio appears to behave a little differently as it does on XP (although I don't think that is part of the issue).
The difference is that in XP, I am sure my Visual Studio used a 'background compiler' (not sure how to call it) when I was working in C# projects. When I make a typo, it would highlight it as an error as soon as I moved to a different line.
Now however, on Windows 7, it doesn't do that anymore. It only lists the error after I try to build the solution. This is really annoying as I tend to make a lot of typos, and I am used to VB.NET where those errors are also instantly noticed. Now, when I try to debug, I will find myself fixing typos for 5 minutes first, because I simply missed them while typing.
It also does this the other way around: when I'm fixing typos, it still lists them as an error even though I already fixed it. I need to rebuild for it to 'catch up'. So it's very hard for me to see quickly which typo's I've fixed already and which I haven't. So that often takes a few builds before I get them all.
Another thing (nit-picking here) is the Output window. I've never even seen it on the XP installation of VS. But now when I build the solution, it comes up (only when working in a C# project, not in a VB project) and for some reason always on top of the Error List. It shows some compile information probably. I think this is really annoying as I like to watch the error list while building so I can quickly see if an error occured or not. Granted, whenever an error does occur, it seems that the Error List window gets 'priority' and jumps in front of the Output window, but the Output window is still behind it. I know, the Output window can tell me probably more about the compilation than the Error List window, but it's just what I'm used to and it's a little annoying now :)
I tried simply closing it, but it just re-opens when I build. I tried checking it in the View menu, but it seems it doesn't work as a checked item but simply opens the window. How do I get it to stop showing?
I was wondering perhaps this has to do with the very first setting you have to specify when you start Visual Studio for the first time? The one where you choose to be a Visual Basic developer, or C# developer, or web, or General developer. I can't remember which I've picked on both installs... Can I change that now?
Or if that's not it, perhaps I installed some add-on that does this? I am pretty sure I'm only using Coderush Express on XP, but not (yet) on Windows 7, but I think that is not the cause for the background compiling in C# in the XP install; I'm pretty sure it did that before installing that.
How do I 'enable' this on my Windows 7 install? I like to think of myself as finally getting more and more knowledgeable of the awesome features Visual Studio has to offer, but somehow I can't figure out why I'm getting different behavior on two installs here...
Thanks!