What are your thoughts on VS 2005, 2008 and the coming VS 2010? What's good, bad? Discuss.
-
I don't know about C++ but in general there are too many inconsistencies in behaviour between C# and VB, especially in the editor. C# integration is much smoother.
Kevin
Certainly, according to what i've heard about that it seems that msft guys are trying to dumb down VB's editor in comparison with that of C#, perhaps, to further force us developers to prefer one lang. over the other. :(
-
What got fixed, what should have been fixed? What's great and what's a disaster? What's your favorite version of VS? Honestly curious to know -- will be visiting MSFT last week and would like to take along some feedback. Witticisms welcomed but thoughtful answers are more helpful. thanks jeff
VS2008 SP1 C++. Whats bad: 1- Hit a breakpoint, change some code, introduce a typo, re-compile. Output window says there is an error but no indication of what or where. Click edit to fix the error, error list is empty. I have to stop debugging and re-compile to see the error in the output window. 2- Try to add a breakpoint, IDE indicates the edit code is different to the compiled code, even though a re-build all took place. Have to context select 'location' and 'allow code to differ' 3- Multithreaded debugging -known issue with multiple patches, none of which work. see MSDN-Visual Studio 2008 SP1 Stepping and Breakpoint Issues Whats Good: better experience than VS2003 and VS2005 after moving from VS6. I continued using VS6 after trying VS2003 and VS2005. Steve
-
What got fixed, what should have been fixed? What's great and what's a disaster? What's your favorite version of VS? Honestly curious to know -- will be visiting MSFT last week and would like to take along some feedback. Witticisms welcomed but thoughtful answers are more helpful. thanks jeff
I've developed C++ in VS 2005 SP1 and now using VS 2008 SP1 .I can say that Visual Studio 2005 was clumsy and slow , VS 2008 is way too much worse than Vs 2005. In every new version nothing but bugs and instabilities injected into Visual Studio. And C++ developers use VS because it's the currently the best one in C++ development( 3rd party tool like Visual AssistX,Incredibuild, debugging and etc..).But this doesn't mean Visual Studio gives C++ developers an IDE that satisfies current development necessities of a project. I'm watching Eclipse CDT and with a new version i see better integration and further progress in IDE. So if it continues like that i can say that future of C++ development seems like CDT. Microsoft has only one chance to change this and it's VS 2010.In VS C++ blogs, they promise VS 2010 will be good. We'll wait and see what's going to happen
[AGP]
-
What got fixed, what should have been fixed? What's great and what's a disaster? What's your favorite version of VS? Honestly curious to know -- will be visiting MSFT last week and would like to take along some feedback. Witticisms welcomed but thoughtful answers are more helpful. thanks jeff
I find that debugging in TFS unit testing after running starting the main program is problematic. I find that I either have to close VS2008 down and start over or bring up task manger and remove VsTestHost.exe then restart debugging my TFS unit test. I just need to remember that before debugging my unit tests, I cannot press F5, F10, or F11. What happens is that the test host starts up and the test goes to the pending state, but not to the inprogress state. I need to kill the test host application and re-run/debug the unit test.