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.

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

MSTest project type not yet supported #997

Open
TheCakeMonster opened this issue Jan 5, 2022 · 4 comments
Open

MSTest project type not yet supported #997

TheCakeMonster opened this issue Jan 5, 2022 · 4 comments
Labels
community reported Triaged Label to show that UA team has triaged this issue.

Comments

@TheCakeMonster
Copy link

Problem encountered on https://dotnet.microsoft.com/en-us/platform/upgrade-assistant/tutorial/install-upgrade-assistant
Operating System: windows

Version: 0.3.261602+efb3cc30a24e699e6e4337f263a2b9478f04f618

I tried to upgrade a .NET Framework unit test project using MSTest to the new SDK-style format using the latest version of upgrade-assistant today and the request to perform the upgrade was rejected because the project type is not yet supported.

It would be great if this additional project type were able to be supported by the upgrade-assistant global tool, as this would save people who are migrating old .NET Framework test projects to support .NET Core a lot of time.

@twsouthwick
Copy link
Member

Can you provide a sample of what the project file looks like?

@twsouthwick
Copy link
Member

Possibly related: dotnet/try-convert#421

@TheCakeMonster
Copy link
Author

Can you provide a sample of what the project file looks like?

Yes, of course. Sorry for the delay. It's on GitHub at the following location. (This is the exact commit I tried it on, just in case we change this file in the next few days)

https://github.com/MarimerLLC/csla/blob/a050eb789bf92ed8acc23abe287f2704922d8d79/Source/Csla.test/csla.test.csproj

@sunandabalu sunandabalu added community reported Triaged Label to show that UA team has triaged this issue. labels Feb 8, 2022
@sla89
Copy link

sla89 commented May 23, 2023

Same issue here - is there any workaround available until this is fixed? Thank you :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community reported Triaged Label to show that UA team has triaged this issue.
Projects
None yet
Development

No branches or pull requests

4 participants