0

The Default Web Site on my Windows Server 2008 with IIS 7 is running MOSS 2007 (SharePoint). Since I want users to feel like they are still on the portal, I created a similarly branded ASP.NET web application and set it up as a virtual directory based application under the same site. Both the Default Web Site and this ASP.NET application are using the same application pool.

  • Is this safe/good practice?
  • If I enable and use session in the ASP.NET application, will that in any way jeopardize the integrity/performance of SharePoint managed session, or affect SharePoint in any other way?
Improve this question

1 Answer 1

Reset to default
1

If you want to go on with this approach, at least make sure you:

  1. Created a dedicated application pool for the ASP.NET app, possibly with a dedicated identity account.
  2. Set the virtual folder as an application in IIS.
  3. Use the dedicated app pool for this app.

If you follow these steps, you have something "safe" considering the constrain "everything runs on the same machine".
Using a dedicated app pool is the best approach you can have here:

  • It prevents a crash from pool A to affect pool B.
  • It ensures sessions are not mixed-up (actually, it's thanks to the Web app created in IIS for the ASP.NET app folder).
  • A hacker gaining access to pool B would not have access to your SP DB (since the identity is totally different and has probably no access to the SQL server).

Note: In SP2003 you had to create an explicit exclusion for the app folder in the Central Admin (managed paths); this is not required/possible anymore since 2007.

Improve this answer
5
  • thanks for the clarification. If I needed access to the SPContext object in the ASP.NET application, then would I need to use the same application pool like I do now?
    – Web User
    Commented Oct 4, 2015 at 1:54
  • 1
    I'm afraid, yes, you'd need tp use the same app pool.
    – Evariste
    Commented Oct 4, 2015 at 5:45
  • I need to override some specific parts of the configuration inherited from SharePoint's (root website) web.config. How do I achieve this without touching SharePoint's web.config?
    – Web User
    Commented Oct 20, 2015 at 8:35
  • Create a new web.config at the virtual folder (your app) level. Its values will override values from default/root web. It may contain only values you want to override from default/root web.config.
    – Evariste
    Commented Oct 20, 2015 at 9:24
  • when I created a new application under that virtual directory, VS automatically created a web.config. But the application is inheriting SharePoint's web configuration and I encounter errors that confirm the conflict. When I run the application in VS Debug mode, there are no such conflicts.
    – Web User
    Commented Oct 20, 2015 at 19:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.