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.