An error occurred while validating vdproj

---

21-Feb-2020 03:33

For more information, see the migration report:2016-06-21T.5711249Z C:\a

For more information, see the migration report:2016-06-21T.5711249Z C:\a\1\s\Source\Upgrade Log.htm2016-06-21T.7821256Z ========== Rebuild All: 0 succeeded, 0 failed, 0 skipped ==========As a wrote in my question, I have five projects in my solution. Hi @Dafna - you should always install VS on the build machine.Main project is a WPF application, three external libraries and an installer project. As far as I understand licensing, you can install the "highest" SKU you have licenses to on the build machine, and as long as no user uses that VS (other than the build agent) you don't actually pay for a license.

||

For more information, see the migration report:2016-06-21T.5711249Z C:\a\1\s\Source\Upgrade Log.htm2016-06-21T.7821256Z ========== Rebuild All: 0 succeeded, 0 failed, 0 skipped ==========As a wrote in my question, I have five projects in my solution. Hi @Dafna - you should always install VS on the build machine.

Main project is a WPF application, three external libraries and an installer project. As far as I understand licensing, you can install the "highest" SKU you have licenses to on the build machine, and as long as no user uses that VS (other than the build agent) you don't actually pay for a license.

First try to build my setup project .vdproj from visual studio 2015. Detecting file changes for project ' Database.sqlproj'...

Deserialization has been completed for project ' Database.sqlproj'.

So there's really no reason not to install VS on the build machine. Hi @Neslihan The only thing I can think of is that the command line VS you are using isn't matching the GUI that you're successfully building from.

Hi @jafuentes - looks like you're source-controlling an older version of the solution - say VS 2010, and then you have a newer version of VS on the build server, say VS 2015. But I get an ERROR: An error occurred while validating. HRESULT = '8000000A' I also get this error from TFSBuild ... You'll have to get it working from the command line first, otherwise the build will never work.

\s\Source\Upgrade Log.htm2016-06-21T.7821256Z ========== Rebuild All: 0 succeeded, 0 failed, 0 skipped ==========As a wrote in my question, I have five projects in my solution. Hi @Dafna - you should always install VS on the build machine.Main project is a WPF application, three external libraries and an installer project. As far as I understand licensing, you can install the "highest" SKU you have licenses to on the build machine, and as long as no user uses that VS (other than the build agent) you don't actually pay for a license.

You’ll need to configure the build to compile the entire solution first, and then invoke Visual Studio to create the setup package.

Considering the high risk of solving the problem, and the fact that Visual Studio Installer projects have been deprecated in Visual Studio 2010 (see “Visual Studio Setup and Deployment Projects”: it is very unlikely that this issue will be fixed.

Remember when Visual Studio had a setup project template? Then you moved to Wi X and after learning it for 3 months and still being confused, you just moved to Web Apps?

Hello everyone, I’ve had a few cases already, where our customers came across a rare problem: They were building Visual Studio Installer projects with Team Build of Team Foundation Server 2010 and the build failed with the error: “An error occurred while validating. When running the build process again, it usually succeeded.

The problem was almost impossible to reproduce and unpredictable in its manner: The customers had several setup projects in their solution and the error appeared seemingly random during the compilation of each of them.

After resurrecting some old setup projects I decided I needed to build them in batch scripts.

---