UPCOMING EVENT: IFSEC (Booth IF3011) - ExCel, London, UK

Jenkins Build Error with .vdproj

If you’re seeing this issue:

—— Starting pre-build validation for project ‘XPressBadgeInstaller’ ——
ERROR: An error occurred while validating. HRESULT = ‘8000000A’
—— Pre-build validation for project ‘XPressBadgeInstaller’ completed ——

The fix is the following:

If you face the error message “An error occurred while validating. HRESULT = ‘8000000A’” while building Visual Studio setup project from command line in Visual Studio 2012 or above IDE environment, the reason is because the new IDEs do not support build outside the own process.

 

But there is a tweak which will help you to enable the same and you will now be allowed to build the MSI setup project from the command line itself.

 

Solution: An error occurred while validating. HRESULT = '8000000A' (www.kunal-chowdhury.com)

 

The solution towards “An error occurred while validating. HRESULT = ‘8000000A’” error message is very simple. It’s just a registry tweak that you have to perform as a workaround.

 

For this to work, open your Windows Registry with administrative privilege and navigate to the following registry key path: “HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\11.0_Config\MSBuild” for Visual Studio 2012 IDE or, to the registry path “HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\12.0_Config\MSBuild” for the Visual Studio 2013. If you are using Visual Studio 2015, then the registry key that you have to navigate to is “HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\14.0_Config\MSBuild”.

 

Registry entry to enable out of proc build in Visual Studio (www.kunal-chowdhury.com)

 

In that path, create a DWORD key with the name “EnableOutOfProcBuild” and set it’s value to “0” (zero). Now restart the build process from the command line and everything will be working as you expected.

 

Hope this small Tips & Tricks was helpful. Do let me know, if this helped you. Stay tuned to my blog for new articles, tips. Don’t forget to read my other posts by the time I write and publish a new post. Have a great day ahead!

That’s from here:

http://www.kunal-chowdhury.com/2016/07/visual-studio-error-code-8000000A.html#pTySk1QU90X9lYw6.97

 

 

The registry key is available here:

Some implications of the new modular setup of Visual Studio 2017 for VSX developers

But not only that. Visual Studio 2017 is also much more isolated and resilient. It doesn’t install Visual Studio assemblies in the Global Assembly Cache (GAC) and it doesn’t use for the most part the main Windows Registry. In the past (since VS 2010, see my post The strange case of the registry key HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0_Config\Projects\{C8D11400-126E-41CD-887F-60BD40844F9E}), Visual Studio redirected HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\<version> to HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\<version>_Config, to allow installation of extensions through .pkgdef files without admin rights, etc. Now, VS 2017 uses its own private registry. See how empty is the regular HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\15.0 key on my machine and notice that there is no 15.0_Config key:

vs2017config

Instead, the VS 2017 private registry is stored in your AppData folder:

privateregistry

Fortunately, you can use regedit.exe to load a private hive. You need to select the HKEY_USERS node, and click the File > Load Hive… menu. You select the privateregistry.bin file, give a name to the hive (I entered “VS2017PrivateRegistry”) and now you can see the 15.0<id>_Config key populated as usual (note: use File > Unload Hive when done):

vs2017privateconfig