So glad this came back. The only problem I found is that my msi wouldn't run on POSReady 2009 and Windows XP but I resolved this by following the advice from http://stackoverflow.com/questions/23978677/dirca-checkfx-return-value-3-vs-2013-deployment-project
Great to have this back. I finally could upgrade to VS2013 (we use setup projects a lot and are using it to create .msm files which is not supported by the Installshield included). We found one problem with it though: if we add the Project Output from an SQL CLR project Visual Studio seems to crash when building the setup.
For the people who are complaining that VS 2013 is crashing, do you by any chance have "Web Essentials" add on installed? I found out that these two extensions don't play well together. Disabling the "Web Essentials" add on fixes the crash on open issue for me.
Hi, we just upgraded our TFS, and moving the solution to VS2013. Replacing the web deployment project, I cant see how to invoke the publish-
Trying "<MSBuild Projects="somepath\my project.sln /p:DeployOnBuild /p:PublishProfile=myProfile"
But it keeps saying it cant find the project? I'm not a build guy, so some examples would help. TIA
Launch Conditions for .Net 4.5 and above only checks for the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" registry, instead of checking the value of the Release DWORD.
To confirm this I have created an installer with a launch condition of .Net 4.5.2 and ran it successfully on a clean Windows Server 2012 R2 machine without issue (4.5.1 is standard on Server 2012 R2). When trying to run the installed software, it crashed as 4.5.2 was not present on the target machine.
I have also confirmed this on a 2008 R2 machine with .Net 4.0 installed – the launch condition was successful in recognising that the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" registry was missing, but after installing .Net 4.5 (2 versions below the required 4.5.2) which created the "Full" subkey, the launch condition message was not shown and the installer ran.
The information on the MS page https://msdn.microsoft.com/en-us/library/hh925568(v=vs.110).aspx describes the values of the Release DWORD that correspond to the versions of the .Net Framework, and it would seem that this is not being checked at present.
Hi, does this work with the Community Version of VS?
I have tried to create an installer for a project and all it create is the SetupWiz.msm. No msi or setup.exe.
What am I missing?
I do get this on building
WARNING: Unable to find dependency 'ENVDTE' (Signature='B03F5F7F11D50A3A' Version='7.0.3300.0') of assembly 'QSS.Components.Windows.Forms.dll'
I've used the Setup Project to create an installer for a simple Hello World WinForms application. The Application itself targets .NET 3.0 and runs fine on the target machine, but the Setup.exe gives me an error that the prerequisites of .NET 4.5 can't be met.
I have unchecked every single box in the prerequisites window, including the 'Create setup program' one at the top, I have set the .NET version to 3.0 in the launch conditions for the .NET framework, I have even set the BackwardCompatibleIDGeneration property of the setup project to true, but nothing has helped.
Does anybody here have an idea of why the setup project thinks it needs .NET 4.5 installed?
Thanks for your help!
I see you just recently uploaded a new version on 5/15/15. Is there a changelog anywhere? I am unsure if it's worth updating a new version. I tried googling around for one and was unable to find it.
During installation/uninstallation a small dialog appears which has one progress bar and a Cancel button. Can we somehow remove or hide this dialog? We have one custom ui wizard for cancelling the installation and user don't want user to click the cancel button on this progress bar dialog.
Or can we detect somehow in our custom action that user has clicked this Cancel button?