I have a ASP.NET application running on the server using ASP.NET membership provider. I would like to use the same database for my ASP.NET MVC3 application.
Do I only need to change the connection string in the Web.Config file? I tried that but no luck.
This depends on how is implemented your membership provider.
You might have to create your own implementation of memmbership provider for the both applications to share the same data tables.
check this guide how to do this:
http://www.danharman.net/2011/06/23/asp-net-mvc-3-custom-membership-provider-with-repository-injection/
Related
I have an Angular 5 application which uses a REST API for its back-end process. And other is pure ASP.NET Core MVC application.
Both have their own AccountController. I have to make an integration in a way that the Angular application has to call the ASP.NET MVC application. When it calls the ASP.NET MVC application, it has to login to that application and returns the Razor page. From this point, user will access the ASP.NET MVC application.
Both the applications have their own databases. But the user details will be stored in both applications.
My question is, how to achieve this?
If any article or documentation is available, it would be helpful if you share it.
I have a solution which has 2 projects: WebUI and WebAPI.
WebUI: There is only FroneEnd part with Angular2. It doesn't know about database.
WebAPI: This is RESTful API's which has database connection string and services.
Question: Can anybody describe how I can make requests from WebUI to WebAPI in a CORRECT way. Set default ports, links, use configuration or else.
Thanks =)
Project structure
In upgrading an old project that was built using WCF Web API to now use ASP.NET Web API, I have run into a few classes that implement HttpOperationHandler<HttpRequestMessage, T>. I'm unable to find an equivalent class in the new assemblies. Does something similar exist or will I need a different approach?
The concept of Operation handlers has been replaced with Filters and model binders.
Here are some links that you might find useful:
How to Migrate from WCF Web API to ASP.NET Web API
Mike's blog on How WebAPI does Parameter Binding
Getting started tutorials on ASP.NET WebAPI page.
Hope this helps.
I have a working ServiceStack application which started off part of my MVC application which contains my Jquery Mobile web site.
The services are growing and I am thinking about moving the ServiceStack code to separate app but not sure whether I should host service stack in an Asp.net web application or in a MVC application.
Are there any benefits down the road if I go one way or the other? In the future I need to introduce authentication for the services, would that be a factor in deciding?
I would host it on an vanilla ASP.NET host, since it's a more barebones web host than MVC which adds additional (and un-necessary) HTTP Modules and overhead.
I want to use WCF RIA Services as the middle tier for multiple clients including Silverlight and ASP.NET MVC.
I created a solution with Domain classes in a separate assembly using WCF RIA Services 4.2 CTP and Database First, which I want to share between the Silverlight and MVC clients. The solution looks like this:
Solution Foo
Foo.RIAServices.Server.Entities
Foo.RIAServices.Server.Entities
Foo.RIAServices.Server.Entities.Web
Foo.RIAServices.Client
Foo.RIAServices.Client.Web
FooMvcApplication
FooMvcApplication.Tests
FooResources
What if anything is wrong with my architecture and approach? Is there a better approach to using the Microsoft Entity Framework to create a common service for multiple clients?
Can I create a common custom Authentication service for both? Will the [EnableClientAccess()] and [RequiresAuthorization] decorations be respected for all clients?