Cannot rebuild the VSIX package #52

Closed
zpqrtbnk opened this Issue Jun 4, 2015 · 13 comments

Comments

Projects
None yet
6 participants
@zpqrtbnk
Owner

zpqrtbnk commented Jun 4, 2015

Getting error VSSDK1031 - "Extension '' could not be found. Please make sure the extension has been installed." Not sure anything has changed in the project file, really. Can fix by editing the project propertiex, VSIX tab, and unchecking "Deploy VSIX content to experimental instance for debugging". But?

@zpqrtbnk

This comment has been minimized.

Show comment
Hide comment
@zpqrtbnk

zpqrtbnk Jun 4, 2015

Owner

Read this MSDN post which says:

I had the same issue. No suggested solution worked. The problem was: somehow, the experimental instance refused to install the current extension version. Hence the error message which seems to come from a check task during the build.

The "solution" for me: simply increase the version number of the extension. This causes VS to recognize it as 'new' and allows the install.... Took me 2h to find out.

Need to try it.

Owner

zpqrtbnk commented Jun 4, 2015

Read this MSDN post which says:

I had the same issue. No suggested solution worked. The problem was: somehow, the experimental instance refused to install the current extension version. Hence the error message which seems to come from a check task during the build.

The "solution" for me: simply increase the version number of the extension. This causes VS to recognize it as 'new' and allows the install.... Took me 2h to find out.

Need to try it.

@zpqrtbnk

This comment has been minimized.

Show comment
Hide comment
@zpqrtbnk

zpqrtbnk Jun 4, 2015

Owner

Tried to bump the minor version (2.1.3.44 to 2.1.3.46) in the manifest file - does not work.

Owner

zpqrtbnk commented Jun 4, 2015

Tried to bump the minor version (2.1.3.44 to 2.1.3.46) in the manifest file - does not work.

@zpqrtbnk zpqrtbnk added the bug label Jun 4, 2015

@zpqrtbnk zpqrtbnk self-assigned this Jun 4, 2015

zpqrtbnk added a commit that referenced this issue Jun 4, 2015

zpqrtbnk added a commit that referenced this issue Jun 5, 2015

@AmadeusW

This comment has been minimized.

Show comment
Hide comment
@AmadeusW

AmadeusW Aug 13, 2015

This issue came up in search results when I had the same problem. I blogged about a solution that worked for me: reset the /rootsuffix exp command line argument in Zbu.ModelsBuilder.CustomTool properties, build the solution, restore the argument and build again. Let me know how it went!

This issue came up in search results when I had the same problem. I blogged about a solution that worked for me: reset the /rootsuffix exp command line argument in Zbu.ModelsBuilder.CustomTool properties, build the solution, restore the argument and build again. Let me know how it went!

@zpqrtbnk zpqrtbnk added this to the 2.1.4 milestone Sep 16, 2015

@zpqrtbnk

This comment has been minimized.

Show comment
Hide comment
@zpqrtbnk

zpqrtbnk Sep 16, 2015

Owner

Thanks for the suggestion. Tried to build again today and somehow, it works.
Weird.

Owner

zpqrtbnk commented Sep 16, 2015

Thanks for the suggestion. Tried to build again today and somehow, it works.
Weird.

@zpqrtbnk zpqrtbnk closed this Sep 16, 2015

zpqrtbnk added a commit that referenced this issue Sep 17, 2015

@zpqrtbnk

This comment has been minimized.

Show comment
Hide comment
@zpqrtbnk

zpqrtbnk Jan 14, 2016

Owner

Having the same issue again, with Visual Studio 2015.

Looked at @AmadeusW blog post, unfortunately my solution does not have anything in command line arguments that I can remove. So the main solution would not work. So I went on trying the other options, including removing the extension from the main VS instance, and doing (which essentially re-creates the experimental instance):

cd "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VSSDK\VisualStudioIntegration\Tools\Bin"
CreateExpInstance.exe /Reset /VSInstance=14.0 /RootSuffix=Exp

Alas, nothing seems to work.

Next I decided to compare my VSIX project against a fresh project. In my project options, Debug start action was set to "start project" and not in the fresh project. So I changed mine to align with the fresh project, ie "start external program" with option /rootsuffix Exp.

Fails.

Read this issue and tried to manually start the exp instance. Ie, exit all instances of Visual Studio, do the reset as explained above, then

cd "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE"
devenv.exe /rootsuffix exp

Works!

Owner

zpqrtbnk commented Jan 14, 2016

Having the same issue again, with Visual Studio 2015.

Looked at @AmadeusW blog post, unfortunately my solution does not have anything in command line arguments that I can remove. So the main solution would not work. So I went on trying the other options, including removing the extension from the main VS instance, and doing (which essentially re-creates the experimental instance):

cd "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VSSDK\VisualStudioIntegration\Tools\Bin"
CreateExpInstance.exe /Reset /VSInstance=14.0 /RootSuffix=Exp

Alas, nothing seems to work.

Next I decided to compare my VSIX project against a fresh project. In my project options, Debug start action was set to "start project" and not in the fresh project. So I changed mine to align with the fresh project, ie "start external program" with option /rootsuffix Exp.

Fails.

Read this issue and tried to manually start the exp instance. Ie, exit all instances of Visual Studio, do the reset as explained above, then

cd "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE"
devenv.exe /rootsuffix exp

Works!

@AmadeusW

This comment has been minimized.

Show comment
Hide comment
@AmadeusW

AmadeusW Jan 14, 2016

So did your build process create the .vsix and deploy it to the experimental instance only after you manually launched and closed experimental Visual Studio?

So did your build process create the .vsix and deploy it to the experimental instance only after you manually launched and closed experimental Visual Studio?

@zpqrtbnk

This comment has been minimized.

Show comment
Hide comment
@zpqrtbnk

zpqrtbnk Jan 14, 2016

Owner

Correct - it worked only after I manually started experimental Visual Studio - even resetting, deleting & recreating the experimental VS was not enough

Owner

zpqrtbnk commented Jan 14, 2016

Correct - it worked only after I manually started experimental Visual Studio - even resetting, deleting & recreating the experimental VS was not enough

@AmadeusW

This comment has been minimized.

Show comment
Hide comment
@AmadeusW

AmadeusW Jan 14, 2016

Thank you. I will update the blog post!

Thank you. I will update the blog post!

@jameswiseman76 jameswiseman76 referenced this issue in jameswiseman76/JsGoogleCompile Jan 15, 2016

Open

Create VSIX #8

@tahaipek

This comment has been minimized.

Show comment
Hide comment
@tahaipek

tahaipek Jun 9, 2016

I solved this problem. Thanks for response @zpqrtbnk
There is an easier solution. Delete this folder and VS will be recreated with default settings. C:\Users*User*\AppData\Local\Microsoft\VisualStudio\14.0Exp

tahaipek commented Jun 9, 2016

I solved this problem. Thanks for response @zpqrtbnk
There is an easier solution. Delete this folder and VS will be recreated with default settings. C:\Users*User*\AppData\Local\Microsoft\VisualStudio\14.0Exp

@ChristopherHaws

This comment has been minimized.

Show comment
Hide comment
@ChristopherHaws

ChristopherHaws Nov 27, 2016

It seems like the issue is that the assembly's version (not the extension version in the manifest file) is not being incremented. I was having this problem when the assembly version was set to [assembly: AssemblyVersion("1.0.0.0")] or did not exist. Changing it to [assembly: AssemblyVersion("1.0.*")] solved the issue for me.

It seems like the issue is that the assembly's version (not the extension version in the manifest file) is not being incremented. I was having this problem when the assembly version was set to [assembly: AssemblyVersion("1.0.0.0")] or did not exist. Changing it to [assembly: AssemblyVersion("1.0.*")] solved the issue for me.

@claudiuconstantin

This comment has been minimized.

Show comment
Hide comment
@claudiuconstantin

claudiuconstantin Nov 29, 2016

Increasing the version number of the extension worked for me.

Increasing the version number of the extension worked for me.

@zpqrtbnk

This comment has been minimized.

Show comment
Hide comment
@zpqrtbnk

zpqrtbnk Nov 29, 2016

Owner

Weird - I tried in the past to go from eg 1.0.0.0 to 1.0.0.1 without success... but IIC you are going from 1.0.0.0 to 1.0.1.0 - wondering if that makes a difference?

Owner

zpqrtbnk commented Nov 29, 2016

Weird - I tried in the past to go from eg 1.0.0.0 to 1.0.0.1 without success... but IIC you are going from 1.0.0.0 to 1.0.1.0 - wondering if that makes a difference?

@janvanderhaegen

This comment has been minimized.

Show comment
Hide comment
@janvanderhaegen

janvanderhaegen Dec 20, 2016

My version of this issue was resolved after deleting the 14.Exp folder as @tahaipek suggests, then manually starting devenv.exe with /rootsuffix Exp arguments. Visual Studio opened, I went to Tools > Extensions and Updates, and the "Composing MEF graph" dialog popped up.
After that, I could close the exp VS and all was well again.

My version of this issue was resolved after deleting the 14.Exp folder as @tahaipek suggests, then manually starting devenv.exe with /rootsuffix Exp arguments. Visual Studio opened, I went to Tools > Extensions and Updates, and the "Composing MEF graph" dialog popped up.
After that, I could close the exp VS and all was well again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment