Jan Krivanek
@v-ainigao have you been able to verify if the localizations were propagated properly?
Very nice and valuable overview! Looking forward the addition of host files parameters altering functionality
Another failed CI run: https://github.com/dotnet/templating/pull/5314/checks?check_run_id=8514891843
@Drizin Good point! Changing `Option` to `Option` in the above sample resolved the exception. Though it still doesn't produce the expected completion (empty result is returned).
Closing as work in context of 7.0 was done. Tracking the next iteration ideas in a new item: https://github.com/dotnet/templating/issues/5705
@GangWang01 - please have a look what might be the options for this problem and list some here
Let's use some structured info (not a textual info in BuildMessageEventArgs etc.). We possibly might reuse `PropertyReassignmentEventArgs` (where previous value is `null`) - but probably not a good idea as...
+1 on prototyping and then measuring on a reasonably sized project (OrchardCore e.g.) If there is a measurable difference in overall build time and binlog size, then we can think...
Investigated with @rainersigwald: **tl;dr;:** Strictly speaking `ReferenceOutputAssembly` is behaving as it should (preventing the output assembly to be referenced and pulled to output folder by referencing project). However it might...
@jhudsoncedaron It works - see https://github.com/dotnet/msbuild/issues/4371#issuecomment-1195950719 for more context. Btw. I'm seeing same behavior building from net7 and net6 (6.0.406), while targetting both of those.