-
Notifications
You must be signed in to change notification settings - Fork 51
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
Error when installing the Reqnroll template via command line #22
Labels
bug
Something isn't working
Comments
I also got the same error mentioned here. |
This seems to be related to dotnet/msbuild#3468 |
gasparnagy
added a commit
that referenced
this issue
Feb 14, 2024
Seems to be working. Will be released soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reqnroll Version
1.0.0
Which test runner are you using?
xUnit
Test Runner Version Number
--
.NET Implementation
.NET 8.0
Test Execution Method
Visual Studio Test Explorer
Content of reqnroll.json configuration file
It did not reach the .NET version configuration stage, nor the test executor, nor creating the reqnrollfile. were filled in as it is a mandatory field
Issue Description
Error when installing the Reqnroll template via command line
Steps to Reproduce
Hey! I was able to successfully create a project with Reqnroll template via Visual Studio, but when doing the same via vs code, via the command line, when installing Reqnroll template with the command 'dotnet new install Reqnroll.Templates.DotNet', I got an error stating that it was already the template existed, making reference to Specflow. I uninstalled the Specflow template, restarted the machine and tried the installation again, getting the following error:
image
and, as a result, the template was not installed, generating an error when executing the command ´dotnet new reqnroll-project´:
image
dotnet new list:
image
Are there any other steps I need to do or could it be an error in the template script?
Link to Repro Project
No response
The text was updated successfully, but these errors were encountered: