UWP test assembly build failing

pascal's Avatar

pascal

09 Sep, 2015 02:41 PM

Hi,

I have an error saying that "OutputPath" is not defined when build an UWP assembly. When building it locally using msbuild (in command-line prompt) it builds.
The failed build is here: https://ci.appveyor.com/project/picrap/mradvice/build/master-132
I probably missed something somewhere, but what?

Thanks for any help.

  1. Support Staff 1 Posted by Feodor Fitsner on 09 Sep, 2015 05:58 PM

    Feodor Fitsner's Avatar

    It looks like the problem comes from nuget restore command.

    Try installing nuget 3.2-rc with this command:

    appveyor DownloadFile https://dist.nuget.org/win-x86-commandline/v3.2.0-rc/nuget.exe
    

    or previous nuget 2.8.5 with:

    appveyor DownloadFile https://www.nuget.org/nuget.exe
    

    to see if that helps.

  2. 2 Posted by pascal on 09 Sep, 2015 07:17 PM

    pascal's Avatar

    Hi Feodor,

    you are probably the fastest support on earth!
    The idea was good and I tried both options which seemed to solve the specific error, unfortunately, another package doesn't work anymore (TransformOnBuild doesn't transform on build).

    The most frustrating thing is that I am unable to reproduce this in local, so this is very hard to debug.

  3. Support Staff 3 Posted by Feodor Fitsner on 09 Sep, 2015 07:20 PM

    Feodor Fitsner's Avatar

    What the error is that? Where do you get it?

  4. 4 Posted by pascal on 09 Sep, 2015 07:22 PM

    pascal's Avatar

    See at https://ci.appveyor.com/project/picrap/mradvice/build/master-134
    The ProductInfo.cs file is missing because it was not generated from ProductInfo.tt by Clarius.TransformOnBuild.

  5. Support Staff 5 Posted by Feodor Fitsner on 09 Sep, 2015 07:23 PM

    Feodor Fitsner's Avatar

    I see. Is it like T4? How does it usually work? Is there something missing on build workers?

  6. 6 Posted by pascal on 09 Sep, 2015 07:26 PM

    pascal's Avatar

    Yes, it is a T4 generator, but instead of generating files on source modification, it generates them on build.
    It was working until here (all my previous builds which were successful are using it).

  7. Support Staff 7 Posted by Feodor Fitsner on 09 Sep, 2015 07:31 PM

    Feodor Fitsner's Avatar

    Btw, could you try rebuilding the last successful build: https://ci.appveyor.com/project/picrap/mradvice/build/master-130 to see if that's environment change?

  8. 8 Posted by pascal on 09 Sep, 2015 07:37 PM

    pascal's Avatar

    It still builds :)

  9. Support Staff 9 Posted by Feodor Fitsner on 09 Sep, 2015 08:42 PM

    Feodor Fitsner's Avatar
  10. 10 Posted by pascal on 10 Sep, 2015 05:43 PM

    pascal's Avatar

    II made a few tests, and installing another nuget that the version provided breaks the Clarius.TransformOnBuild package.
    So until there is an official nuget release, I'll keep my changes in a separate branch.

  11. 11 Posted by pascal on 13 Sep, 2015 07:02 PM

    pascal's Avatar

    I found a fix: I simply need to add the following line
        <OutputPath>bin\Release\</OutputPath>
    to the UWP csproj files, in the first <PropertyGroup> node.

  12. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:00 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac