Skip to content
This repository was archived by the owner on Apr 22, 2024. It is now read-only.

Xamarin developers can acquire and manage mobile .NET SDKs #4

Open
1 of 2 tasks
maddymontaquila opened this issue Oct 26, 2020 · 2 comments
Open
1 of 2 tasks
Labels
Cost:M Work that requires one engineer up to 2 weeks Priority:0 Work that we can't release without Theme: great client app dev XP User Story A single user-facing feature. Can be grouped under an epic.

Comments

@maddymontaquila
Copy link
Member

maddymontaquila commented Oct 26, 2020

Summary

@maddymontaquila maddymontaquila added the User Story A single user-facing feature. Can be grouped under an epic. label Oct 26, 2020
@chrisntr chrisntr added the Priority:0 Work that we can't release without label Oct 28, 2020
@Redth Redth added the Cost:M Work that requires one engineer up to 2 weeks label Oct 28, 2020
@Aguilex
Copy link

Aguilex commented Dec 10, 2020

Xamarin-Tools comments... there is probably some impact on the IDEs. We will need to support the creation of new .NET 6 projects in the IDEs. We will also need to support existing projects with all SDKs. But it's unclear what the upgrade scenario is, also need to look at Try-Convert as part of the upgrade experience.

@mairaw
Copy link

mairaw commented May 26, 2023

I'm cleaning up the .NET 6 project. Can this issue be closed @maddymontaquila or does it need to be updated?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Cost:M Work that requires one engineer up to 2 weeks Priority:0 Work that we can't release without Theme: great client app dev XP User Story A single user-facing feature. Can be grouped under an epic.
Projects
None yet
Development

No branches or pull requests

5 participants