B
BullyOwner
Guest
I'm doing automated builds under TeamCity and I had to add the following to all my .csproj files in order to avoid the unnecessary rebuild issue caused by TeamCity overriding and cleaning the %temp% folder for each build:
<TargetFrameworkMonikerAssemblyAttributesPath>
$([System.IO.Path]::Combine('$(IntermediateOutputPath)','$(TargetFrameworkMoniker).AssemblyAttributes$(DefaultLanguageSourceExtension)'))
</TargetFrameworkMonikerAssemblyAttributesPath>
Unfortunately, this now has another unwanted side effect. Now, when I update the .csproj files to update the target framework:
For example:
<TargetFrameworkVersion>v4.5</TargetFrameworkVersion>
to
<TargetFrameworkVersion>v4.6</TargetFrameworkVersion>
The .AssemblyAttributes file DOES NOT get re-generated.
How can this be fixed?
Continue reading...
<TargetFrameworkMonikerAssemblyAttributesPath>
$([System.IO.Path]::Combine('$(IntermediateOutputPath)','$(TargetFrameworkMoniker).AssemblyAttributes$(DefaultLanguageSourceExtension)'))
</TargetFrameworkMonikerAssemblyAttributesPath>
Unfortunately, this now has another unwanted side effect. Now, when I update the .csproj files to update the target framework:
For example:
<TargetFrameworkVersion>v4.5</TargetFrameworkVersion>
to
<TargetFrameworkVersion>v4.6</TargetFrameworkVersion>
The .AssemblyAttributes file DOES NOT get re-generated.
How can this be fixed?
Continue reading...