I have an old web forms application that uses membership provider. I want to use an existing .net core identity project instead of membership provider. Where and how can I configure it in my old web forms project? Does anyone know how to implement that in my old project?
Related
At work, we have an Old application developed with the following technologies:
Visual Studio 2010 Ultimate
.NET Framework 4
C# 4.0
ASP.NET WebForms
With our application we are Highly concerned with issues like:
-security,
-links,
-and users sessions.
We have some new software requirements features which in turn means that we have to add to the existing application.
We would like to use newer Microsoft .NET technologies for the new features.
However, we are concerned about compatibility problems. We have Visual Studio 2019, and we would like to develop the new features using Visual Studio 2019.
But, how far can we go before we have compatibility problems, and face other kinds of limitations?
Is it possible to successfully bridge the Old application with newer technologies like:
-.NET Core Web API
-.NET Core MVC
-.NET Core Razor Pages?
Again, we can Not compromise on the following:
-security
-links
-and users sessions
Yes, you can use both .net framework application and .net core application inside single hosted application. Same thing i have done in one of my project. old project was in .net framework 4.5 and we wanted to build new features in .net core with web api.
We did and integrate both application inside a single application which is hosted on IIS server.
In term of security and sessions , .net core provide more control over these things.
Let me know if you need more help of info.
I am doing this project in mvc6 using asp.net framework 6.how I can add this reference in my project please help me.
You have to talk to BingAds and ask them for a compatible version. This is the same with every library provider, they all must support the new platform. You cannot add a library which targets .NET 4.x, they must rewrite and publish a new version/
We are maintaining an internal organizational administration system written (sadly) in ASP.NET 3.5. We have recently been asked to add password management capabilities to the system, which seemed like a perfect fit for the password management features of ASP.NET Identity.
My question is, can we use ASP.NET Identity in our system, having it being written in ASP.NET 3.5?
If so, what is required to do it?
If not, are there any alternatives? We only need the password-related stuff, like length, special characters, prevent reuse of previous, say, 3 password etc.
Cheers,
ashilon
ASP.NET Identity framework is collection of nuget packages (DLL's) and the Runtime Version (minimum supporting .NET Framework) is v4.0.30319.
So that you could not be able to use ASP.NET identity framework on ASP.NET 3.5 which is .NET Framework 3.5.
Following packages using Runtime Version v4.0.30319
Microsoft.AspNet.Identity.Core
Microsoft.AspNet.Identity.EntityFramework
Microsoft.AspNet.Identity.Owin
You could upgrade your project to support .NET Framework 4.0 or above and then you could be able to use asp.net identity framework.
I am going to be developing a new web app using MVC 4. It will be hosted on a shared server (one of those $5/month sites: sqlservermart.com)
It has been a few years, and it looks like there is a new "Universal Membership Provider" instead of the old membership provider. My question is can I assume that the universal membership providers will be available if .NET 4.0 is on the remote server? If not, what are the providers installed as part of?
Thanks!
universal providers are not installed with .NET Fx. Its a nuget package which you will have to install in your project. when you publish your project to the remote server you will have to publish the universal provider dll which would be in the bin of your application
http://nuget.org/packages/Microsoft.AspNet.Providers.Core
I am working on a project with Vs2010 and MVC4. (mainly Apicontrollers). Now the project is ready to deploy into production. The problem is that the client don't want to go with MVC4 even though there is a go-live license from Microsoft. The only new feature I used in this project from MVC4 is webAPI.
Can I use APIcontrollers in MVC3?
If yes How can I implement API controllers in MVC3 project?
What troubles will I face if I downgrade to MVC3 from webAPI standpoint (like :routing,hhtpconfiguration)
Yes
You can get web API with Nuget to you MVC3 project
Don't think you'll have any troubles, web API comes in separate dll that is independent of MVC dlls