Earlier this week Soma, Vice President for the Microsoft Developer Division, blogged about the future of Visual C++. Please check out what he has to say and feel free to leave comments for him on our strategy. You can check out his blog at http://blogs.msdn.com/somasegar/archive/2007/08/08/visual-c-futures.aspx.
The Visual C++ Development Team
THAT IS SO SNEAKY!
I thought you were talking about http://video.google.com/videoplay?docid=7625918717318948700
Sorry...there was no intent to confuse people! What we hear from customers all the time is "tell me your future plans". Hence the title of the blog post. Note that we are very interested in "C++ Futures" but we have no information to share on that as yet...
Visual C++ Development Team
FYI: there are currently about 190 comments/replies to Soma’s “Visual C++ Futures” blog post. It is fascinating reading – describing, often in great detail, what our users love and hate about VC++, and all manner of suggestions for what we should do to add value to the product in the future. Feel free to add your voice to any of the suggestions already on Soma’s blog or, of course, add your own.
There is a bug in VC Orcas that seems to prevent the use of VC for database development.
Visual Studio 2008 Orcas Beta 2 will not add a datasource in C++. (Menu Item: Data->Add New Data Source->Choose Data Type shows only object not database as this same item does in C# Orcas Beta 2).Microsoft admits that this is a "bug by design". See the following response from Microsoft to a person who first submitted this bug
Thank you for taking the time to report this. The issue you are reporting is By Design.
Visual Studio 2008 does not support adding new data sources (database or webservice) to Visual C++ projects anymore. Due to VC's changes in focus and strategy in Orcas and going forward and our resources availability to maintain Data Designer integration, we decided to reduce our support for this feature.
Projects created with Visual C++ 2005 that contain data sources will continue to work as expected as there are no breaking changes in the editor or the build system.
Thank you for understanding,
Visual C++ IDE
Posted by Microsoft on 8/14/2007 at 6:30 PM
Where does this leave their long term committment to C++?
Many good features of VC++6 are missing in the newer versions of VS, including VS2005, such as (1) Cannot use debugger to examine the content of each class array element (e.g., class matrix A(10,10), then debugger cannot see A(0,1), A(1,1), ...); (2) More difficult to customize the editor (now it is very difficult to customize the editor and many customizable features of VC++6 are gone); (3) Very difficult to activate the Watch 2, Watch 3 in debugging window. People can list more ......
Lloyd Martin wrote:
"Microsoft admits that this is a "bug by design". […] Where does this leave their long term committment to C++?"
So firstly, on this particular case, just to be clear - we did not say this was a “bug by design” – we are saying that this is “by design” and therefore not a “bug”. Secondly, we have not removed this functionality from our C++ project system per se, rather we have removed a wizard that auto-generates this code from within the IDE - you can of course still wire it by hand yourself, which is clearly more work but no loss of capability.
However on the far more important macro-level, the work we’ve done for Orcas and the work we’re planning for Orcas+1 is a good measure of our team's commitment to C++. Our strategy around driving Visual C++ forward is described in Soma's post referred above and also in more detail in Steve Teixeira and Bill Dunlap's Channel 9 video.
The decision of reducing support for Data Designer was driven by this change in strategy. Our desire was to allocate resources going forward on higher priority and higher value workitems – such as the native Libraries improvements or the new Intellisense support. It is known that all existing features come with a cost (design cost, bug fixing and test cost). Removing Data Designer was a difficult decision on our side, but mitigating factors were the limited adoption of the Data Designer in VC++ and the availability of a state-of-art Data Designer integration in languages like C# and VB.
We do however want to be very clear and honest about a few facts:
1) The Visual C++ IDE is not competing with Visual C# or Visual Basic IDEs in the .NET Framework development space. C# and VB will continue to provide great innovations in .NET (consider LINQ as one such example) which won’t be mirrored in Visual C++. Visual C++, on the other hand, will focus on providing a great experience for native code development and native/.NET Interop development which is where the vast majority of our customers have asked us to center our efforts
2) From time to time we will unfortunately have to remove some functionality from Visual C++ to allow us to concentrate our resources on workitems more fundamental to our central goal of providing an unparalleled native development experience to our customers. When this happens we will try and notify customers as soon as possible of the situation and provide alternatives as best as we can.