How do you tell InstallShield LE which project in the solution to install? I have added the installer project to my solution and I don't see where to tell it which project needs to be included into the install. Currently it just installs a blank folder.
Authoring installers is development. InstallShield LE doesn't automagically look at your solution and decide for itself how to deploy your projects.
Take a look at InstallShield Limited Edition for Visual Studio 2010 Walkthrough for a high level walkthrough.
Related
I installed WIX in my machine.
I followed the video of https://www.youtube.com/watch?v=CoFPyIbcqN8enter link description here
I can not find any way to add File Systems, no icon for it, no context menu entry on project.
I am using Visual Studio 2012.
That's the Add-In Express designer for WiX in the video. It's a paid for component.
Installing WiX on your system only adds project templates to Visual Studio. It's a free installer/packaging engine that uses XML (scripting) to build MSI's and etc and doesn't come with a designer.
WiX is quite a steep learning curve, if you want the editor then I suggest you check out the Package & Deployment add-in Microsoft re-introduced for VS2013, it's on VisualStudio Gallery. Brian Harry blogs about it here: http://blogs.msdn.com/b/bharry/archive/2014/04/18/creating-installers-with-visual-studio.aspx
Visual Studio 2013 has a free Community Edition that you can use. You add the Installer add-on:
https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d
Then what you have is the same Visual Studio installer setup projects as you had in VS 2010.
We have VC++ projects in VS 2008 and Wpf Projects in 2010. We want to migrate both of them to Visual Studio 2015.
The biggest problem we face, while a new user needed to install our software is, he need to install the pre-requisite of installing VC++ Redistributable Package, which requires Administrator rights. Then he need to install our application via clickonce server.
We want to ease this part - installing VC++ Redistributable Package.
Is the new 2015 VC++ Redistributable can be installed in my application path, without requiring administrator rights? I could not the spot the link to download VS 2015 VC++ R P link - please provide.
I got the suggestion of using /MT (linking statically) from below link, but we want the application to be statble (as we also dispatch patches), we don't want a library conflict.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/a8d4ca59-c295-43bf-b34e-518fe2f7977c/vc-2015-redistributable-package?forum=vclanguage#667db896-f517-4fa5-b5b7-b5b0c3d12d52
Please, help.
I believe no, you can't do that.
Read this article at VC++ team blog: Introducing the Universal CRT, where James McNellis said:
App-local deployment of the Universal CRT is not supported.
I have a game written in MonoGame in VS2012. How can I create setup file witch will also install .net framework if user doesn't have it?
There are no setup projects in VS 2012, unless you get the InstallShield LE add-in. VS 2010 had setup projects; VS 2013 supports the return of installer projects as an add-in. Therefore you may be stuck looking for a 3rd party solution, like InstallShield LE or any other number of other tools that can build setups and have a VS IDE add-in support (such as WiX). List of tools here:
http://www.installsite.org/pages/en/msi/authoring.htm
If you are keen on VS setup projects and want a simple tool that does the basics without you needing to learn too much, moving to VS 2013 and using the installer projects add-in would probably suit you.
https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d
I have a windows form project and I want to create an installation package for this project. How can I create a setup file in Visual Studio 2012 ? My project is without data base.
How to create a Setup package using Visual Studio 2012.NET?
Microsoft released the Visual Studio Installer Project extension in April of this year, the catch is it's for VS2013, not VS2012.
http://blogs.msdn.com/b/visualstudio/archive/2014/04/17/visual-studio-installer-projects-extension.aspx
The 'lite' InstallShield option remains in VS if you need something with more flexibility.
Advanced Installer also has a free version that includes an extension for VS. This is a commercial tool but the extension is included in the free edition as I said, for more advanced features you need to purchase a Professional or higher licenses and edit the project direct from Advanced Installer GUI, not from VS. (but you can still use the project in the VS solution, so you get the MSI built at the end of your build process)
Visual Studio setup projects (vdproj) are not supplied with VS 2012
There are several solutions for you:
You could use InstallShield instead.
If you don't want or
can't use InstallShield for any reason, you could try WiX. This
toolset builds Windows installation packages from XML source code.
If you only use Windows Presentation Foundation (.xbap), Windows Forms (.exe), console application (.exe), or Office solution (.dll) you could look at ClickOnce. To use this you should right click on the project file in the solution explorer and select "Publish" from the pop-up menu.
Alternatively you can use previous version of Visual Studio (2010).
In Visual Studio 2010 SP1, there is an option on the right-click menu on a web project to Add Deployable Assemblies. Phil Haack blogged about it here.
In Visual Studio 11 beta and Visual Studio 2012, this option appears to be missing. Thankfully, you can easily round trip solutions between VS 2010 and VS 11 so I could just open the solution in VS 2010 to add the MVC assemblies to the _bin_deployableAssemblies folder.
Is it just my installation thats broken or do I need to install anything else to get this working?
The Add Deployable Assemblies dialog was a feature that enabled you to deploy MVC or Web Pages projects. It was necessary because in older versions all the assemblies were installed into the GAC on your dev machine but you wouldn't necessarily know if that was the case on the server. Thus this tooling gesture that made your project bin-deployable.
Starting with MVC 3 Tools Update we are now using Nuget package references, which means that your project is automatically bin-deployable. Since the tooling gesture is no longer necessary it was removed from VS 11.