I guess you cannot just reuse VS 6.0 Series 60 app wizard in VS .NET.
Probably the shortest workaround would be to generate some or all possible variants of applications using Series 60 wizard in VS 6.0, and then to reopen these project files from VS .NET.
Later you can use these project 'templates' for your new projects.
Alternatively, you could have Virtual PC or VMWare installed, with a virtual machine that contains VS 6.0 installation so that you can use app wizard from there.
And yes, good luck: the project generated by Series 60 app wizard is one of the most complicated things I've ever seen.
Actually, it's a build process itself that is clumsy:
- six different subdirectories for project files;
- debug/release build generated in a completely different directories far, far away (depending on your project's source directory and SDK installation directory, this can be 10+ subdirectories deep!)
- build procedure invoking Perl scripts to generate makefiles that call other makefiles that call other Perl scripts, displacing files everywhere around...
One must be very motivated not to give up immediately.
If the idea is to make this platform adopted by developers, then it would be nice to iron this out somehow.
Get The EPOCfromMMP wizard and try to resolve problem with it.
It is used for creating new VC projects from MMP's file in IDE Microsoft Visual Studio .NET 2002 - 2003. and VC++ 6.0
Go to download http://wallsmedia.narod.ru/epoc/index.html
Series 60 AppWizard for VS.NET