Open rainersigwald opened 8 years ago
The MSBuild preprocessor makes its output harder to read by collapsing whitespace inside strings (probably due to XML parsing or output). It'd be nice if it kept things as
<Target Name="XamlPreCompile" Inputs="$(MSBuildAllProjects); @(Compile); @(_CoreCompileResourceInputs); $(ApplicationIcon); $(AssemblyOriginatorKeyFile); @(ReferencePath); @(CompiledLicenseFile); @(LinkResource); @(EmbeddedDocumentation); $(Win32Resource); $(Win32Manifest); @(Page); @(ApplicationDefinition); @(CustomAdditionalCompileInputs); $(ResolvedCodeAnalysisRuleSet)" Outputs="@(DocFileItem); @(XamlIntermediateAssembly); @(_DebugSymbolsIntermediatePath); $(NonExistentFile); @(CustomAdditionalCompileOutputs)" Returns="" DependsOnTargets="$(CoreCompileDependsOn)" Condition="'@(Page)' != '' Or '@(ApplicationDefinition)' != ''" >
instead of turning it into
<Target Name="XamlPreCompile" Inputs="$(MSBuildAllProjects);
 @(Compile);
 @(_CoreCompileResourceInputs);
 $(ApplicationIcon);
 $(AssemblyOriginatorKeyFile);
 @(ReferencePath);
 @(CompiledLicenseFile);
 @(LinkResource);
 @(EmbeddedDocumentation);
 $(Win32Resource);
 $(Win32Manifest);
 @(Page);
 @(ApplicationDefinition);
 @(CustomAdditionalCompileInputs);
 $(ResolvedCodeAnalysisRuleSet)" Outputs="@(DocFileItem);
 @(XamlIntermediateAssembly);
 @(_DebugSymbolsIntermediatePath);
 $(NonExistentFile);
 @(CustomAdditionalCompileOutputs)" Returns="" DependsOnTargets="$(CoreCompileDependsOn)" Condition="'@(Page)' != '' Or '@(ApplicationDefinition)' != ''">
This happens (or can happen) when updating a NuGet package.
SDK-style csproj with net48 target: Fix anytime soon? Or is it tracked elsewhere?
The MSBuild preprocessor makes its output harder to read by collapsing whitespace inside strings (probably due to XML parsing or output). It'd be nice if it kept things as
instead of turning it into