Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problem Statement 2: Upgrading projects from .shproj to .csproj is unsatisfactory and lacks sufficient documentation and support. #1600

Open
jstedfast opened this issue Sep 10, 2024 · 1 comment
Open

Problem Statement 2: Upgrading projects from .shproj to .csproj is unsatisfactory and lacks sufficient documentation and support. #1600

jstedfast opened this issue Sep 10, 2024 · 1 comment
Assignees
@jstedfast @DianaSoltani

Comments

@jstedfast
Copy link
Member

Feedback: "The actual platform head upgrades were generally fine; the old ".shproj" upgrade was a completely unsatisfactory experience. To use the upgrade assistant, you need to have your project upgraded to the latest XF version along. .Shproj files aren't a supported experience for the upgrade assistant due to this. I could not find much documentation or stack overflow answers on how to properly migrate from these so there was a lot of trial and error in determining what I needed to upgrade from shproj to csproj. There are unanswered questions on stack overflow and copilot didn't get me any useful responses on this."
@jstedfast jstedfast transferred this issue from dotnet/maui Sep 11, 2024
@jstedfast
Copy link
Member Author

We'll be tracking this internally with this bug item: https://dev.azure.com/devdiv/DevDiv/_workitems/edit/2250101

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jstedfast jstedfast

@DianaSoltani DianaSoltani

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jstedfast @DianaSoltani