I had previously installed WIX 3.8, and could see the "Windows Installer XML" selection when creating a new project in VS 2012. I downloaded and installed VS 2013 Ultimate, with SP1. I did a Repair on WIX, and I did see it referencing VS 2013. But when I go to create a new project in VS 2013, the "Windows Installer XML" does not show.
When I look at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\Wix, it only has a "ProjectTemplates" folder with three zip files in it. The same folder in VS 2012 has a number of items in it.
What do I need to do to correct this (Do the trial versions of VS preclude this from working)?
I had this problem, you cannot do a repair as it won't try to re-detect the VS2013 installation. Just uninstall Wix completely and re-install and it will then work.
Related
When I go the the New Project dialog in Visual Studio 2015, Windows Installer XML isn't available. How can I enable WiX projects in Visual Studio 2015?
Update 2015-09-08: WiX Toolset 3.10 is released with official support for Visual Studio 2015 editions. It is available for download from wixtoolset.org.
You can manually enable Visual Studio 2015 compatibility with WiX 3.9 or earlier:
Copy
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\WiX to
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\WiX
Then execute as Administrator:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv" /setup
When you open Visual Studio 2015, WiX 3.9 and earlier projects will be compatible.
This was also my issue before, and it looks like Chris Schiffhauer's answer isn't the best solution by now, as WiX 3.9 or earlier is not specifically build for Visual Studio 2015.
The solution is just to install the latest builds of WiX v3.10 from this link as what they replied on their tweets: https://twitter.com/wixtoolset/status/597796279729528833
#5ervant latest builds of WiX v3.10 support #VisualStudio 2015.
I only have Visual Studio Community 2015 RC when I'm looking for a solution, and upon following Chris' answer, after installing WiX Toolset v3.9 R2, I didn't found the C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE folder nor the C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7 folder in my system.
If you have VS 2012 and VS 2015, Install Wix ToolSet V3.10.3.
This will install the Wix toolset for 2012 and 2015 will not yet detect it.
Next in Control Panel-->Programs, choose the WIX installation, right click and change. Choose the Repair option in the toolset UI.
Once repaired 2015 starts detecting the installer and it works fine after.
I have found that the order of installation is important. Using VS2015, when I tried to add an existing WiX project I could not select it because the *.wixproj extension was not available. When I tried to add a new WiX project the "Windows Installer XML" templates were not available.
To fix this I closed VS2015, uninstalled the WiX tools using the Control Panel and reinstalled it by running wix310.exe (version 3.10.2.2516 downloaded from https://wix.codeplex.com/releases/view/619491)
In my scenario the Wix project in the VS 2015 solution would load fine, but stopped loading one fine day with the exception that wix project type was not supported. The issue kept popping even after already installed the VS 2015 relevant Wix Toolset v3.11.1.2318 was updated.
The solution lied in going to Tools->Extension and Updates, locating Wix extension in the list of extensions and enabling it. It had got disabled somehow. Enabling it asked for restarting the VS 2015, which, upon restarting loaded the Wix project fine.
HTH!
I got the same issue with 3.11. I uninstalled 3.11 & installed WIX 3.10. Wix version 3.10 worked smoothly without any manual steps with VS 2015.
Atul
I have a project in a solution I am working on in Visual Studio 2012, and I get this message for one of the projects: "This version of Visual Studio does not have the following project types installed, or does not support them." It is a vdproj. What does this mean and how do I resolve this problem
The correct procedure to resolve "Incompatible" issue with VDPROJ Projects coming from Visual Studio 2010 and 2015 in 2017 or 2019 is:
Enter Visual Studio .NET 2017 or 2019
2017: Click on "Tools" -> Extension and Updates -> Online
2019: Click on "Extensions" -> Manage Extensions -> Online
Type "Installer Project" on the search box
Click on "Install" in Microsoft Visual Studio Installer Project
Restart Visual Studio .NET and follow the instructions to install the extension
With this extension the old project (2010, 2015) is capable to work in (2017, 2019). VDPROJ are not deprecated, simply they are improved with a new extension, for more information about this please visit the oficial MarketPlace.
There is also the official:
Microsoft Visual Studio 2015 Installer Projects
Microsoft Visual Studio 2013 Installer Projects
Microsoft Visual Studio Installer Projects (2017 & 2019)
Microsoft Visual Studio 2022 Installer Projects
if you can jump to VS 2013, 2015, 2017+2019, or 2022
But BozoJoe is right, its time to drop vdproj and move on to WiX.
vdproj is a MSI creation project for Visual Studio. Its been deprecated and most people have moved on to either WIX or NSIS or a professional grade installer creation tools such as Install Shield.
If you do not require an installer for your product just exclude the vdproj project from the solution and continue with your life
for fun if you want to try to transition right away to wix, try this powershell script https://github.com/chrisoldwood/vdproj2wix
Visual Studio 2017 can use the Visual Studio Installer. It is NOT a default. You have to run InstallerProjects.vsix. You can get it at Microsoft Visual Studio 2017 Installer Projects. I have used it and worked great, at least for a windows GUI project. It's worth a shot before you get into the Install Shield intricacies.
if You use Microsoft Visual Studio Installer Project (Vs2017).
Microsoft Visual Studio Installer Project may be disabled after an update.
Tools -> Extensions and Updates..
Click Installed
Find and Select -> Microsoft Visual Studio Installer Project
do Enable
Restart Visual Studio
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/
I have a newly built Windows 8 VM with VS 2012 Premium running on it, when I try open any sln file I get the following modal pop up error
Visual Studio 2010 Shell
Invalid license data. Reinstall is required.
I can open the sln's if I open up VS and then do project open, this is really annoying, any ideas how I fix it?
*Note I have done a VS repair and it didn't solve it...and I never had any VS RC release on the machine, all new build with s/w downloaded from the MSDN
Cheers
I encountered the same exact error when I created a solution with a full version of Visual Studio 2012 Professional on one machine and then tried to open the solution file with a copy of Visual Studio 2012 Express on a different machine. I got the error when double-clicking the solution file, but not when loading the solution into an already opened instance.
I fixed the error by opening the solution file (.sln) with notepad and changing the line that says Visual Studio 2012 to say Visual Studio Express 2012 for Windows Desktop.
After that, I was able to double-click to open the solution file on the machine that has Express installed.
I'm using VS 2013. I fixed this by right clicking the .sln and setting the Open With parameter to visual studio 2013 and not VS version selector or VS 2010.
I have faced the same problem. When I set the system Date and Time to the current Date and Time, The Problem solved by itself.
It looks like the .sln extension is owned by "Visual Studio 2010 Shell" a minimal version of Visual Studio that ships with products like SQL Server and Office to provide support for add-in development without any other features. Since this is a minimal version, it's unable to load any project type that ships with Visual Studio Express, Professional or above.
The same may happen when you have Visual Studio Express installed next to a full version of Visual Studio.
This may happen when you install an older version of Office or SQL Server after having installed Visual Studio. The old installer will hijack the extension.
To repair this problem:
use the "Open With" option of Windows and select the "Visual Studio Version Selector" as your default action.
Or open the "Default Programs" option in Windows, look up the .sln extension and make sure it uses the "Visual Studio Version Selector" as default:
Or locate Visual Studio 2012 in the Programs and Features window of Windows and chose "Change", the Visual Studio installer will pop up, chose "Repair" to have it repair the file associations and any other problems that may arise by installing Visual Studio versions in reverse order (it may for example mess up the MsBuild directory as well).
Remember that when Visual Studio 2010 was released, it could not yet know what Visual Studio 2012 would change, as such, it's best to install versions of Visual Studio in the order they were released. This may sometimes prove difficult, as other products may install Visual Studio versions without you knowing.
I have Visual Studio 2010 Ultimate installed. I installed all tools listed here.
When I create a new project in Visual Studio, I don't see anything about Windows Phone or XNA anywhere. I've tried reinstalling the tools. I've tried doing devene.exe /InstallVSTemplates following this.
Am I missing something here?
Update: I did have VS2010 SP1 installed before I installed the WP7 developer tools.
I was able to fix this by doing the following:
Uninstall everything related to Visual Studio 2010
Install Visual Studio 2010
Install the WP7 developer tools
Install VS2010 SP1
What I found was, when installing the WP7 developer tools, if VS2010 SP1 is installed, the tools installer doesn't find VS2010 and the plugins/templates don't get installed.
If there is a way to fix this without doing a reinstall, I'd love to know.
I did in this way:
goto the folder Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplates\CSharp\Silverlight for Windows Phone\
change the name folder 1033 to 2052
ran devenv.exe /InstallVSTemplates
start visual studio 2010, I found those templates are available but I got errors when try to create project form them .
So I changed the folder name back to 1033 and ran devenv.exe /InstallVSTemplates again.
Hi All,
I solve this problem as follows:
I'm creating a new project (silverlight for windows phone, for example) in Visual Studio Express.
Closing Express edition.
Open created project in my Ultimate edition! :)