On trying to convert the starter kit to work with the XNA 3.0 CTP. When i unzip the installed template, and make the changes from v2.0 to v3.0 and zip it back up, neither visual studio 2005 pro or visual studio 2008 express c# will recognize the altered template. Also, just unziping, and rezipping with no modifications it causes it not to appear. I have also tried changing the extension on the .vsi installer file to .zip to try and locate the problem there. However i get an error saying that the compressed folder is corrupt. According to the directions from microsoft for manually creating a vsi, and for creating a template, the fix should be as simple as some of the previous posters have recommended. That all you have to do is change the v2.0 to v3.0 and the assembly versions from 2.0.0.0 to 3.0.0.0. I can repeat this problem with any created template that uses the export template wizard with the following:
This problem exists on XP SP2 and Vista SP1, with both Visual Studio 2005 and 2008
1) create a new project of any type
2) select File->Export Template
3) follow the steps to create a template from the newly created project and click Finish
4) select File->New Project and verify that the template is visible under My Templates, click cancel
4) go to the location where the template zip file was created (on my machine it was C:\Documents and Settings\<userName>\My Documents\Visual Studio 2008\Templates\ProjectTemplates)
5) right click the zip file and choose Send To...->Compressed (zipped) Folder
6) follow the steps on the wizard to extract the file (just accept the defaults)
7) delete the zip file you just decompressed
8) right click the folder that was created in step 6 and choose Send To...->Compressed (zipped) Folder
9) follow the steps in the wizard excepting the defaults
10) go back to Visual studio and select File->New Project .. the template is no longer visible undere My Templates
with all that having been said, If the original RPG template would just load all of the projects (it does not load the executable project) i could just manually change the invalid references to the correct xna v3.0 references and continue working from there.
I'm trying to locate a different work around at the time. If i come up with a workable solution i will post it here as soon as i find out, one way or the other.