-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VMR Stage2 build fails with error MSB1006: Property is not valid.
#4579
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Not sure why it's complaining about setting an MSBuild property. That is set here: https://github.com/dotnet/source-build-externals/blob/f08c68bfc6c6e065f72e56dcd4dc15d3ea1f43a4/repo-projects/application-insights.proj#L20 Here's the command it's failing on:
That's identical to the command in stage 1. Looking at the diff of the VMR comparing when this was working to when this failed, nothing clearly stands out as the culprit. Could it possibly be caused by dotnet/sdk#42240? /cc @baronfel |
The only thing I could see that could perhaps be triggering here is this change to how we forward 'empty' properties to MSBuild from the CLI. This is an odd property anyway - is there any insight into why it is empty? |
cc @rainersigwald for thoughts here on MSBuild property syntax |
It's set by default in the application insights source. For source build, we want its value to be cleared. I don't have information on why we need it cleared. |
potential workaround might be to set an explicit empty string value via |
|
Very odd - there were some tests in the SDK side that didn't pass until I changed that. I'll take a look at getting that fixed soon, then - @rainersigwald I'll ping you on that PR to make sure our understanding of the MSBuild property syntax is correct. In the meantime @mthalman can you try the explicit-quotes suggestion and see if that unblocks you? |
Getting the same error using quotes: build (internal link) |
ok, then we just have to wait until I can force the linked fix through SDK CI (which is being very intransigent on the .NET Framework leg). |
Ok, the proposed fix just merged to main in the SDK. |
Fixed with dotnet/sdk#43004 |
Failing build (internal Microsoft link)
VMR Stage 2 legs are building failed with below message:
The text was updated successfully, but these errors were encountered: