We are using Adal as authentication library but we would like to use the policy functionality in Asp.Net Core security in our MVC5 application. The idea is to compile the Asp.Net Core library to .NET 4.6. This works! However, now I need to click the authentication things in my owin application.
Just adding the AuthorizeAttribute from the library doesn't work, it is not executed.
I have also read about the ported version from P. Schaeflein, but I would preffer to use the libraries provided by Microsoft.
Anyone an idea how to get this working?
Asp.net Core / .net core is a total rewrite of asp.net framework and the way it work is very different. For example Asp.net Core is most made around a Dependency Injection. So moving part of a framework that made for Asp.net Core to Asp.net MVC 4.6 made not work and would have to be rebuild to work with Asp.net MVC 4.6.
Related
I want to add .NET Core Web API project to an existing .NET core (3.1) Web Application project, with JWT Token Authentication with Identity Framework with routing and all..
Please Do we have any suggestion & is this possible & good idea to combine both the Projects?
Its not good idea to add .NET Core Web API to an existing .NET core (3.1) Web Application project.. first of all you have to set "Default Project" from your solution, and both project have entry point or start up class.
So if you want you can marge both project, you can move your controller and service from .NET Core Web API to .NET core (3.1) Web Application project, that may large work if your project size is big...
I originally have code using HttpContextBase from System.Web in my ASP.NET Web MVC project.
I would like to extend this functionality to a project that is using .NET Core by moving the code into a .NET Standard Library so both projects using ASP.NET Web MVC and ASP.NET Core respectively can use it.
Is there a replacement library or method I can use instead of HttpContextBase in my .NET Standard library to share code?
I'm porting a .net core 2.2 app to .net core 3.1 and have no idea of what's going on.
The generated swagger.json could also have other issues. We are using openapi-generator to generate the client files for our angular application and so far it isn't working.
I'm not finding any clear answer on this. On the Compatibility page, they say:
Everything in .NET 4.7 except WPF, WWF, and with limited WCF and
limited ASP.NET async stack
What about .NET Core 2.2? Is it possible to run it on MONO or not?
I'm glad .NET Core framework is becoming more mature; but unfortunately it doesn't support legacy WebForms, and MONO's support for Core is unclear, so they don't mix well.
Mono 5.4 implements netstandard 2.0. Since ASP.NET Core 2.x runs on netstandard 2.0, Mono 5.4 also does support ASP.NET Core 2.x.
Note that starting with ASP.NET Core 3.0, the framework will only run on .NET Core. That means that if you want to stick to Mono, you will have to stick with ASP.NET Core 2.x.
Since ASP.NET Core 2.2 is not a long time support (LTS) release, which means that it will run out of support not too long after 3.0 releases, I would recommend you to stay on ASP.NET Core 2.1 if you want to run it on Mono.
That being said, there isn’t really a reason for you to run on Mono there. You can just use .NET Core properly. If you need Mono around for other WebForms projects, then you can just do that for those projects. But for ASP.NET Core, you can just choose the .NET Core runtime. Because in the end, ASP.NET Core and WebForms will not mix, even if you run both on Mono.
how can i configure asp.net core signalr in ASP.NET Web Application (.NET framework 4.6.2 or higher) web project?
from this documentation this should be possible, but i cant find any way to implement it.
I think this is not supported.
The server type required for asp.net core signal r is asp.net core.
The normal "system.web" pipeline would not be compatible with the asp.net core SignalR.
In my opinion, you will be able to use CLIENT package - only if your application is client to asp.net core web api.