You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow the following rules:
- SOF (_Start Of File_) Imports,
- Core properties, Package properties, build properties,
- Build items, Resource items, Content items, Misc. items,
- In-place Imports, Choose (_elements within follows outer sort order_)
- `ProjectReference` items, `PackageReference` items,
- Targets and Properties and Items close to said Targets,
- EOF (_End Of File_) Imports.
Where there's a condition by target properties, we should group them together under `Choose`.
For multiple target values, we should sort them by the order in which they are defined.
And the order in which they should be defined is either ascending or descending in terms of compatibility layering.
<!-- If the source generators are disabled, also emit a warning. This would've been produced by MSBuild itself as well, but
39
-
emitting this manually lets us customize the message to inform developers as to why exactly the generators have been
40
-
disabled, and that the rest of the MVVM Toolkit will still keep working as intended, just without additional features. -->
39
+
<!--
40
+
If the source generators are disabled, also emit a warning. This would've been produced by MSBuild itself as well, but
41
+
emitting this manually lets us customize the message to inform developers as to why exactly the generators have been
42
+
disabled, and that the rest of the MVVM Toolkit will still keep working as intended, just without additional features.
43
+
-->
41
44
<Warning Condition ="'$(CurrentCompilerVersionIsNotNewEnough)' == 'true'"Text="The MVVM Toolkit source generators have been disabled on the current configuration, as they need Roslyn 4.x in order to work. The MVVM Toolkit will work just fine, but features relying on the source generators will not be available."/>
0 commit comments