Frustrated
-
<rant> So VS.NET 2003 will be coming out soon. Geez.. great. But what about all us users who have been stuck with VS.NET 2002 with all it's frustrating bugs for a year now? And the #1 bug that's been plaguing our project is the infamous VS.NET file locking bug: As soon as your DLL passes the magical 64kb mark, you get the "the file is locked by another process" error. Another process my #@$#@!!! And now, for the millionth's time since we started this project I have to either fork the project into artificially smaller project (man, I thought the days of 64kb limits were long behind us!) or add yet another utility project to do some voodoo file copying to get around the problem. I think this is irresponsible behavior on Microsoft's side. In the entire year that VS.NET has been on the market, only one patch (fixing only one bug) was released (and even that one was hard to find!). Now we'll be forced to upgrade to the new IDE (god knows what problems that will introduce) just because they didn't fix fundemental problems with the current release. Maybe someone from Microsofts hangs around the lounge and would like to tell me why it has to be this way? </rant> -Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC++ experience that much more comfortable...
-
<rant> So VS.NET 2003 will be coming out soon. Geez.. great. But what about all us users who have been stuck with VS.NET 2002 with all it's frustrating bugs for a year now? And the #1 bug that's been plaguing our project is the infamous VS.NET file locking bug: As soon as your DLL passes the magical 64kb mark, you get the "the file is locked by another process" error. Another process my #@$#@!!! And now, for the millionth's time since we started this project I have to either fork the project into artificially smaller project (man, I thought the days of 64kb limits were long behind us!) or add yet another utility project to do some voodoo file copying to get around the problem. I think this is irresponsible behavior on Microsoft's side. In the entire year that VS.NET has been on the market, only one patch (fixing only one bug) was released (and even that one was hard to find!). Now we'll be forced to upgrade to the new IDE (god knows what problems that will introduce) just because they didn't fix fundemental problems with the current release. Maybe someone from Microsofts hangs around the lounge and would like to tell me why it has to be this way? </rant> -Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC++ experience that much more comfortable...
I hope you cc'd Nick on this ;) cheers, Chris Maunder
-
<rant> So VS.NET 2003 will be coming out soon. Geez.. great. But what about all us users who have been stuck with VS.NET 2002 with all it's frustrating bugs for a year now? And the #1 bug that's been plaguing our project is the infamous VS.NET file locking bug: As soon as your DLL passes the magical 64kb mark, you get the "the file is locked by another process" error. Another process my #@$#@!!! And now, for the millionth's time since we started this project I have to either fork the project into artificially smaller project (man, I thought the days of 64kb limits were long behind us!) or add yet another utility project to do some voodoo file copying to get around the problem. I think this is irresponsible behavior on Microsoft's side. In the entire year that VS.NET has been on the market, only one patch (fixing only one bug) was released (and even that one was hard to find!). Now we'll be forced to upgrade to the new IDE (god knows what problems that will introduce) just because they didn't fix fundemental problems with the current release. Maybe someone from Microsofts hangs around the lounge and would like to tell me why it has to be this way? </rant> -Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC++ experience that much more comfortable...
Oz Solomonovich wrote: And the #1 bug that's been plaguing our project is the infamous VS.NET file locking bug: As soon as your DLL passes the magical 64kb mark, you get the "the file is locked by another process" error. Another process my #@$#@!!! I hate to send you into an even lengthier tirade - but where does this bug occur? Is it only with C++ projects? BTW: I love WndTabs! ;) -- Russell Morris "Have you gone mad Frink? Put down that science pole!"
-
<rant> So VS.NET 2003 will be coming out soon. Geez.. great. But what about all us users who have been stuck with VS.NET 2002 with all it's frustrating bugs for a year now? And the #1 bug that's been plaguing our project is the infamous VS.NET file locking bug: As soon as your DLL passes the magical 64kb mark, you get the "the file is locked by another process" error. Another process my #@$#@!!! And now, for the millionth's time since we started this project I have to either fork the project into artificially smaller project (man, I thought the days of 64kb limits were long behind us!) or add yet another utility project to do some voodoo file copying to get around the problem. I think this is irresponsible behavior on Microsoft's side. In the entire year that VS.NET has been on the market, only one patch (fixing only one bug) was released (and even that one was hard to find!). Now we'll be forced to upgrade to the new IDE (god knows what problems that will introduce) just because they didn't fix fundemental problems with the current release. Maybe someone from Microsofts hangs around the lounge and would like to tell me why it has to be this way? </rant> -Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC++ experience that much more comfortable...
Anyone know when VS.NET 2003 will be released? I'm really looking forward to the Compact Framework stuff.
-
I hope you cc'd Nick on this ;) cheers, Chris Maunder
No complaints to Nick - he's been doing an excellent job in moving VC++ along! I don't think he's related to the IDE team (though I wish he were...) -Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC++ experience that much more comfortable...
-
Oz Solomonovich wrote: And the #1 bug that's been plaguing our project is the infamous VS.NET file locking bug: As soon as your DLL passes the magical 64kb mark, you get the "the file is locked by another process" error. Another process my #@$#@!!! I hate to send you into an even lengthier tirade - but where does this bug occur? Is it only with C++ projects? BTW: I love WndTabs! ;) -- Russell Morris "Have you gone mad Frink? Put down that science pole!"
Russell Morris wrote: Is it only with C++ projects? I see it C# projects. With the way the C# projects work (and possibly VC.NET projects as well), the IDE has to copy the output DLL to two or three locations (even more if you have a lot of references), so the bug manifests itself more. I suspect that it would be more rare with VC++ project since there is less copying involved (read: I've never seen it in any of my VC++ projects). Russell Morris wrote: BTW: I love WndTabs! Thanks! --- Grab WndTabs from http://www.wndtabs.com to make your VC++ experience that much more comfortable...
-
Oz Solomonovich wrote: And the #1 bug that's been plaguing our project is the infamous VS.NET file locking bug: As soon as your DLL passes the magical 64kb mark, you get the "the file is locked by another process" error. Another process my #@$#@!!! I hate to send you into an even lengthier tirade - but where does this bug occur? Is it only with C++ projects? BTW: I love WndTabs! ;) -- Russell Morris "Have you gone mad Frink? Put down that science pole!"
Nope C# for me anyways. For every build I want to do I have first close VS.NET, then delete the obj directory, then reopen and build, but build will only build once, very fustrating. I now just made it a single project in a solution to cut down load/build times, then have it refenced in another VS.NET instance. I never knew it was a bug though, though it was just me, but it all makes sense now. Damn you MS for making me lose confidence in myself. ;P I rated this article 2 by mistake. It deserves more. I wanted to get to the second page... - vjedlicka 3:33 25 Nov '02
-
No complaints to Nick - he's been doing an excellent job in moving VC++ along! I don't think he's related to the IDE team (though I wish he were...) -Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC++ experience that much more comfortable...
Nick's pretty good at slapping those guys around though. I heard he made CodeProject feedback on VS.NET required reading for some of those guys! cheers, Chris Maunder
-
Anyone know when VS.NET 2003 will be released? I'm really looking forward to the Compact Framework stuff.
Real Soon Now®. cheers, Chris Maunder
-
Real Soon Now®. cheers, Chris Maunder
Chris Maunder wrote: Real Soon Now®. Is that in the eastern time zone, or that crazy mountain time? evilpen dot net
-
Chris Maunder wrote: Real Soon Now®. Is that in the eastern time zone, or that crazy mountain time? evilpen dot net
Kristopher wrote: crazy mountain time :D cheers, Chris Maunder
-
Chris Maunder wrote: Real Soon Now®. Is that in the eastern time zone, or that crazy mountain time? evilpen dot net
Kristopher wrote: Is that in the eastern time zone, or that crazy mountain time? It's in GRT (General Redmond Time) ¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)!
-
<rant> So VS.NET 2003 will be coming out soon. Geez.. great. But what about all us users who have been stuck with VS.NET 2002 with all it's frustrating bugs for a year now? And the #1 bug that's been plaguing our project is the infamous VS.NET file locking bug: As soon as your DLL passes the magical 64kb mark, you get the "the file is locked by another process" error. Another process my #@$#@!!! And now, for the millionth's time since we started this project I have to either fork the project into artificially smaller project (man, I thought the days of 64kb limits were long behind us!) or add yet another utility project to do some voodoo file copying to get around the problem. I think this is irresponsible behavior on Microsoft's side. In the entire year that VS.NET has been on the market, only one patch (fixing only one bug) was released (and even that one was hard to find!). Now we'll be forced to upgrade to the new IDE (god knows what problems that will introduce) just because they didn't fix fundemental problems with the current release. Maybe someone from Microsofts hangs around the lounge and would like to tell me why it has to be this way? </rant> -Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC++ experience that much more comfortable...
More of a turbo rant I thought :laugh: Elaine (fluffy tigress emoticon) The tigress is here :-D
-
Kristopher wrote: Is that in the eastern time zone, or that crazy mountain time? It's in GRT (General Redmond Time) ¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)!
Acording to Windows' Date/Time Properties, GRT is GMT +/- ∞ :~
David Wulff
"David Wulff can't live without me, so you shouldn't either" - Paul Watson
-
<rant> So VS.NET 2003 will be coming out soon. Geez.. great. But what about all us users who have been stuck with VS.NET 2002 with all it's frustrating bugs for a year now? And the #1 bug that's been plaguing our project is the infamous VS.NET file locking bug: As soon as your DLL passes the magical 64kb mark, you get the "the file is locked by another process" error. Another process my #@$#@!!! And now, for the millionth's time since we started this project I have to either fork the project into artificially smaller project (man, I thought the days of 64kb limits were long behind us!) or add yet another utility project to do some voodoo file copying to get around the problem. I think this is irresponsible behavior on Microsoft's side. In the entire year that VS.NET has been on the market, only one patch (fixing only one bug) was released (and even that one was hard to find!). Now we'll be forced to upgrade to the new IDE (god knows what problems that will introduce) just because they didn't fix fundemental problems with the current release. Maybe someone from Microsofts hangs around the lounge and would like to tell me why it has to be this way? </rant> -Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC++ experience that much more comfortable...
Oz Solomonovich wrote: Maybe someone from Microsofts hangs around the lounge and would like to tell me why it has to be this way? So you'll buy the 2003 version. Of course, those of us who don't like wasting time are sticking with VC6 until Microsoft fixes all the bugs and introduces new ones. Remember, bug fixes don't sell, only new features sell.
Through 86 years of perpetual motion, if he likes you he'll smile and he'll say, "Some of it's magic, some of it's tragic, but I had a good life all the way"