Is this bug going to be fixed anytime soon
Using VC++ Express 2005 v8.0.50215.44 (beta2.050215-4400) and .NET Framework v2.0.50215 on a Win2K SP4 test box.
I've tried the solutions from both Boris and Chaos to workaround the problem and neither appear to work.
I've been charged with evaluating VC++ for our enterprise, ( I'm principally a gcc user), and a rudimentary bug like this ought to get squashed pretty quick IMO.
[EDIT]
OOPS! Sorry to start this as a new thread. Meant to reply to the existing one.
Set VC++ Directories in Options dialog (Visual C++ Express)
Hot Topic
- SAPI: How to specify training text?
- Plz help ,hoe to make coloured scrollbars in a MDI application in VC++ 6
- 2d array delete problem and question
- Can we get to the bottom of this.
- error LNK2005: "void __cdecl bp5(void)" (?bp5@@YAXXZ) already defined in test.obj
- Indenter etc. for VC++ 2003
- About my screen shot
- Turning off beep?
- using ATL macro to change LPSTR to LPCWSTR
- Vector data corrputed
Visual C++
- newbie question: Migrating from MSVC5.0 to actual Visual C++ 2005 Express Edition
- MCF and Framework .NET
- STL.NET serialization
- my win32 api app build in studio 2005 couldnt run in other computer..
- Nameless namespaces in c++ 8.
- unresolved tokens when migrating from 2003 to 2005
- _CRT_SECURE_NO_DEPRECATE doens't eliminate warning related "strnicmp"
- Memory leak in the STL list class
- Need syntax examples and info for the super set of C++ (managed C++/CLI)
- setting compiler options programmatically.
Set VC++ Directories in Options dialog (Visual C++ Express)
Marlund
magoria
That is what I tried. The details are in those posts...
Since the bug has been squashed and will not be an issue in the next (hopefully) version release, it seems rather pointless to pursue this.To be frank, I simply don't have the time to detail everything I tried and the "workaround" will no longer be necessary anyway. Thanks for the replies. I'll wait until the product becomes an "install and go" package...
ebaklund
Just to be clear, the bug was fixed ages ago on our side, it's just not reflected in Beta 2, which you are using. Perhaps you can access a version of Visual Studio via MSDN instead of using the Express edition and thus get newer bits. On the other hand, I'd like to understand why the workarounds are not working for you, can you tell me more
Thanks,