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.
Can anyone help me with creating a shortcut on the windows task bar as part of the install.
I have found out how to create a custom folder but I'm not too sure about how to direct it for example to:
C:\Users\Neil\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar
Any help would be greatfully reiceved.
Many Thanks Neil
Currently it reports that Visual Studio isn't installed and so won't continue with the installation.
And if it is going to be updated... please fix the known issues with it that people have bothered to report here.
I've created a very simple installer project.
It contains 2 text files. One text file in the Application folder, one in a subfolder.
When I install, I adjust the path to "C:\test setup". This works fine.
The subfolder isn't created when I:
1. Start the .msi installer + click Next
2. Click Browse and choose "C:\" and hit OK
3. Now adjust the path to "C:\test setup" (textually, without using the browse button) and continue the installation.
4. Observe how the subfolder isn't created.
Tested on Windows 7 and 8.1 (both 64 bit).
We were so happy to see a REAL installer back in VS2013, InstallSheild LE is terrible and so crippled its near useless.
I have a simple website to deploy thats built using our build server from the command line - we constantly get the following error.
------ Starting pre-build validation for project 'HelpDeskVSInstaller'
------ ERROR: An error occurred while validating. HRESULT = '8000000A'
------ Pre-build validation for project 'HelpDeskVSInstaller' completed
I have been able to replicate this on my local box by running the installer from the command line:
C:\Windows\system32\cmd.exe /s /c ""C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv" "Payzone.Web.sln" /Rebuild Release /Project VSInstaller"
The installer is able to be built from inside VS2013 IDE. Can you let me know how I can fix this issue?
We have the same error while building from command line. The installer builds OK from GUI.
http://stackoverflow.com/questions/8648428/an-error-occurred-while-validating-hresult-8000000a has an explanation for older Visual Studio versions. I wonder if the problem was addressed in VS 2013 and this extension.
It seems that there is more than 1 person with this issue - Is anyone from Microsoft care to comment on this on how to get around it.
We need to build from the command line and the gui is not an option for us. The installer should work from the command line.
I have removed all the extra lines in the build as per the question / answer on stack overflow referenced by Aurimas above.
This is still not working from the command line.
PLEASE PLEASE PLEASE PLEASE get back to us on a how to fix or if its not going to be fixed so we can start using an installer that does what it says on the tin!!
Same problem here, it's very frustrating and now we can't script Builds from our Build server and therefore will still need to find another way to Build the product. Works fantastically from the UI though, but not really practical to deliver it this way and to be honest it should work the same as in the UI
BUMP BUMP -
Cmon guys someone must be aware of this and have a fix or workaround? I cannot believe that there hasnt even been a response to this from VS Team......
We are basically not going to use Microsoft installers for any future projects because of the current shambles of the recent releases.....
As an update - I did try the workaround posted on the main page with v18.104.22.168 release - and this fixes issues when executing from the command line for the current logged in account - but invoking the same command line parameters from our build process still fails with the HRESULT = '8000000A' error on the same server. Does the registry key have to be added elsewhere when running as a TFS service account?
StlDev: I know your post is old but other people might find this useful.
When your account doesn't experience the problem but the build process does, it is probably because the build process runs under a different windows account. Solution: Log on with the account that your build process uses and apply the registry fix again. Each user has their own HKEY_CURRENT_USER so to speak.
I'm still getting the error "An error occurred while validating. HRESULT = '8000000A'" when running from command line. I have set HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0_Config\MSBuild\EnableOutOfProcBuild to 0.
Using version 22.214.171.124 with VS 2013 update 4.
Any new version coming soon?
I've indeed the same problem with my TFS automated builds.
I try to launch the msi generation by using all the steps described in the following post (http://geekswithblogs.net/jakob/archive/2010/05/14/building-visual-studio-setup-projects-with-tfs-2010-team-build.aspx) but it doesn't work.
My build server currently runs with TFS 2013 and a VS 2013 version having this plugin but it doesn't work.
I have set the HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0_Config\MSBuild\EnableOutOfProcBuild registry value to 0 but it works only if i launch the msi generation through Visual Studio 2013...
It is really a shame that Microsoft doesn't fix this issue when i see that we are a lot to wait for a VALUABLE fix !!!