I think I have it fixed. It was not an issue with the Extensibility installer at all, the paths to my project templates and item templates were set to my user folder in Visual Studio rather than Visual Studio's install location where the Extensibility SDK was putting the template. Setting the correct paths in Visual Studio under Tools > Options > Projects and Solutions seems to have solved the problem.
Could you please specify a little bit more? I still have the same problem here. Thanks.
Hello Mette,
Sorry you've had trouble extracting the templates. Unfortunately the zip file is 15MB, so it can't be attached here at the forum. Can you tell me where you're getting stuck in the process of extracting the zip file? Are you able to see the .zip file once you extract it from the Setup.msi?
Thanks,
Katy
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
I think I have it fixed. It was not an issue with the Extensibility installer at all, the paths to my project templates and item templates were set to my user folder in Visual Studio rather than Visual Studio's install location where the Extensibility SDK was putting the template. Setting the correct paths in Visual Studio under Tools > Options > Projects and Solutions seems to have solved the problem.
Hi,
I also have the similar problem. I have created an MVC template in VS 2013, to re-use basic functionality using VSIX Extension. I am able to see the zip file in appdata/local......../projecttemplate location. When i open new project wizard. it doesn't show up there.
I even try to put the zip file in visual studio project template (Where VS is installed). This way it comes up in new project wizard but when i create new project from this template. It says "file paths not found in project folder". I unzip the template and the files are there.
I am not able to understand why it is showing this error.
Any suggetion to make it run??????