Replies: 2 comments 1 reply
-
|
@Sweekriti91 hmm, likely a race condition from your change to handle multi-targeting for maui projects, could you take a look? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Probably something in that logic, I'll take a look, thanks for the tag! |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
If you end up doing work for this please create an issue from this discussion to encompass the fix. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
If you find the upgrade assistant is trying to make all your projects into Maui projects, even if they have no xamarin code -- it's because you have multi-targeted frameworks...
In your csproj files, change:
<TargetFrameworks>net48</TargetFrameworks>to
<TargetFramework>net48</TargetFramework>And it will no longer do this...
I didn't dive into the code enough to determine the thinking behind this... but the analysis believes you have a Maui project if it sees any code related to Xamarin.Forms, OR the PLURAL version of "TargetFrameworks" targeting.
Beta Was this translation helpful? Give feedback.
All reactions