I have an add-in that works with Visual Studio 2008, 2010 and 2012. All I have to do is to copy some files to c:\users\username\documents\Addins folder, and then check the relevant line in VS Add-in Manager.
I've just installed Visual Studio 2013, and I'm trying to integrate it with that add-in. It does not work. I googled and it says something about changes to add-ins... new VS packages... I lost it.... Just want to make it work with no major changes. Do you know how to?
Thank you
Make sure your .addin file lists support for VS 2013:
<HostApplication>
<Name>Microsoft Visual Studio</Name>
<Version>12.0</Version>
</HostApplication>
And the directory to copy files is usually documents\Visual Studio 2013\Addins.
It would be best to convert it to a VSPackage as AddIns are depreciated in VS 2013. As with any other future updates from MS you wouldnt want that to break your addin each time would be the risk.
http://msdn.microsoft.com/en-us/library/dn246938.aspx
Related
My question is about the different versions of Visual Studio and an effective way to update the web applications or websites that were created in visual studio 2003 to visual studio 2010 all to visual studio 2013. Most of the solution files on the web server for the various applications or websites have not been updated since 204. But some of the .aspx.vb files have been updated in 2012. Not sure if there is a missing .sln file or that the files were all updated manually using notepad or something? I need to update the content of several of these projects and not sure where to begin. Looking for the most effective way to update these files. Anyone with experience transitioning from different versions of Visual Studio working with visual basic may have these same questions. Some of these include crystal reports from visual studio 2005.
Have you opened the .sln file in VS2013? I know when I was transitioning projects from VS2008 to VS2013 it prompted me to convert them when I tried to open it in VS2013. When and if there were any issues it showed you what didn't match up and what might be obsolete. Might be a good starting point if you haven't already tired.
I recently started a new job, and got a machine with Visual Studio 2013 Proffesional installed. This would be great, except the colleague that I'm working with is using Visual Studio 2010. As far as I know, there is no way to work on the same project (or solution), without having quite a lot of issues, is this correct?
And if so, is it still possible to download Visual Studio 2010 (from a reliable source)? I cannot seem to find it anywhere in my MSDN subscriber downloads. All I can find is a stuff like service packs, tools, etc. Did they terminate the support of it?
You work on visual studio 2013 but there are option to select which version of visual studio you want select 2010 and run your project.
You should be able to open Visual Studio 2013 solutions in 2010, if you install Visual Studio 2010 SP1. There is a possibility that some project types won't be supported, but the solution should open.
I am trying to build fltk 1.1.10 in Visual Studio 2013 but I get the warning
"fltk.sln: Visual Studio needs to make non-functional changes to this project in order to enable the project to open in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without impacting project behavior."
After searching, I found out how to do this for a C# project but how can I do it for fltk.sln?
Many thanks for the help.
There are 3 solutions in the FLTK1.1.10 distribution
visualc - for Visual Studio 6
vcnet - for Visual Studio 2003
vc2005 - for Visual Studio 2005
None of these will load directly into VS2013. They have to be converted to VS2013 format. Easiest way is to make a copy of vc2005 and call it vc2013. Then start fltk.sln. It will tell you that it needs to make a one way upgrade with the message you described. Just click OK.
What this does is migrate the 2005 sln to 2013 sln and migrate the vcproj files to vcxproj files. Basically you don't lose the vcproj files - you just get completely new versions of vcxproj files. Once that is done, just do a build.
I want to migrate a Visual Studio 2010 Solution so that I can work with Visual Studio 2013.
If I understand it right, due to the round-tripping feature of Visual Studio 2013,
there is no reason to convert the solution!? I can just open my old solution with
Visual Studio 2013 and can just work with it.
Is that right? Or is there a good reason or need to do a conversion to a
Visual Studio 2013 solution.
Or better: Is there any good reason to not stick with the old Visual Studio 2010 solution?
Visual Studio 2013 can open a sln file created by Visual Studio 2010. However, Visual Studio 2010 can not open a sln file created by Visual Studio 2013.
The easiest way to see this is to open the sln file in a text editor and look at the first 2 lines:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2012
Visual Studio has a version setting in the header (this example is from VS 2012). An older version of the tool wont open the file.
Beyond that there aren't really any big differences in the file. There are certain project types (ie Project("{guid}") that aren't supported in older version of Visual Studio. For example a Visual Studio 2013 SDK project can only be opened with Visual Studio 2013.
To wrap up, if you have an existing Visual Studio 2010 sln file, there isn't really any need to change it. If you plan on opening it again in VS2010 then make sure you don't change it. Otherwise I wouldn't worry about it and just let VS do whatever makes VS happy.
I installed the free version of ApexSQL which is awesome in SSMS, but I really don't want all those menus in Visual Studio. I went to add-in manager and unchecked them, but the Startup column is checked and disabled so every time I restart Visual Studio they come back.
Is it possible to permanently remove the ApexSQL menus from Visual Studio?
If you have ApexSql installed and you don't want those pesky menus in Visual Studio do 2 things.
In Visual Studio, go to Tools > Add-in Manager and uncheck the ApexSql addins. Close Visual Studio.
In Windows 7, there's a hidden folder C:\ProgramData. In Windows Explorer go to C:\ProgramData\Microsoft\MSEnvShared\AddIns folder. Edit each of the *.MsvsLoader.Addin files and set <LoadBehavior> to 0. If you can't save the files directly, you'll have to save the files to a different location (desktop maybe) and then copy them back into C:\ProgramData\Microsoft\MSEnvShared\AddIns because there's some Admin privilege required.
Now when you restart VS those ApexSQL menus should be gone
The issue of crowding menus is resolved in latest releases, now all ApexSQL add-ins are under the main ApexSQL menu as sub-menus. They look like this now:
If you don't need ApexSQL add-ins in VS or SSMS you can simply choose not to integrate them with VS or SSMS during the installation, just check out SSMS ot VS version in which you want the add-ins integrated
Note: To get this dialog in which you can check the wanted integration you need to use individual installers not the main one. You can find all individual installers on this link
Disclaimer: I work for ApexSQL as a Support Engineer
For Visual Studio 2010 on Windows 7, I attempted #Chris Bayles suggestion and do not see ApexSql addins under Tools->Add-in Manager.
I followed #Jerome2606's pointer to https://knowledgebase.apexsql.com/remove-add-ins-just-visual-studio-retaining-sql-server-management-studio/ and it worked for me, but only when I removed the parent ApexSQL folder as well.
Summary of what is required to do:
Remove folder
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\ApexSQL
Depending on the version of Visual Studio, the version number in the default installation location will be different:
Product name Version number
Visual Studio 2010 Microsoft Visual Studio 10.0
Visual Studio 2012 Microsoft Visual Studio 11.0
Visual Studio 2013 Microsoft Visual Studio 12.0
Visual Studio 2015 Microsoft Visual Studio 14.0
Select and delete the ApexSQL folder and its contents.
Open Command Prompt as an administrator, then run
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" /setup
Please note the command is different for Visual Studio 2012, 2013, and 2015.
If you are using SSMS v18.0 then you can disable the apex features in following way.
You can find the ApexSQL.Complete.Addin.SSMS18.pkgdef file from following path.
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Extensions\ApexSQL Complete
Then open this file in Notepad++ Administrator mode and comment the content.
If you need further reading follow this link.
https://knowledgebase.apexsql.com/remove-apexsql-tools-sql-server-management-studio/