I am is there any way of using standard asp.net alongside umbraco, I have a site that runs umbraco, but i also wish to use the same hosting for some standard asp.net pages (upload area etc) that i dont want to / know how to do in umbraco.
My experience is that I also have to add a ton of umbraco related dlls to the subfolder/bin folder as well. (umbraco.*.dll, UrlRewrite, businesslogic, etc). Am I doing something wrong? I added my folder (/projects/) to the reservedurls and reservedPaths keys.
Jay, is that subfolder configured as an application in iis? If so, yes, some dll's will have to be repeated. Otherwise, I don't see why you should add the /bin folder and dll's from the root /bin folder (Or I might be missing the point)
I think the answer lies in weather you wish the pages to run under the umbraco installation or as a virtual site. If, as Dirk says, you are just adding asp.Net pages to the umbraco site, you just need to place them in a new folder (for convenience) and add the folder in the reserved URLs.
If going down the virtual directory option, the root web.config will have entries such as:
Any virtual site below this will use this configuration (it cascades). You can copy the DLL to the bin directory in the virtual site or preferably (IMO) you can remove the call in the virtual sites web.config:
Then you can stop the cascading. You can work out by trial and error which bits of the Umbraco 6 web.config need it - system.web and system.webserver did the job for me. Then you have a clean application to start with.
Standard asp.net outside of Umbraco
Hi
I am is there any way of using standard asp.net alongside umbraco, I have a site that runs umbraco, but i also wish to use the same hosting for some standard asp.net pages (upload area etc) that i dont want to / know how to do in umbraco.
Is there any way to run the 2 side by side?
Cheers
Hywel
You can add your app into folder and then set umbraco to ignore this folder by adding it into umbracoReservedPaths key in web.config.
Petr
Yes, indeed. Peter is right. Here's the way to do it:
<add key="umbracoReservedUrls" value="/config/splashes/booting.aspx,/install/default.aspx,/config/splashes/noNodes.aspx,/MyNewPage.aspx,/MyNewDir/MyNewPage.aspx" />
Just remember to seperate with a comma, then everything should be fine...
Ahhh sorry, Petr, not Peter. My bad. :)
Nice one thanks guys.
My experience is that I also have to add a ton of umbraco related dlls to the subfolder/bin folder as well. (umbraco.*.dll, UrlRewrite, businesslogic, etc). Am I doing something wrong? I added my folder (/projects/) to the reservedurls and reservedPaths keys.
Jay, is that subfolder configured as an application in iis? If so, yes, some dll's will have to be repeated. Otherwise, I don't see why you should add the /bin folder and dll's from the root /bin folder (Or I might be missing the point)
Cheers,
/Dirk
I think the answer lies in weather you wish the pages to run under the umbraco installation or as a virtual site. If, as Dirk says, you are just adding asp.Net pages to the umbraco site, you just need to place them in a new folder (for convenience) and add the folder in the reserved URLs.
If going down the virtual directory option, the root web.config will have entries such as:
Any virtual site below this will use this configuration (it cascades). You can copy the DLL to the bin directory in the virtual site or preferably (IMO) you can remove the call in the virtual sites web.config:
You will also need to remove unnecessary Handlers
and remove/comment out any sections that are in the root web.config that is used in the virtual site and probably should remove the role manager.
Well, that's how I did it anyway!
urgh, I can't believe I spelt whether as weather (well I can believe it but am a little embarrassed . . .)
With the latest version of asp.net if you wrap sections of your web.config with
Then you can stop the cascading. You can work out by trial and error which bits of the Umbraco 6 web.config need it - system.web and system.webserver did the job for me. Then you have a clean application to start with.
is working on a reply...