Replies: 2 comments
-
Okay, further research suggests that this is a problem with NuGet package location configuration. After I've researched more, I'll be back to clarify and apologize. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'll apologize for wasting everyone's time. I do not have an answer, but my problem is not what I think it is. And I'm sure I'm looking for a solution in the wrong direction. I'm closing this and will ask a better question when I figure out what that is. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I ran into the problem as #7989 today using 4.0.5. in my automated builds.
I had just upgraded from 4.0.2. My builds with this release worked just fine. After the upgrade to 4.0.5 I found that I now get a lot of these WIX0200 errors.
I went looking for my dependencies to see what I might learn.
I seems that the extension packages are not placed into the solution project packages directory. Only the Mba.Core and Host libraries are present there. As I look at the project dependencies in the solution with VS2022, I find that my extension packages are stored in a new place. The [User].nuget\packages folder. And the reason I does not find my packages during the automated build operation is because the user that I develop the project with is different than the one used in the automated build. So the project dependency references folders that do not exist on my build server.
I have confirmed that the Target "Restore" operation does indeed download the extension libraries into the build user .nuget\packages\wixtoolset.bal.wixest\v4.0.5 folder. It just happens that the project dependency references point to my developer user that does not exist on the build server.
Should these extensions be placed into the project's packages folder rather than the build users .nuget\packages folder?
Is this a bug, or did I do something wrong when I upgraded from 4.0.2 to 4.0.5?
Beta Was this translation helpful? Give feedback.
All reactions