Comments (5)
.NET Core supports multiple TFMs, and that includes full .NET Framework. In fact, we list netcoreapp1.0
as supported.
from specflow.netcore.
I've been trying to understand what this means for a couple of days now. My understanding (probably totally wrong) was that i could use VS2017 to develop a DOTNET CORE class library and then test it using another DOTNET CORE Test Project, using the SpecFlow.NetCore NuGet package (and modifications to the app.config).
The behaviour appears conflicting.
The .feature.cs gets generated but the Techtalk.Specflow library is missing.
If I include SpecFlow 2.1.0 the build fails with incompatible .net versions.
Am I simply trying to use this in an impossible way or is there a workaround.
We use Specflow universally and a attempting to start a DOTNET CORE project right now and failing miserable.
Thnaks
from specflow.netcore.
I believe it may be the case that we support dotnet core projects, but SpecFlow does not. Perhaps my understanding is flawed though. Us supporting dotnet core doesn't matter if SpecFlow doesn't, of course.
from specflow.netcore.
I created a separate issue for this to be sure I understand what's going on.
from specflow.netcore.
@gegana I got caught up on the technicality of .NET Core and TFMs. We support netcoreapp1.0
however @erik-lundgren is right, it's a moot point if SpecFlow does not. I should have instead referred you to #39. I'll update the README to clarify.
@jimdeane I'll follow up on #46.
from specflow.netcore.
Related Issues (20)
- dotnet core 2.0 support HOT 5
- Tools version is unsupported HOT 3
- Do not hardcode to SpecFlow 2.1.0 HOT 2
- dotnet SpecFlow.NetCore does not work on linux HOT 6
- Scenarios break when the name is too long HOT 1
- Tools version is unsupported HOT 6
- Build fails when there is an existing fake.csproj file (or any extra csproj file) HOT 4
- .net core 2.0 (CLI) HOT 2
- does not work with SpecFlow 2.2.1 HOT 5
- Error in SpecFlow.NetCore tool during print messages HOT 15
- Consider netcoreapp ONLY compatiblity HOT 2
- Attempt to reduce the confusion of the project name HOT 7
- New NuGet package HOT 2
- Building with Mono doesn't generate files. HOT 3
- Use Project's namespace instead of SpecFlow.GeneratedTests HOT 2
- Project not rebuilding when changing .feature file in VS 2017 (15.7.1) HOT 3
- Different result locally and on CI server HOT 3
- When specifying --specflow-path it doesn't detect SpecFlow Version.
- Version for package 'Specflow.NetCore' could not be resolved HOT 3
- Can you please add support for net core 3 HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from specflow.netcore.