I've a windows application project developed in c# and VS2010 environment. Now I need to prepare a setup for it. I've prepared it via creating "setup project" within VS2010 and it works fine.
The problem is, when I wanted to migrate my project to VS2012, I noticed that Microsoft is no longer supporting "setup projects" inside VS2012 anymore. InstallShield technology seems to appear.
My question is, has anyone tried to use an existing setup project which is created by VS2010 in VS2012? Does it work? Any problems? Is that still supported for VS2012?
By the way, I researched in web and found out that WiX is another solution for preperation on setups. Does anyone use that? Can I integrate my VS2010 .SLN file into ViX? Will that work when I migrate my project to VS2012? If so, how?
My project will be commercial so that any another well 3rd party solutions are fine by me.
I think you should migrate to WiX, as it is available both for Visual Studio 2010 and the later versions of Visual Studio. It also creates MSI installers and is much more customizable than the setups created by the Visual Studio 2010 template.
Actually it is the other way: You don't integrate a solution with WiX, but a WiX installation project will be just like any other project in your solution. Pretty much the same a with the Visual Studio setup project type.
Related
I have developed a windows application (one type of CRM System) but now I want to create its setup file so it can be easily installed on client's machine. I have searched online and found out the way using InstallShield. But it is giving the free trial and then it is offering the paid version. Is there any other way to create Setup file without using InstallShield?
You can use the extension Visual Studio Installer Projects Extension: VSI_Bundle.
See the The Visual Studio Blog
It worked good for me.
See my answer in this post: https://stackoverflow.com/a/28029063/200824
You can use visual studio 2015 and install installer projects extension.
You should also take a look at https://wixtoolset.org. A lot of new, helpful elements (grammar is XML) were added to simplify development. So while it's not drag-and-drop design, it's fairly easy to use and 3.x builds MSIs that are still the mainstay on Windows. 4.x pre-releases can also build other formats such as AppX (though, that is only supported on Windows 10 to install).
Yes, i've tried devenv/install, with no help.
So, I don't have the Console C# Project option when creating the project,
as shown here
Currently i have installed windows basic pack - there's my 'about' screen.
I have just reinstalled Windows because i was getting the same exact problem on old system, and because VS2015 had interface bugs and crashed consequently, but it didn`t help(as well as reinstalling both VS 2015 and 2017 numerous times)
Hope that you can guess whats wrong with my PC.
Visual Studio 2017 setup allows you to very fine-grainedly install various "components" separately, or groups of components delivered as "workloads".
You're missing the workload named ".NET desktop development", which contains among others these project templates. So re-run setup and install that workload.
You have a link, Open Visual Studio Installer in a New Project window that will allow you modify your installed components
I am trying to create an installer for a project, But I don't know much how to do it? I've read some articles here and here
In those steps which describe the procedure of setup installer after adding a new project we should select s Setup and Deployment Projects in the dialog box so my issue was that !! , in My dialog box I don't have setup and Deployment Projects.
I'am using visual studio Community.
Can anyone help me.Thanks
Under Other Project Types you should see Setup and Deployment.
I believe in VS 2013 only the InstallShield Limited Edition is included so you can get the Installer Projects extension here
I have a wpf application which needs to generate an installer file. The IDE for this project is vs2012. I found there was no setup project template at all in vs2012. I googled the solution and I found template below which was for vs2013.
enter link description here
Is there any setup solution for vs2012?
You can go with clickonce solution to deploy your application. It is quite easy to use clickonce. Just google this.
If you want to generate the installer using setup project than you will definitely require the Setup and Deployment template in Visual studio but unfortunately Microsoft has removed the Setup project template from VS2012.
In this case you can go with WIX which is a free open source alternative, far more functional, but tricky to set up.
See the link for more details.
VS2013 Windows Service - How to make installer?
I have a solution with .NET projects and a setup project(Visual Studio Installer 2010). My previous version of the same project was 1.7.9 and the new version is 1.8.4. I also create a shortcut on the desktop to one application in my MSI. I changed all the versions in the assemblyinfo.cs and also changed the product version in the Setup Project, the product code got changed automatically and the upgrade code is the same. The problem I'm facing is that the Targetdir is updated with 1.8.4 files. But on the desktop I see 2 shortcuts (1.7.9 & 1.8.4) and in control panel I see two versions of the same application. I have set the RemovePreviousVersion flag to true and also set the DetectNewerVersion to true. Can someone please help me out with this? After changing the assemblyinfo file why isn't it upgrading properly?
Visual Studio Setup Projects are a deprecated feature that hasn't seen any love since before Visual Studio 2008 was released. I understand it's a feature that ships with Visual Studio all the way up to 2010, but it's probably a much better idea to switch to another product, such as WiX (free and open source), NullSoft Installer a 3rd party commercial solution.
From what I gather, you did the correct things building your installer and setting up the configuration. You might want to check that the previous installer really has the same GUID you're expecting it to have.