Visual studio 2005 extension/plugin up gradation to visual studio 2017

Question

1.00/5 (1 vote)

See more:

Hi,

I have a project which builds a custom tool menu item in Visual Studio i.e an extension add-in project to visual Studio 2005.

Now I need to upgrade this project so that it should behave as plugin/extension for VS2017.

My first question is, Do we have possibility to upgrade this project type from Vs2005 to Vs2017 extension. I did little bit of google and I can see every blog saying to play with VSIX project type to build an extension. But in VS2005 days such extension project doesnt exist.(This is my guess)

2) I tried to upgrade the project some how and building installer. But after installation I cannot see any plugin visibility in tool bar to Vs2017 , which is expected.

Please give your inputs and it will be great if any solution do exist

What I have tried:

I tried to upgrade the project some how and building installer. But after installation I cannot see any plugin visibility in tool bar to Vs2017 , which is expected.

Posted 28-May-19 23:00pm

jing567

Updated 29-May-19 3:54am

Add a Solution

2 solutions

Add a Solution

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)

Richard MacCutchan · Answer 1 · 2019-05-29T02:03:00

Solution 1

See Starting to Develop Visual Studio Extensions - Visual Studio | Microsoft Docs[^].

Posted 29-May-19 2:03am

Richard MacCutchan

Comments

jing567 29-May-19 9:11am

Thanks for your reply. Please do read my query. I did considerable time on google and posted this question. The link which you have provided is the first link appear in google search and doesnt have info about my question :) Hope you posted reply to stand in the "Top experts" in dashboard in code project site.

Richard MacCutchan 29-May-19 9:42am

Well there is not much more that can be said. Your question is not specific to any programming issues, and until you can provide some proper details of what is failing in your code, and where it fails, it is anyone's guess what to do.

The article at the link I gave you contains full details of how to build extensions. So that should be the place where you can start to find out what you need to do to convert your extension code to the latest version.

BTW, I have no interest in being a "Top expert", I am merely trying to help guide people to solutions to their problems.

johannesnestler · Answer 2 · 2019-05-29T03:54:00

I'd just create a new extension project (VSIX Project). Verify you have updated your knowledge and can install/uninstall the new VSIX Project, and find out how to work with the "experimental instance" of vs (on Project properties page you can deploy your vsix on build directly to the experimental instance of VS to debug your Extension by checking a box...). With that up and running it should be quite easy to port your existing code to VS2017 because as far as i remember the Automation-API shouldn't have changed much, at least the principles are the same.