Support for dotnet core 2.0 about tickspec HOT 10 CLOSED

The .NET core does not support all the methods needed for code emitting. However, I guess that it should be possible to create a lightweight version for netstandard (without code emit) and full version for net45.

from tickspec.

Are there any plans to proceed with dotnet core support? how significant or involved is the effort for the lightweight version (if I wanted to contribute)?

from tickspec.

It feels relatively simple to do a .NET Standard version of TickSpec if you exclude support for debugging feature files. I have done a proof of concept some time ago in this branch https://github.com/michalkovy/tickspec/commits/feature/DotNetCore

The reason debugging feature files is harder to solve is because I haven't found at the time replacement for DefineDocument
https://docs.microsoft.com/en-us/dotnet/api/system.reflection.emit.modulebuilder.definedocument?view=netframework-4.7.2
and MarkSequencePoint
https://docs.microsoft.com/en-us/dotnet/api/system.reflection.emit.ilgenerator.marksequencepoint?view=netframework-4.7.2

My feeling is that even though debugging feature files is nice feature there are good ways how to work differently, so it makes great sense to create .NET Standard version even without the feature.

from tickspec.

I agree, you'd still be able to debug underneath the features right? at each step definition.

I'd love to see this updated with Core support, what would it take to make that a reality at this point? I'm looking through your branch some

from tickspec.

Good job, It'll be great if you publish a new nuget version.

from tickspec.

With this closed, will a nuget be published in the near future?

from tickspec.

@bartelink I think we currently don't have any known defect - so, like suggested, can you please publish a nuget package? I would consider to make it a preview first. Thanks

from tickspec.

Hey @michalkovy, apologies for the delay - I clearly need to enable one of you de-facto maintainer guys to publish (perhaps by automating the upload, sequestering credentials somewhere and rigging the CI such that a tag on a commit in master is what grants the right to publish under a name?). I'll get to that either today or tomorrow (my work and side project time slots are both blocked and my WIP limit is 2 on my kanban board :( ) cc @enricosada @gusty

from tickspec.

cc @tylerhartwig Please bear with us while we get this sorted - this is on me and it really is not a good state of affairs for the production of nugets to lag in this way. I know this is not an answer, but can you self service by downloading nupkgs from the CI outputs for now in the interim ?

from tickspec.

@bartelink thanks, I have a setup that works locally for the time being. I'm using this on a side project, so it's not super urgent for me to get it all in CI yet. Glad to see this come to standard though, it's a really awesome framework.

from tickspec.