*.dannyg

http://msdn.microsoft.com/en-us/library/ms732012.aspx

There are some really nice modules to add on to IIS7.  One of the them URL Rewrite.  You can also set up a Reverse Proxying rule.  This basically allows you to re-route any traffic that might be specified in DNS to a different server.  In this particular scenario, the DNS rules couldn’t be changed because they weren’t owned.  However, because there is control over the destination server, I can re-route incoming traffic to a different server.

Double-click on URL Rewrite on the website that is accepting the incoming traffic.  Then “Add Rule”.  Select “Reverse Proxy” rule.

Now you can specify the new destination for all request.  You can be a little more specific about links with regular expressions if necessary.

Now you can test your theory by opening your web browser and pointing to the original domain name.  You can even rewrite links in the response.

After deciding that I wanted to query the much reveled OData services offered by Sharepoint 2010 I ran into multiple issues (now which I’ve resolved).

This is the service endpoint

http://<hostname>/_vti_bin/ListData.svc

1) OData services do not work over HTTPS.  I’m assuming this is related to configuration of WCF.  This is a key point to remember. 

2) Installing of the ADO.NET Data Services v1.5 CTP2 on the Sharepoint 2010 Server.  Do an IISRESET or reboot after this.

3) Ensure that there are no corrupt lists on a site.  If there are you’ll be able to hit a specific list but not hit the endpoint.  You’ll keep getting prompted with the NTLM/Keberos login from your web browser and never get logged in.  To remove a corrupted list (mine happened from upgrading from Sharepoint 2007 to Sharepoint 2010 without installing custom list types), run the following command from the Sharepoint Powershell Prompt (thanks to Harold van de Kamp’s blog entry on this one.)

stsadm.exe -o forcedeletelist -url <url>

http://blog.stevensanderson.com/2008/07/04/options-for-deploying-aspnet-mvc-to-iis-6/

This is pretty simple.

Create a batch file, call it app-pool-pid.bat for instance.

Edit it and add the following lines into the file:

@echo off

cscript.exe c:\windows\system32\iisapp.vbs

pause

Pretty tricky, the title says it all

cscript %systemdrive%\inetpub\adminiscripts\adsutil.vbs set w3svc/AspScriptErrorSentToBrowser true      (to allow error message send to client)

On a x64 OS (I run Windows 7 RC x64)

cscript C:\Windows\winsxs\amd64_microsoft-windows-iis-legacyscripts_31bf3856ad364e35_6.1.7100.0_none_4b5800ce84aa413c\adsutil.vbs set w3svc/AspScriptErrorSentToBrowser true

I’ve done this a million times, I just found it useful to publish it for easy reference

C:\Program Files\IIS Resources\SelfSSL>selfssl /T /N:CN=www.tempuri.org /K:1
024 /V:5000 /S:232294796 /P:443

/T: is to make it trusted

/N: is the common name

/K: is bit length

/V: is days of validity

/S: it the Site ID, you can get this from the log prepend (see below)

/P: is port

To get the site ID, open IIS, and check the log settings.