-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Force current runtime and arch for GenerateResources on Core msbuild #348
Conversation
<NoLogo>true</NoLogo> | ||
|
||
<!-- Temp Hack: https://github.com/Microsoft/msbuild/issues/720 --> | ||
<!-- Workaround: https://github.com/Microsoft/msbuild/issues/720 --> | ||
<OverrideToolHost Condition=" '$(DotnetHostPath)' != '' and '$(OverrideToolHost)' == ''">$(DotnetHostPath)</OverrideToolHost> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this can be removed. It should no longer be needed/used.
(Obviously leaving it in now doesn't hurt anything. So maybe we should remove it after RC.)
ScenarioBuild a project with .resx file using dotnet CLI with different architecture than target. i.e. dotnet.exe is 32-bit and application being built is 64-bit. BugWorkaroundsSet the following in your project: <PropertyGroup>
<GenerateResourceMSBuildArchitecture>CurrentArchitecture</GenerateResourceMSBuildArchitecture>
<GenerateResourceMSBuildRuntime>CurrentRuntime</GenerateResourceMSBuildRuntime>
</PropertyGroup> RiskLow risk - we only change the property on Core MSBuild and it has no impact on VS builds Performance ImpactNone Regression AnalysisNot a regression, |
@MattGertz for approval |
Approved. |
Update the License
Cancellation for `CreateNewImage` task
Fix #346 with a workaround for dotnet/msbuild#1293
Also cleaning up the nearby usage 'hack' to just 'workaround' ;)
@srivatsn @rainersigwald @NTaylorMullen @dotnet/project-system