Monday, August 13, 2012 10:59 AM
After i install my setup Visual studio 2012 is not showing up my project template under create new project. It comes up after I run devenv /Setup.
When i install VisualStudio 2012 newly and without opening it if i run my setup , then it shows up the template. But if the visual studio is opened before running my setup, it is not showing up.
What could be the problem and how can i fix it ? I want my template to appear without running devenv /setup. How do i do that?
Tuesday, August 14, 2012 5:41 AM
We can find the deference og devenv /setup on the msdn which said:Forces Visual Studio to merge the resource metadata that describes menus, toolbars, and command groups, from all available VSPackages.
I don't know what causes your Visual Stuido not showing the project templates.
I want to know how do you create your project templates,using the Export Template wizard or creating templates in the VSIX file?
Thursday, August 16, 2012 5:47 PMModeratorYou can't, /setup is required. The reason it works if you have never launched is that the first launch essentially does /setup (and then some).
Wednesday, August 22, 2012 6:41 AM
Created it using the VSIX file
Wednesday, August 22, 2012 6:43 AM
Since /setup is a costly operation, is there any other way to make the VS pick my project template?
Friday, August 31, 2012 8:15 AM
A workaround for this you may like to try is to touch "extensions.configurationchanged" under the <VisualStudio2012HomeDir>\Common7\IDE\Extensions" directory as part of your template deployment: resetting the date modified of this empty file seems to trigger searching of templates/packages when you next start VS2012. Even with the longer startup time, it's only a fraction of the time it takes to run devenv /setup.
Not sure if there are any side-effects of this approach or if it's even supported by MSFT so, yeah, YMMV. :)
Tuesday, October 02, 2012 8:52 PM
The solution I am going with, tested, so far works just fine, is to load both VS2012 and VS2010 side by side and just use the 2010 Project to build the setup, and do all my new work in the new 2012 version. Turns out you can load the Main Application project in both VS2010 and 2012. The you can load your already existing 2010 Setup into VS2010 and all works as expected. One thing I have found is that I need to exit out of VS2012 when I actually do the build of the Setup project in 2010. Certain files appear to be locked which will hold up the build of the Setup until you exit 2012. Then it just rips by fine.