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

Xamarin developers can leverage a CLI try-convert tool to move basic Xamarin projects to the new project system #9

Open
maddymontaquila opened this issue Oct 26, 2020 · 2 comments
Open

Xamarin developers can leverage a CLI try-convert tool to move basic Xamarin projects to the new project system #9

maddymontaquila opened this issue Oct 26, 2020 · 2 comments
Labels
Cost:M Work that requires one engineer up to 2 weeks Priority:1 Work that is critical for the release, but we could probably ship 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

No description provided.

@maddymontaquila maddymontaquila mentioned this issue Oct 26, 2020
Open
15 tasks
@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:1 Work that is critical for the release, but we could probably ship 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 will take this work on.

@BretJohnson
Copy link
Member

As for scope of this tool, David said "also yes csproj is the primary conversion. IF we/you can augment try-convert to also do namespaces, that'd be delicious"

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Cost:M Work that requires one engineer up to 2 weeks Priority:1 Work that is critical for the release, but we could probably ship without Theme: great client app dev XP User Story A single user-facing feature. Can be grouped under an epic.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@chrisntr @BretJohnson @Redth @maddymontaquila @Aguilex