Points for pjknibbs

Since I will be deleting the original question, here is the cut/paste to show the flow of events.
___________________________________________________________
From: lar_jens
 Hi there..
A guy at work just tried to create win32 project with Visual Studio .NET. The problem is, that studio
did not come up with anything. The wizard claimed that it would create a WinMain function, some header
and cpp files, but nothing happened.
I am considering the move from Visual Studio 6.0 to Visual Studio .NET, and I want to work with only
one studio, and continue to program in unmanaged Win32 C++. Does anybody know the up's n' down's about
using .NET to create unmanaged code?
-LJJ  
___________________________________________________________
From: pjknibbs  Date: 04/04/2002 11:42PM PST  
I've directly loaded an old (albeit quite small) C project into .NET and, apart from one header file
which had changed its name, it compiled and ran with no problems. We've also adapted a much more complex
project to .NET, but again, this only took a few hours--and most of that was spent fighting with SourceSafe
which really wasn't in a co-operative mood! On the whole I'd say it's a good idea to move to .NET.

The real downside is that Microsoft have changed some of the keyboard shortcuts again, just like they
did when they moved from 16-bit Visual C++ to the 32-bit version. I still end up hitting the wrong key
when I come to build a project (or, in .NET parlance, a "solution").  

:)