Default ProduceReferenceAssembly to true
See original GitHub issueGet better incremental build performance by opting in to reference assembly based builds by defaulting ProduceReferenceAssembly
to true.
Since this is a behaviour change, it may be good to do it in 3.0 and for SDK projects only.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:8
- Comments:24 (22 by maintainers)
Top Results From Across the Web
Write reference assemblies to IntermediateOutputPath - .NET
In .NET 5, the ProduceReferenceAssembly property was introduced and defaulted to true for net5.0 and later applications. With this change, many ...
Read more >How to produce ReferenceAssemblies with dotnet
I'm struggling with the following problem: I added <ProduceReferenceAssembly>true</ProduceReferenceAssembly> to my CSPROJ (and I also tried ...
Read more >Every time I make a change in code, does not take the ...
Forms default template project has the <ProduceReferenceAssembly>true</ProduceReferenceAssembly> MSBuild property set in the .
Read more >Fix unable to find *.deps.json for unit tests in .NET 5
Solution 1. Set ProduceReferenceAssembly to false · Solution 2. Ignore the /ref/ folder in your test tasks in Azure DevOps · Tobias Zimmergren....
Read more >Tips & Tricks to improve your .NET Build Setup with MSBuild
MSBuild is the powerful - now open source - build system used in all .NET Builds. It has a language of its own...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
In our sync-up, we decided to go ahead with enabling this by default for .NET 5.0 and higher.
Ok, I did a small proof-of-concept that things are still broken.
MixedSolutionWithRefAssemblies.zip
This solution has:
The unit test project tests library functionality by calling the app that calls the library.
That’s because the fast-up-to-date check in csproj doesn’t understand that it needs to tell MSBuild to build the app even though its direct input (the
lib.dll
reference assembly) hasn’t changed.CoreCompile
will be skipped, but the build will copy the implementation assembly along, so that the updated implementation is available at runtime.