.Net Security Settings

Microsoft in their infinite wisdom decided not to add the configuration tools for the .NET framework with the .NET framework itself. This has resulted in some rumblings on the forums and some headaches for admins but they did add something to ease the burden.

The configuration tool is in the SDK for the .NET framework and with it is the ability to make the changes you require and then export the changes out as an MSI file for installation elsewhere in the enterprise.

Our problem was due to the increased security that .NET imposes by default, no working from network drives. Easily fixed with the .NET framework configuration tools via the MMC (mscorcfg.msc). Pull up the MMC with the .NET Framework Configuration snap-in.

1. Navigate My Computer - Runtime Security Policy - Machine - Code Groups - All_Code - LocalIntranet_Zone
2. Right-click and click 'New...'
3. Enter a name and description
4. For the file location in our case a mapped network drive G: we use file://G:\* The * indicates all subfolders
5. Next step select 'Full Trust' from the drop down list
6. Retstart your development application

Now to export it as an MSI:

1. Right-click on the 'Runtime Security Policy' subtree
2. Left-click 'Create Deployment Package'
3. Follow the wizard to create your MSI package

Thats it in a nutshell, it certainly saves installing a 350MB download on every PC that wants to run a development tool over the network.