-
Notifications
You must be signed in to change notification settings - Fork 458
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
Castle.Core 4.x compatibility #227
Comments
Yes, we are currently working to move our build processes to the new VS2017 tooling and move from TeamCity to AppVeyor. Once this work is done I'm planning to get a new release out that upgrades to Castle Core 4.0, is this currently blocking you? |
Not blocking per se, but Moq > v4.7.0 depends on Core v4.x, so I'm stuck with lower versions until this is released. Do you have a timeline? |
Ah, I thought Moq was still ILMerging Castle.Core.dll into Moq.dll, it looks like they are no longer doing that. Timeline... should be in the next 2 weeks. |
ILMerge doesn't work on .NET Core so we moved to depend on NuGet packages for both .NET Framework and .NET Core. |
NSubstitute 2 would appear to be in same boat as Moq, it now has Castle.Core >= 4 as a dependency where is had none in 1.* |
Opened PR #235 |
@jonorossi so is this resolved? |
@gregsdennis - Sorry I am jumping here, but yes it was resolved. We are preparing a release. Any day now :) |
In #161 a bandaid was applied to the Nuget package to prevent upgrades to Castle.Core 4.x.
Are we going to see a version that is compatible?
The text was updated successfully, but these errors were encountered: