An error occurred while validating hresult

Let’s walk through creating a simple build definition to build a vdproj.

Something is failing to upgrade to the newer version of VS (perhaps a VS component isn't installed) so try to upgrade the solution on your desktop to the same version of VS that is on your build machine. HRESULT = '8000000A' I check my agent service user(my user name is TFSReport) . Make sure you're calling the correct to build the solution.

I connect to server with this user and add key to the specified registry address. Hi I am having trouble building the solution that when I run it on command line this is what I get Deserializing the project state for project ' Database.sqlproj'...

You can run tests or scripts or anything else during the build (for ease I delete the unit test task in the above example). I wrote a post asked about this problem here [ microsoft.com/.../problems-building-setup-project-in-visual-studio-team-services ]. I followed the steps but I got an error during the compilation process.

I now have a successful build: And the msi is in my drop, ready to be deployed in Release Management: Happy setup building! This is my log:2016-06-21T.6466919Z Creating directory C:\a

Something is failing to upgrade to the newer version of VS (perhaps a VS component isn't installed) so try to upgrade the solution on your desktop to the same version of VS that is on your build machine. HRESULT = '8000000A' I check my agent service user(my user name is TFSReport) . Make sure you're calling the correct to build the solution.

I connect to server with this user and add key to the specified registry address. Hi I am having trouble building the solution that when I run it on command line this is what I get Deserializing the project state for project ' Database.sqlproj'...

You can run tests or scripts or anything else during the build (for ease I delete the unit test task in the above example). I wrote a post asked about this problem here [ microsoft.com/.../problems-building-setup-project-in-visual-studio-team-services ]. I followed the steps but I got an error during the compilation process.

I now have a successful build: And the msi is in my drop, ready to be deployed in Release Management: Happy setup building! This is my log:2016-06-21T.6466919Z Creating directory C:\a\1\s\src2016-06-21T.6476927Z Executing the following command-line.

The project ' Database.sqlproj' will close once model building has paused.

||

Something is failing to upgrade to the newer version of VS (perhaps a VS component isn't installed) so try to upgrade the solution on your desktop to the same version of VS that is on your build machine. HRESULT = '8000000A' I check my agent service user(my user name is TFSReport) . Make sure you're calling the correct to build the solution.I connect to server with this user and add key to the specified registry address. Hi I am having trouble building the solution that when I run it on command line this is what I get Deserializing the project state for project ' Database.sqlproj'...You can run tests or scripts or anything else during the build (for ease I delete the unit test task in the above example). I wrote a post asked about this problem here [ microsoft.com/.../problems-building-setup-project-in-visual-studio-team-services ]. I followed the steps but I got an error during the compilation process.I now have a successful build: And the msi is in my drop, ready to be deployed in Release Management: Happy setup building! This is my log:2016-06-21T.6466919Z Creating directory C:\a\1\s\src2016-06-21T.6476927Z Executing the following command-line.The project ' Database.sqlproj' will close once model building has paused.

\s\src2016-06-21T.6476927Z Executing the following command-line.

The project ' Database.sqlproj' will close once model building has paused.

Serializing the project state for project ' Database.sqlproj'...After resurrecting some old setup projects I decided I needed to build them in batch scripts.I remember several years struggling for an hour to find the correct syntax of the command required to batch build a vdproj file.For more information, see the migration report:2016-06-21T.5711249Z C:\a

Serializing the project state for project ' Database.sqlproj'...After resurrecting some old setup projects I decided I needed to build them in batch scripts.I remember several years struggling for an hour to find the correct syntax of the command required to batch build a vdproj file.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.Install Shield and other 3rd party paid installer products. You can run tests or scripts or anything else during the build for ease I delete the unit test task in the above example.

||

Serializing the project state for project ' Database.sqlproj'...

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

I remember several years struggling for an hour to find the correct syntax of the command required to batch build a vdproj file.

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.

Install Shield and other 3rd party paid installer products. You can run tests or scripts or anything else during the build for ease I delete the unit test task in the above example.

\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.Install Shield and other 3rd party paid installer products. You can run tests or scripts or anything else during the build for ease I delete the unit test task in the above example.