Very very annoying
-
I just noticed this with VS.NET 2003... Can't remember if it happened with 2002... Don't think it did. Basically.. if you minimise all the open windows with "Windows Key + D" and then if you click on the taskbar to restore any particular window [except VS.NET 2003] VS.NET will always pop-up as well. Has anybody else experienced this???... It's damn annoying... ok... I just tested it and it also happens when I use the "Show Desktop" button in the quick launch tray... One of my colleagues just tested it here and he has the same problem... VS.NET doesn't grab focus or anything but it's still annoying. Is this a "feature" of VS.NET??? ... if it is, it's a damn annoying one!!! Other than that, I don't have any complaints about VS.NET 2003... <edit> Happens on my another machine too. Both Windows 2000 [SP3] and VS.NET 2003. </edit> Regards, Brian Dela :-)
-
I just noticed this with VS.NET 2003... Can't remember if it happened with 2002... Don't think it did. Basically.. if you minimise all the open windows with "Windows Key + D" and then if you click on the taskbar to restore any particular window [except VS.NET 2003] VS.NET will always pop-up as well. Has anybody else experienced this???... It's damn annoying... ok... I just tested it and it also happens when I use the "Show Desktop" button in the quick launch tray... One of my colleagues just tested it here and he has the same problem... VS.NET doesn't grab focus or anything but it's still annoying. Is this a "feature" of VS.NET??? ... if it is, it's a damn annoying one!!! Other than that, I don't have any complaints about VS.NET 2003... <edit> Happens on my another machine too. Both Windows 2000 [SP3] and VS.NET 2003. </edit> Regards, Brian Dela :-)
I'm not aware of such a feature in VS 2003, though I'm not on the VS team. I've tried reproducing it on Windows XP Professional Service Pack 1, and I'm not seeing the behavior you are describing. I've tried both while in design mode and debugging. I'm just guessing, but this sounds like it might be more related to OS version or settings than VS itself. For example, a potentailly related issue oddity in Windows 2000 Professional is described in http://support.microsoft.com/default.aspx?scid=kb;en-us;262088 [^] Burt Harris
-
I'm not aware of such a feature in VS 2003, though I'm not on the VS team. I've tried reproducing it on Windows XP Professional Service Pack 1, and I'm not seeing the behavior you are describing. I've tried both while in design mode and debugging. I'm just guessing, but this sounds like it might be more related to OS version or settings than VS itself. For example, a potentailly related issue oddity in Windows 2000 Professional is described in http://support.microsoft.com/default.aspx?scid=kb;en-us;262088 [^] Burt Harris
Happens on my another machine too. Both Windows 2000 [SP3] and VS.NET 2003. I've fooled around with all the settings I can think of but it's still nodifferen. Thanks for the info anyway. Regards, Brian Dela :-)
-
I'm not aware of such a feature in VS 2003, though I'm not on the VS team. I've tried reproducing it on Windows XP Professional Service Pack 1, and I'm not seeing the behavior you are describing. I've tried both while in design mode and debugging. I'm just guessing, but this sounds like it might be more related to OS version or settings than VS itself. For example, a potentailly related issue oddity in Windows 2000 Professional is described in http://support.microsoft.com/default.aspx?scid=kb;en-us;262088 [^] Burt Harris
Burt, could you kindly reply to my post below on whether Windows 2003 Server is included in the Enterprise Developer edition of VS.Net 2003? I have purchased VS.Net Professional 2003 (upgrade from 2002). My only interest in the Enterprise Developer version is: (a) Windows 2003, including the 64-bit version when it is released (b) SQL Server 2000 I would appreciate your response. Thanks, Robert