Vs2013 addin into vs2015 vspackage

Question

0.00/5 (No votes)

See more:

VS2015

Can anyone please guide me how can I convert Add-Ins to VSPackage Extention without recreating/replicating everything into VSIX?

I have one addin which is supporting VS2010 to VS2013. I have everything in .sln. I want to migrate/create .addin into .vsix for compatibility issue of VS2015.

What I have tried:

After few research, I have found that the code what is written in IDTCommandTarget.Exec method has to run into my custom command class of vsix project...

FAQ: Converting Add-ins to VSPackage Extensions

So, I created a new .vsix project in same solution & add a reference of my .addin project into .vsix project but its giving me following error...

An exception of type 'System.IO.FileLoadException' occurred in GForgeVSIX.dll but was not handled in user code
Additional information: Could not load file or assembly 'GForgeTrackerAddIn, Version=1.2.2.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)

Posted 9-Mar-16 23:20pm

Ishan Malik

Add a Solution

Comments

Richard Deeming 10-Mar-16 5:56am

"A strongly-named assembly is required."

So give the assembly a strong name.

Strong-Named Assemblies[^]
How to: Sign an Assembly with a Strong Name[^]

Ishan Malik 11-Mar-16 2:40am

Thanks...its working now

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)