I want to create my installer. But missing Other Project Type > Visual Studio Installer > Setup Project
They are not supported anymore on VS2012.
http://blogs.msdn.com/b/buckh/archive/2011/03/17/visual-studio-setup-projects-vdproj-will-not-ship-with-future-versions-of-vs.aspx
VDProjects are no longer supported. Either:
Use older versions of visual studio to build existing VDPROJ project types (you can keep them in the solution)
If creating new installers, use a framework such as WiX which contains Visual Studio integration. Little bit of a learning curve, but a very good product (and free). This will produce an MSI from XML within a WiX project in visual studio after you install it.
http://wixtoolset.org/
Related
I use Visual Studio Community 2017.
I need to create a new project of U-SQL Project.
When I do that, I have this error.
There is a missing project subtype.
Subtype: '{416D63FD-0477-49AA-A954-A7C5B95A9B51} is unsupported by this installation.
Unfortunately, R Tools for Visual Studio in 2017 updates the assembly binding redirect for all Visual Studio which causes conflicts for others. Could you try to go to the Visual Studio Installer, and uninstall the Data Science workload (which contains R Tools) and see if the issue goes away?
We have a build definition in TFS 2015 that have worked fine with Visual Studio 2015 projects and solutions. We have now decided to upgrade to Visual Studio 2017 and thus we would like to target Visual Studio 2017 in the Visual Studio build task. We have installed Visual Studio 2017 on the build agent. Unfortunately the only options available int the Visual Studio build task are 2012, 2013, 2015 and Latest. We have tried latest but it does not find Visual Studio 2017 on the build agent. It won't work with the msbuild task either.
I have a similiar issue and resolved by installing VS2017 in my build agent server and configuring MSBuild to point to my MSBuild 15.0 folder:
Add MSBuild to your build steps
On the Advanced options, expand and fill the 'Path to MSBuild' like the image below:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin
VS2017 RTM is released recently while TFS2015 was released before. That's why there is no VS2017 option in VS Build Task in TFS2015 Server. If you upgrade your server to the latest TFS2017, you would see "Visual Studio "15" (preview)" option listed in VS Build Task which is the version for VS2017 preview. And in the feature, the option will be updated to VS2017 which is the same as VSTS.
we are facing a similar issue and it is not possible for us to update ourselves as it is maintained on a company level where we cannot take that much influence.
However our team wanted to switch to VS2017 and make use of the C# 7 features. That's why we tried it as well with replacing the build steps from Visual Studio Build to MSBuild. Sadly this did not work as expected (we got some errors during the build).
As our main objective is to use the C# 7 features we looked for a way how to still achieve that at the time with Visual Studio 2015 remaining on the Build Server. We ended up using the nuget package Microsoft.Net.Compilers that, when used in a project, will use that compiler instead of the installed one.
More on this can be found in this Thread.
It seems the updates to the build tools are installed via the command line of the VS2017 installer.
See the docs for details.
Just adding another thing: if you're using custom build template make sure to edit it and modify the ToolPath attribute value to:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin
I have Visual Studio 2008, 2010, and WIX37.msi (WIX 3.7) installed on my machine.
However, I am unable to see WIX project type in Visual studio 2008/2010.
Do I need to install additional tool/plugin?
I have Visual Studio 2008 and Visual Studio 2010 installed on my machine and I installed WiX v3.7 RTM from Codeplex. Things work okay for me. There is a known issue in VS2008 that requires you to set an MSBuild property called RunWixToolsOutOfProc to true. This occurred because parts of WiX v3.7 were incorrectly built against the NETFX4.0 and VS2008 runs on NETFX2.0.
Install v3.0 of WiX Toolset, to make it work with Visual Studio 2008. You can get it here: http://wix.codeplex.com/releases/view/44406
I don't know why it's not documented on their site but apparently you can't install the latest version (3.10 at the moment) and make it work with VS2008.
I got a copy of a Visual Studio 2005 project from a friend. The project referenced the DLLs Microsoft.ReportViewer.Common and Microsoft.ReportViewer.WinForms. On my machine I have Visual Studio 2012. I upgraded the project. The references to these DLLs are broken, understandably, because they are Windows locations, not in the VS project. So, I want to delete the references and re-create, but I cannot find the DLLs on my machine. Do they not get installed with Visual Studio 2012? Can I download them?
I got a copy of a Visual Studio 2005 project from a friend
Which explains the problem, the target .NET version of your project is 2.0. The ReportViewer included with VS2012 requires at least 3.5.
Fix it with Project + Properties, Application tab, Target Framework combobox. You'll then find the ReportViewer control back under the "Reporting" header in the toolbox.
These have been replaced by Report Server. Though if you'd copy them over from your VS2005 machine you should still be able to use them as binary references in your solution. You can download the binaries from the MSDN Download site.
Though there should be binaries for Visual Studio 2012 as well. I suspect they will get installed when you install the SQL Server Development tools, which include the SQL Server Reporting Server components.
You can try to use the Redistributable package for Visual Studio 2010.
Is it possible to use Wix with Express editions? I am interested in 2010/2012 versions. I know I can use candle and light from the command line, but I am interested in integration with IDE
The Express versions of VS does not allow to extend the VS with the necessary plug-ins. So you have to stay with the command line.
Alternatively to VS you could try WiXEdit.
Actually, if the goal is to have a free installer suite, WiX is perfectly happy installing into Visual Studio Shell Integrated, which is freely available. All features of WiX are available.
The only limitation is you have to open a different instance of Visual Studio in order to build your installer, but I haven't found this to be limiting in the slightest, and in fact I appreciate the separation of concerns.
Of course, another solution these days is to simply use VS Community Edition.