Introduction

This article explains about custom wizard making and OpenGL custom wizard in Visual Studio 2010 using MFC custom wizard. Many people have a question about custom wizard in Visual Studio 2010. This article explains "How to make Custom Wizard in Visual Studio 2010 using OpenGL?".

Background

Previously in "Custom Wizard for OpenGL in Visual Studio .NET", I explained Visual Studio 2003/2005 Custom Wizard. Visual Studio 2008 was not different between Visual Studio 2003/2005 and Visual Studio 2008. Visual Studio 2010 environment is very similar to Visual Studio 2008. But, Visual Studio 2010 environment is very variable.

Firstly, Project XML file format is different from *.vcproj to *.vcxproj. And secondly, “Project properties” are very variable.

Create Custom Wizard

If you know the custom wizard making process, you have to create a custom wizard project in Visual Studio 2010 using “File > New > Project” menu. And, you can select custom wizard project in Visual C++ project list. Finally, you finish button click.

Editing Custom Wizard Script File

C:\Program Files\Microsoft Visual Studio 10.0\VC\VCWizards\AppWiz\OpenGL\Application\scripts\1033\default.js file is very~ very~ very~ important. This file is similar between Visual Studio 2003/2005/2008 and Visual Studio 2010. But, the script file is different project extension, target .NET Framework version, add on configuration properties on Visual Studio 2010. But the other is the same within Visual Studio 2003/2005/2008.

Visual Studio Wizard Insert

Last, if you make custom wizard project, you have to build this project. But, if you don't make custom wizard, you should insert custom wizard to Visual Studio 2010 Wizard list. C:\Program Files\Microsoft Visual Studio 10.0\VC\vcprojects\vc.svdir file is a list of Visual Studio 2010. You have to change your custom wizard install path for OpenGL Custom wizard file.

This is a security problem. The wizard files are marked as insecure. I had the same problem with the WTL Wizard.

Solution: download the zip file again, unzip it (I used 7zip) and install the AppWiz again

Important: Do not open the zip file via click on the downloaded file and copy & paste the files contained in the zip to the new destination. This will mark the file as unsecure. You see this with rightclick|properties on the file. At the bottom of the first page you see: (german)"Die Datei stammt von einem anderen Computer. Der Zugriff wurde aus Sicherheitsgründen eventuell blockiert"
Google translates this to "The file came from another computer. Access is blocked possibly for security reasons"

I had a similar problem with a custom wizard. It was a browser security issue.
I had my project files on a mapped network drive (actually a Linux server but I do not think this was the issue). When I put Script.js and common.js in the same folder as default.js and with the *.htm files on the same drive the problem was solved.