Allow self-developed web applications to coexist with SharePoint

Web applications developed by ourselves under Moss Program It cannot run on the same site. How can we make the web application developed by ourselves coexist with wss3.0 or moss2007? We can modify the web of the application. config file to solve this problem (if not specifically stated below, the application is a self-developed web application), the principle is to use our own application web. config configuration overwrites the WSS-defined configuration at the top level without modifying the original WSS configuration file.

1. In the system. Web Section of the Application Web. config, clear the Asp.net handler, HTTP modules, and address forwarding definitions defined in the upper-level application. We need to re-specify to use Asp.net handler to process the ASPX page, Code As follows: < Httphandlers >
< Clear />
< Add Verb = "*" Path = "*. Aspx"  
Type = "System. Web. UI. pagehandlerfactory,
System. Web, version = 1.0.5000.0, culture = neutral,
Publickeytoken = b03f5f7f11d50a3a"   />
</ Httphandlers >
< Httpmodules >
< Clear />
</ Httpmodules >
< Pages >
< Tagmapping >
< Clear />
</ Tagmapping >
</ Pages >

2. Because wss3.0 or moss2007 sets the trust level, we need to modify the trust level in our applications, instead of using the definition in WSS. Add code:<TrustLevel= "Full"Originurl= "" />

 
3. Because the top-layer WSS web. config defines that the session module is disabled, that is, enablesessionstate is false. Therefore, we may need to enable the session and add the following code to the application configuration:<Httpmodules>
<AddName= "Session" 
Type= "System. Web. sessionstate. sessionstatemodule"/>
</Httpmodules>

If the system prompts that the session module in the application has been enabled and cannot be restarted, we only need to remove the httpmodules section.
Through the above settings, our application can have the same IIS Site with wss3 or moss2007.