-
Notifications
You must be signed in to change notification settings - Fork 19
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
feat (NetCoreSupport): Continue work done on PR #78 #80
Conversation
Relates to #77 |
Oh nice, is this ready for review/merge? (I'm not an admin, just curious as I'd like to update it in Shouldly) |
@josephwoodward It should be good to merge. Just after a maintainer to review/commit. Funny, my prime motivation was to update this for Shouldly. I am unsure if this project is abandoned, the last commit was a few years ago. ? If no response from maintainers can fork and publish a forked Nuget package but this is not an ideal outcome. |
@jafin I think that's a good idea, at least until this gets merged. |
Hi. I'm a TestStack maintainer. I'll take a look at this over the weekend and try to get it merged and released |
Oh great, thanks @mwhelan! |
@mwhelan Sorry I misunderstood the versioning process. DotNet pack wasn't updating the version. I pushed another PR which should correct it. #81 |
Thanks @jafin . There are a couple of deployments in appveyor - one to create GitHub release notes and one to push to NuGet. They might be quite out of date after 4 years... I'll tag this as v4.0.0 and try to release. I would like to upgrade Autofac to 5.1.2. There were breaking changes in Autofac between version 4 and 5 and I'd like to be up-to-date with the latest version. Let me know if you think there might be any issues with doing that. |
@mwhelan thanks, If I get time this arvo I can attempt the upgrade to Autofac 5.1.2, I'll do another PR if so. |
I'm actually just doing it now. All the tests compile fine with it. |
Continue work done on PR #78 to get net core builds.