Shankar Vaidyanathan - VC++ IDE: Past, Present and Future
- Posted: Jul 31, 2006 at 2:41 PM
- 29,074 Views
- 12 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Tell me the reason that why c++ programmers should move from 2003 to 2005? As a matter of fact, there are still few people use VS 2005 or write C++/CLI code...So, I prefer VS 2003 or VS6...that's my choice.
Even if you do not use C++/CLI, VC++ 2005 compiler is much better
than VC6 compiler. Language support is better, preprocessor is
better, IDE is richer... So far the only code I could not compile with
VC++ 2005 is some forward template declaration. But it's ok. I have heard some people would like to see this feature removed from the language (although unlikely).
Just because .NET 2.0 was hyped doesn't mean VS is all managed now. VC++ is still good for unmanaged C++. I am the coder on a halflife2 mod and the mod is of course unmanaged. We used to use VS2003 ... and VS2005 is soooooo much nicer. Lot's faster, better intellisense, doesn't take forever to start up, etc.
Well... I don't mean that I hate VS2005. I know there are really a lot of improvements and exciting features...but anyway, i think for pure c++ programmers, that's really a difficult choice, to be pure c++ or CLI, I even don't know whether it's worthy to learn C++/CLI, how long will it last for? Just like managed c++?? Who knows.
What mod do you work on?
VC++ 2005 is the latest and greatest incarnation of VC++... It does not require C++ developers to write CLI-based code, however it makes it a hell of of lot more logical and easy to do should your aplication require interoperation with managed libraries, which will most likely increase with future iterations of Windows...
Managed code is not a fad, it's the future, but umanaged code will not go away and will continue to play an important role in application development for the forseeable future...
It's all about using the right tools to get your job done. Sometimes you may need both managed and unmanaged in your application. VC++ 2005 makes it easy to do so. It does not in any way require that you do so. I hope this is clear.
C
Hit the nail right on the head there!
I think the IDE support for C++/CLI is a little weak in comparison to C#'s support, but that's likely due to the greater complication in the C++ language and the fact that C++/CLI is not the preferred development environment of those who want a lot of tool support.
- Due to the runtime checks in the debug build (similiar to stlport debug mode) I found a really stupid bug (wells its only a private fun project)
- the whole source code intellisense thing is top notch (but it always was good)
- the debugger hoover over symbol and popup-with-expandable-content thing is very cool
- ide looks extremeley polished (at the begin I thought too polished), the colours are nice (classes and folders).
I dislike the whole msvcrt8 thing (manifest etc).
If I compare this software with eclipse ... just start eclipse on win32, navigate to Window> Show View list and check out how many entries have the navigation (not ide keyboard) shortcut P -> Package Explorer, Problems, Progress and Properties all use the P key. Well, unfortunately I have only "p" key on my keyboard. And of course there is no default ide keyboard shortcut for Problems (Is nobody missing this?). Which means when my compilation fails, I cannot use Alt-W+V+P to access the problems, but I have to use Alt-W+V+(n x P), which is annoying. Come on, my build fails, give me a default keyboard shortcut to jump to the first error!
Weird...
It makes my IDE really slow, I would rather disable it and use some 3rd patry tools.
Remove this comment
Remove this thread
close