[release/6.0] Fix Xamarin assembly names in HttpClientHandler #64391
Conversation
Update to match the new names from dotnet/macios#13847
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsBackport of #64385 to release/6.0 /cc @akoeplinger Customer ImpactTestingRisk
|
|
Tagging subscribers to 'arch-android': @steveisok, @akoeplinger Issue DetailsBackport of #64385 to release/6.0 /cc @akoeplinger Customer ImpactThe iOS SDK team is renaming their assemblies from Xamarin.* to Microsoft.*. We use reflection in runtime to call into the iOS http handlers, so we need to change our reference to the assembly names as well. TestingManual testing with a MAUI app and an updated runtime RiskLow
|
|
Tagging subscribers to 'os-ios': @steveisok, @akoeplinger Issue DetailsBackport of #64385 to release/6.0 /cc @akoeplinger Customer ImpactThe iOS SDK team is renaming their assemblies from Xamarin.* to Microsoft.*. We use reflection in runtime to call into the iOS http handlers, so we need to change our reference to the assembly names as well. TestingManual testing with a MAUI app and an updated runtime RiskLow
|
leecow
added
Servicing-approved
ghost
locked as resolved and limited conversation to collaborators
Backport of #64385 to release/6.0
/cc @akoeplinger
Customer Impact
The iOS SDK team is renaming their assemblies from Xamarin.* to Microsoft.*. We use reflection in runtime to call into the iOS http handlers, so we need to change our reference to the assembly names as well.
Testing
Manual testing with a MAUI app and an updated runtime
Risk
Low