Archive for the ‘IIS’ Category

ASP.NET Best Practice Analyzer

Thursday, July 13th, 2006

Microsoft have released an alpha version of a best practice analyser for ASP.NET. Without using the tool yet, it looks like the tool scans your config files, and not your code or your aspx pages. You can download the tool here.

Found via : Joe Morel’s Blog - Best Practice Analyzer for ASP.Net Alpha Released!

We are experiencing a few minor technical difficulties please stand by

Saturday, March 25th, 2006

Update: Ken Schaefer has posted about Using commas in IIS Redirects, which will solve the problem that I was having. I personally decided to change the permalinks from dasBlog’s default use GUID’s in permalinks standard, to the much more human friendly .aspx format.

Now I just need to work out why Ken’s comments disappeared ….

Original post: (Tuesday, 21 March 2006)

Well I have finally migrated my blog from flat html to dasblog. This change means that the locations and extensions of all my files has changed, requiring a number of server redirections.

Interestingly it was at this point that I noticed that IIS can’t support commas in redirection URL’s and, suprise, suprise, dasblog uses commas in it’s permalinks…

So the rub is that there are currently a few broken links around the place (like where I have manually relinked to a post), but I will be working to fix them as soon as possible.

I will definatley be changing the current permalinks, so please don’t link to anything just yet.

Deploying an ASP.NET application side by side with virtual hosts

Friday, January 14th, 2005

Origional post (Mon, 6 Sep 2004)
To fully utilise the power of side by side deployment of ASP.NET sites running on IIS, through pain and experience we that the best way to do this is to set up a virtual root for each daily build and then simply point the master site to the virtual root of the “live” build.

There is a significant lack of flexibility available when you are doing this. We have found out the hard way that you need to add an additional host header with a unique port number to deploy to a virtual root, then call the msiexec command line and specify the TARGETPORT of the website.

e.g: www.example.com:8888 <- website host header

msiexec.exe /i c:\WebSetup.msi TARGETPORT=8888

This will install a virtual site under the website that uses port 8888, you can then remove the host header and you are done.

Update (Fri, 7 Jan 2005)

David Every has written a detailed step-by-step article (www.15seconds.com/issue/041223.htm) on how to get IIS side-by-side up and running.