-
Notifications
You must be signed in to change notification settings - Fork 548
Closed
Labels
breaking-changeIf an issue or a pull request represents a breaking changeIf an issue or a pull request represents a breaking changedotnetAn issue or pull request related to .NET (6)An issue or pull request related to .NET (6)enhancementThe issue or pull request is an enhancementThe issue or pull request is an enhancement
Milestone
Description
The breaking changes between legacy and dotnet profiles will lead to confusion about which version/profile is being used when looking at project sources (e.g. on GitHub) or when issues are reported.
The later (issues) are often incomplete and simply seeing Xamarin.iOS.dll will immediately lead to the question of "Is this a legacy or dotnet app ?". Such questions always delay bug resolutions.
Updating the name of the assemblies to something else, like a Microsoft prefix, would automatically answer this question for future issues - even if it makes me sad to see Xamarin disappear even more from the code base :(
This is probably not a trivial change wrt msbuild... but now would be the best time to do it
dalexsoto
Metadata
Metadata
Assignees
Labels
breaking-changeIf an issue or a pull request represents a breaking changeIf an issue or a pull request represents a breaking changedotnetAn issue or pull request related to .NET (6)An issue or pull request related to .NET (6)enhancementThe issue or pull request is an enhancementThe issue or pull request is an enhancement