1

We are developing an application and want to separate it into two projects. The first project for end users will be on asp.net mvc, and the second for administration will be on asp.net webforms because simple crud operations perform easier on webforms and there are many out of the box controls. Problems:

  1. share same authentication system
  2. access to backend via site.com/backend
David Hall
  • 32,624
  • 10
  • 90
  • 127
Eldar
  • 862
  • 9
  • 22

3 Answers3

3

Piece of cake.

  1. The backbone of Authentication is part of Asp.net's core. MVC and WebForms share things like the FormsAuthentication cookies and Membership Providers

  2. WebForms and MVC get along just fine. All you really need to do is set routes.RouteExistingFiles = true; in global.asax for your /backend/ subdirectory and MVC won't try and route your WebFormPages.aspx to Controllers.

John Farrell
  • 24,673
  • 10
  • 77
  • 110
  • I meant in question two separate projects. In one mvc project mixing with webforms as you said is indeed piece of cake – Eldar Nov 27 '10 at 20:14
0

cause simple crud operations performs easer on webforms

I don't agree with this at all. You have the same problems with either or unless you're going to use SQLdatasource which I don't recommend. nHibernate and EntityFramework provide a nice data access solution for both webforms and mvc

Here is a link to how I achieved Single Sign On, two asp.net projects pointing to the same membership schema.

Community
  • 1
  • 1
jim
  • 26,598
  • 13
  • 51
  • 66
0

Why are crud operations easier on webforms? MVC in my opinion is better for crud operations out of the box. Also try jquery controls, as they are better than the built in ASP.NET controls.

Stephen Curial
  • 27
  • 1