Hi All,
Apologies for the delay on this; it took us a while to pinpoint the scenario and cause. It looks like for systems with only Visual Studio 2012 installed the template isn't getting extracted properly. Here is the workaround.
Basically, you need to extract the template from the setup and manually wire it up to work with VS:Hope that helps.
- If Visual Studio is open, close it.
- If the Extensibility SDK is already installed, uninstall it.
- Once the uninstall has finished, start the Extensibility SDK installer
- When the setup window appears, navigate to %temp%\{1275F0CE-72F0-4FDD-9981-CB215CE2F310}. You can find the path to %temp% by opening a command prompt and issuing the command �??echo %temp%�?�. On Windows 7, for instance, the temp directory will be C:\Users\<user name>\AppData\Local\Temp. Note that you must navigate to the temp directory while the setup window is open.
- Copy the setup.msi file from the temp directory to another location (e.g. C:\temp).
- Complete the Extensibility SDK setup.
- Extract the contents of the setup.msi. To do this, open a command prompt and issue the command �??msiexec /a <msi path> /qb TARGETDIR=<extraction path>�?� - for example �??msiexec /a c:\temp\setup.msi /qb TARGETDIR=c:\temp\viewer�?�. (No quotes)
- After the contents have been extracted, navigate to the Microsoft Visual Studio 11.0\CSharp\Silverlight\Esri folder in the extraction location.
- Copy the ESRIViewer.zip file to the appropriate Visual Studio 2012 templates directory. If Visual Studio is installed on the C drive, this will be C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ProjectTemplates\CSharp\Silverlight\Esri
- Open the Developer Command Prompt for VS2012 and enter the command �??devenv /setup�?� (You may need to run the command prompt as an administrator).
Katy
This is a quite good point and here I add another video to demo this method! http://screencast.com/t/9pGbEA0atP