Last post Apr 12, 2013 04:41 PM by dsouzajohnson23
Apr 11, 2013 09:50 PM|shamcs_ini|LINK
hye there...just a simple question..
i want to develope 2 different web application with one single membership database. What is the better approach, is it combine 2 web application into one project and deploy it as one application. or create 2 different project and deploy it as separate application..?
The question come because, i just think, if application one have high request/access rather than application two.. is it will effect performance of application two also..?
If i seperate the project and deploy it as different application in one domain such as :
Performance of application two will effect if application one have high request or not..?
Thanks in advance.=)
Apr 12, 2013 06:29 AM|binson143|LINK
If both applications are diffrent you may go to use diffrenst solutions, if both this applications are sharing code base you can use one application in single solutions.
Use a common DB fro asp.net membership
Apr 12, 2013 06:46 AM|smirnov|LINK
Keep applications in different projects but include them in one solution in VS.NET. This will simplify development and maintenance of the code. Use separate application pools on IIS if each application needs different access to system resources.
Apr 12, 2013 09:56 AM|shamcs_ini|LINK
both application share one dll and also share single membership database... for my situation...application one is more often access by user and not application two... if at peak time....application one have more request than application two... is it necessary
seperate the application(in deployment) and implement single sign on...?
Apr 12, 2013 10:18 AM|smirnov|LINK
1) both application share one dll and also share single membership database...
You can share as many dlls/databases as you need.
2) if at peak time....application one have more request than application two...
3) is it necessary seperate the application(in deployment) and implement single sign on...?
It's up to you.
Splitting or merging applications in projects is a pure organizational question of development. Even if you defined 2 projects, you could deploy both projects as one application on IIS with the same pool. So, I would recommend to make 2 projects which give
you more flexibility.
Apr 12, 2013 04:41 PM|dsouzajohnson23|LINK
As I can understand, you have two applications sharing a single database and a dll but still maintaining its own unique stature…I term them as AppA and AppB….both are web applications having the same infrastructure….only difference that I see is AppA has
more user base than AppB….am I correct so far? ...Is there any other differences and expectations from these two apps?