Skip to content
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

Support for targeting .NET Core #261

Closed
2MmYxoeg opened this issue Nov 26, 2018 · 4 comments
Closed

Support for targeting .NET Core #261

2MmYxoeg opened this issue Nov 26, 2018 · 4 comments

Comments

@2MmYxoeg
Copy link

We are in the process of retargeting our application from .NET Framework 4.7.1 to .NET Core 2.1.

We now have the following warnings:

Warning NU1701 Package 'CacheManager.SystemRuntimeCaching 1.1.2' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.1'. This package may not be fully compatible with your project.

It doesn't appear that we are experiencing any compatibility issues. However I just wanted to ask if there are any plans to release a version of this package that targets .NET Core?

@MichaCo
Copy link
Owner

MichaCo commented Nov 26, 2018

see #221

Tbh, I don't really know why you get that warning. Might be because the current 1.1.2 version of cachemanager only targets netstandard1.2.
That should be compatible with whatever .NET Core 2.x though.

Maybe give the 2.0 beta package of CacheManager a go. Let me know how that works.

The beta 2.0 of CacheManager also uses the new StackExchange.Redis client btw..

@2MmYxoeg
Copy link
Author

Thanks - it seems that the beta package doesn't give the same warning. I'll look forward to the release of v2.0 then!

@MichaCo
Copy link
Owner

MichaCo commented Nov 26, 2018

just FYI, I'm currently testing the 2.0 beta bits in production without any issues so far

I still have to change a few things before releasing it, primarily internal changes, so, still a few weeks to go before that gets released

@jfritchman
Copy link

Any ideas when 2.0 will be released?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants