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

Unable to add UWP Test project template in VS 2017 #40

Open
HappyTreesDev opened this issue Oct 25, 2017 · 9 comments
Open

Unable to add UWP Test project template in VS 2017 #40

HappyTreesDev opened this issue Oct 25, 2017 · 9 comments

Comments

@HappyTreesDev
Copy link

I am attempting to add NUnit 3 Test Project (Universal Windows) to my solution and I am getting an error every time I try.

I get the error "Unable to copy the file 'project.json' from the project template to the project. Cannot find file "C:\Users\XXXX\AppData\Local\Temp\XXXX\Temp\project.json"

@rprouse
Copy link
Member

rprouse commented Oct 26, 2017

The UWP test project hasn't been updated in awhile. Are you using VS2017? I am not sure it still works there.

@HappyTreesDev
Copy link
Author

HappyTreesDev commented Oct 26, 2017

Yes I am using VS 2017. I decided to use a UWP test project built upon MSTest for now.

@ChrisMaddock
Copy link
Member

I'm fairly sure this worked in the original version of VS 2017 - I wonder if something's changed with the move to dotnet new.

This project's becoming hard to keep up with. 😞 I'm starting to wonder if we should revert the current project to max VS 2015, and do something new with VS 2017. My only reason for not doing that - is that I use this in VS 2017 every day!

@rprouse
Copy link
Member

rprouse commented Oct 27, 2017

I've actually stopped using this in 2017. Whenever I use the snippet in .NET Core projects, it gives me errors about the using statements :(

I really want to see NUnit project templates in VS to compete with the MSTest and xUnit templates that are shipped with VS, but it would be nice if we knew what format we should be using to maintain compatibility going forward.

@sunchunqiang
Copy link

is the issue fixed?

@rprouse
Copy link
Member

rprouse commented Sep 17, 2018

@sunchunqiang no, if the issue was fixed, it would be closed.

@michaelkollmann
Copy link

Are you still investigating this issue or will this just not be fixed?
Is there a workaround?

@ChrisMaddock
Copy link
Member

@michaelkollmann - this project is looked after by a small team of volunteers, who are stretched thinly. We’d welcome a pull request to fix this issue.

@bee-s
Copy link

bee-s commented May 14, 2019

Any update on this ? I can still see that the issue exists.
2 years and still stretched out ? I wish i had all the skills to do this myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants