Make VMWare Share Part of the Local Intranet

This is one I’ve found to get stuff to build that I didn’t find anywhere else. Even after running caspol I still couldn’t run executables on the share. That is, until I made the share part of the Local Intranet.

Open Internet Explorer, then open Internet Options.

Find the Security Tab

Open Local Intranet by selecting Local Intranet and pushing the Sites button

This will allow for executables to start working. All but the ones built and run from Visual Studio.

.NET Built Executables/Services No Longer Work

It may be awhile before you run into this one. You may have a console application you are building. You will notice once you move over to the share, you start getting errors related to that. What you need to do is add a small configuration value to the the config files.

Add the following to your config files:

<runtime>
<loadFromRemoteSources enabled="true" />
</runtime>

This will allow it to be loaded into memory, otherwise it will not run from a network share.

Caveats to Network Share

Caveats to think about when developing against a share:

Visual Studio has trouble noticing updates to files if you update them outside of Visual Studio.

If you run the local built in web server for web development, don’t expect it to catch the files updating automatically.

If you do any kind of restoring a database from a backup, you may want to consider copying that database to a local drive first.