Timeline for ASP.NET application under SharePoint website
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 20, 2015 at 19:21 | comment | added | Web User | 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. | |
| Oct 20, 2015 at 9:24 | comment | added | Evariste | 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. | |
| Oct 20, 2015 at 8:35 | comment | added | Web User | 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? | |
| Oct 4, 2015 at 5:52 | vote | accept | Web User | ||
| Oct 4, 2015 at 5:45 | comment | added | Evariste | I'm afraid, yes, you'd need tp use the same app pool. | |
| Oct 4, 2015 at 1:54 | comment | added | Web User |
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?
|
|
| Oct 3, 2015 at 14:56 | history | answered | Evariste | CC BY-SA 3.0 |