Friday 19 December 2008

Loading this assembly would produce a different grant set from other instances

If you get this exception message when trying to browse an ASP.NET site you are developing, first stop the site in IIS, then clear out the ASP.NET Temporary Files folder that relate to your site (default location is under C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files). Then start IIS and try browsing the site.

Localhost on IIS7

By default, browsing to localhost on IIS7 brings up a welcome screen. To associate localhost with a particular web site, right-click the web site in IIS7 and select "Edit Bindings" (or just "Bindings", depending on which pane you were in when you right-clicked; IIS is still as inconsistent as ever!). In the "Add Site Binding" dialogue box, add localhost as a host name. Apply the changes. You will now be able to browse to localhost.

Thursday 18 December 2008

Visual Studio External Tools Menu

Further to my post about setting up Windows Explorer as an external tool within Visual Studio (http://www.neilpullinger.co.uk/2008/03/open-visual-studio-project-folder-in.html), I have set up a number of other tools set up in the same way. Here's my list now:







TitleCommandArgumentsNotes
Run test(full path to nunit.exe)$(ItemPath)
Reflector(full path to reflector.exe)$(ItemPath)
FxCop(full path to fxcop.exe)$(TargetPath)
Explorer(full path to explorer.exe)/e, /select, $(ItemPath)
Open in Notepad(full path to notepad.exe)$(ItemPath)
Open(full path to a batch file containing just "%1")$(ItemPath)
Error Lookup(errlook.exe, in VS\Common\Tools folder)(none)Not sure where this one came from; installed by default?
Spy++(spyxx.exe, in VS\Common\Tools folder)(none)Installed by default

I've excluded a couple of the others that are there by default (eg. Create Guid and Dotfuscator).

(Edited 19/12/2008)