Recently Kate Gregory (VC++ MVP), Ale Contenti (Dev Lead VC++) and Steve Teixeira (GPM VC++) attended TechEd Europe and presented sessions on VC++ (what else?) During a break in proceedings Charles Torre (Channel 9) caught up with all three in a speaker’s lounge and asked how the VC++ community was reacting to VC++ 2008, the upcoming MFC/TR1 release and the TechEd sessions. The interview also touched on the VC++ strategy and direction moving forward and, as always, our MVP provided some real world experiences and feedback - actually the input from our MVPs is an amazing asset for all the MS Product Units – a direct link to many of our valued customers. We hope you enjoy the video.
PingBack from http://www.absolutely-people-search.info/?p=253
We regularly port C++ scientific code using Visual Studio. Can you make this easier to do? The code is usually from unix/makefiles with many things that do not compile under VC++. Some examples,
a) #include <abc.h> instead of #include "abc" for non-system include files.
b) putting a space between the '#' and 'ifdef' so that preprocessor directives can be indented.
c) linking in the CRT / C++ iostream classes multiple times (in a library) resulting in duplicate symbol linker errors. Can VS just recognize that the same function is being linked in and ignore the duplicates?
d) relying on autoconfig / configure to handle platform differences (a big big pain for us)
e) relying on non-posix API calls (e.g., truncate() to set a file's length).
Helping us with even one of the above problems would be great.
A refactor method to push local variables to their innermost scope would help greatly.
We'd use this, followed by a refactor to extract the immermost block to a new method.
Bob, I've been porting code between platforms for 30+ years now. Programmers need to learn to program, and not expect the tools to do everything.
There's a reason for a).
There's a reason NOT to allow b).
c) - Look into include guards (or #pragma once).
And if porting is a big issue, look into Lint, which will astound you with the portability problems it can find in "good" code.
b) Whitespace between '#' and 'ifdef' (or other directive is not a problem in MSVC, and hasn't been since at least Visual Studio 6.
e) for relying on unimplemented APIs, you may want to find or come up with a porting library. For things like truncate(), this would be easy, but clearly depending on what APIs you need to have ported the effort may be too large.
• Currently VC++ has no IDE support in Visual Studio for programming these CLR technologies (why???):
• 1) ASP .NET
• 2) WPF
• 3) WCF
• 4) LINQ
while of course C# supports all of them. Clearly you, and Microsoft, could support all of these using C++/CLI in pure/safe mode modules.
If you are not interested in supporting .NET, and just ceding .NET development to C#, just drop C++/CLI and stop pretending that you are creating a level field for all .NET languages.
• What is the real reason of releasing the only Web library ATL Server on CodePlex.com? Is it to hard to ingrate some of sophisticated web components like in ASP. NET to make our only C++ Web library ATL Server web developpement easy to use?
• MFC will support BCG controls bar but it is only for desktop application and not for web application.
• Can we built 3-tiers application entirely in VC++?
You did an excellent job of creating a first class .NET language with C++/CLI and you have done a general good job in interoperating between C++/CLI and standard C++, but you have done a terrible job of bringing .NET technologies to C++/CLI.
• I would want to say that [url]www.hotmail.com[/url] still use *.srf web page to open connection in the mail box. And *.srf pages are built using ATL Server technology. It 's the same for .NET passeport web pages. Can you explain this?
• With Silverlight 1.1 we can build interaction web application using C# or VB .NET with the .NEt Framework and C++/CLI is not a .NET language?
• Is ASP .NET only for C# and VB.NET? But it is not all of .NET language?
• Can you explain the real Visual C++ Futures?
WHAT VISUAL C++ 2008 LIBRARY THAT TARGETS THE WEB?
WHAT VISUAL C++ 2008 TOOLS THAT TARGETS WPF?
WHAT VISUAL C++ 2008 TOOLS THAT TARGETS WCF?
WHAT VISUAL C++ 2008 TOOLS THAT TARGETS LINQ?
WHAT VISUAL C++ 2008 TOOLS THAT TARGETS ASP. NET?
WHAT VISUAL C++ 2008 TOOLS THAT TARGETS SILVERLIGHT?
WHAT KIND OF VISSUAL STUDIO 2008 WITH VISUAL C++ INSIDE MICROSOFT WOULD GIVE US?
WHAT ABOUT THE FUTUR OF VISUAL C++?
Most of your questions refer to the development of web applications. The VC++ team made the explicit decision not to focus on web apps as a target application type. VC++ is focused at systems software, native rich-client softare, and multi-platform code bases.
The focus of the C++/CLI language binding is to serve as the interop layer between native and managed code. Most (but admittedly not all) VC++ customers elect to write their managed code in C#, so VC++ embraces this fact and chooses to invest more heavily in native code support rather than providing "me too" features to maintain .NET feature parity with C#. You'll find a lot of discussion on this topic (and a multitude of other topics) in the thread following Soma's "VC++ Futures" blog entry: .http://blogs.msdn.com/somasegar/archive/2007/08/08/visual-c-futures.aspx