You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're going to look at .Net Core 3 when a general release is made, we're still on Preview 5 (unless I missed something). However it shouldn't be tricky to use Lynicon with .Net Core 3 as it is just a .Net Standard 2.0 library which should be fully compatible. I do know that ASP.Net Core 2.2 introduces a new routing system which is not compatible with the essential custom routing extensions in Lynicon. However you can configure this to revert to the current routing system. The changes increase efficiency in the routing system, and are transparent to everything but advanced customisation of the routing system. So if you simply use the .Net Core 2.1 instructions here: https://lynicon.atlassian.net/wiki/spaces/LAC/pages/363495425/Installing+to+a+New+Project+-+VS2017+.Net+4.6.1+.Net+Standard+2.0+Core+2.1 and adapt as you go it should be fine.
We'd greatly appreciate the contribution if you did this and let us know any issues you resolve or you need help with on this thread. As I said, it should be pretty straightforward, it was only a few hours work for us to move from .Net Core 2.0 to 2.1.
Activity
jamesej commentedon Jun 8, 2019
We're going to look at .Net Core 3 when a general release is made, we're still on Preview 5 (unless I missed something). However it shouldn't be tricky to use Lynicon with .Net Core 3 as it is just a .Net Standard 2.0 library which should be fully compatible. I do know that ASP.Net Core 2.2 introduces a new routing system which is not compatible with the essential custom routing extensions in Lynicon. However you can configure this to revert to the current routing system. The changes increase efficiency in the routing system, and are transparent to everything but advanced customisation of the routing system. So if you simply use the .Net Core 2.1 instructions here: https://lynicon.atlassian.net/wiki/spaces/LAC/pages/363495425/Installing+to+a+New+Project+-+VS2017+.Net+4.6.1+.Net+Standard+2.0+Core+2.1 and adapt as you go it should be fine.
We'd greatly appreciate the contribution if you did this and let us know any issues you resolve or you need help with on this thread. As I said, it should be pretty straightforward, it was only a few hours work for us to move from .Net Core 2.0 to 2.1.
sergpy commentedon Oct 15, 2019
The problem still remains :(
Any plans to support AspNet.Core 22 ?
jamesej commentedon Oct 15, 2019
Sorry although at some point we aim to upgrade to .Net Core 3, there's no timeline as yet.