locked
Error 102: Task 'GenerateAppxPackage' failed. When trying to create an .appx

    Question

  • I just put together a small helper tool for our build process as a WinJS project. It runs just fine out of Visual Studio but when trying to create an .appx package for deployment on our CI server, I receive the following error message:

    Error 102 Task 'GenerateAppxPackage' failed. The filename, directory name or volume label syntax is incorrect. (Exception from HRESULT: 0x8007007B)
    C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\AppxPackage\Microsoft.AppXPackage.Targets:1080

    Couldn't find anything on the net, would appreciate any tip you might have.

    All the best
    Marcus

    Tuesday, January 29, 2013 9:43 AM

Answers

  • I found the solution: a <Link> destination for one of the files included a forward slash instead of a backslash. This worked everywhere except when trying to build a package. Replacing the forward slash with a backslash fixed the problem.
    • Marked as answer by Marcus Ilgner Thursday, February 07, 2013 3:20 PM
    Thursday, February 07, 2013 3:20 PM

All replies

  • Hi Marcus,

    Please check the kb article about Error 0x8007232b or 0x8007007B occurs when you try to activate Windows in the following link.

    http://support.microsoft.com/kb/929826

    Hope this helps, thanks.


    Yanping Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, January 31, 2013 2:41 AM
    Moderator
  • I don't see how this problem which pertains to Windows activation and volume keys is in any way related to the problem at hand concerning package building via MSBuild?

    Tuesday, February 05, 2013 9:27 AM
  • I found the solution: a <Link> destination for one of the files included a forward slash instead of a backslash. This worked everywhere except when trying to build a package. Replacing the forward slash with a backslash fixed the problem.
    • Marked as answer by Marcus Ilgner Thursday, February 07, 2013 3:20 PM
    Thursday, February 07, 2013 3:20 PM