For some web-projects I needed a public available space on the internet that supported ASP.NET 2.0. The domain tisgoud.nl was running under ASP.NET 1.1 but my webhosting provider Vevida supports ASP.NET 1.1 and 2.0.
Then there is my (das)blog, initially built for ASP.NET 1.1 and according to the documentation compatible with 2.0. I only had to make some adjustments to the web.config and al should be fine.
What they failed to mention is that if your provider has set the trust level to “High” and the “allowOverride” to false you are screwed. Running dasBlog results in the following ”Security Exception“.
Then what?
After some failed attempts of recompiling the sourcecode in VS2005 – food for another blog post – I decided I had to get a workaround.
As an intermediate solution I just had set up my pc at home to run my blog.
What do you need for that?
- Machine with IIS 6 and at least ASP.NET 1.1,
well it turned out to be a Windows 2003 R2 server with ASP.NET 2.0. And the server has it’s trust level set to “Full”.
- A static internet address,
my broadband provider is one of these big cable-companies and as most of them do they use dynamic ip- addresses. To get a semi-static address to reach the pc at home DynDNS comes to the rescue. Only the basic funtionailty is needed so the free Dynamic DNS service is fine.
- Redirect for the application directory blog to the machine at home,
my hosting provider recently installed ISAPI_Rewrite. One of the features is the “Regular expressions-based URL rewriting engine”. A simple rewrite rule in a http.ini file is all it takes to redirect requests to the blog directory. A much cleaner solution than a rewrite in a .aspx file.
- Local router configuration,
the incoming requests on port 80 have to be redirected to the machine running the local dasBlog site.
It’s up and running now, the workaround is in place and now I can continue with my attempts of setting up dasBlog in VS2005.
Ah, I see. I’ll look into this. It’s tricky though. You can see from the screen shot that your ISP isn’t allowing DasBlog to even read it’s config file. Did you try turning Impersonation on?
Turning impersonation didn’t help:
Security Exception
Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application’s trust level in the configuration file.
Exception Details: System.Security.SecurityException: Request failed.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[SecurityException: Request failed.]
newtelligence.DasBlog.Web.SiteConfig.GetSiteConfig(String configPath) in SiteConfig.cs:143
newtelligence.DasBlog.Web.SiteConfig.GetSiteConfig() in SiteConfig.cs:126
newtelligence.DasBlog.Web.Core.TitleMapperModule.Init(HttpApplication context) in TitleMapperModule.cs:24
System.Web.HttpApplication.InitModules() +267
System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers) +1251
System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +243
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +106
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +214
Pretty cool site you’ve got here. Thanx for it. I like such themes and anything that is connected to them. I would like to read more soon.
Anete Swenson