VB Project security violation on new Workstation

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

VB.net migrated a large, multi-moduled VB6 application to a networked drive.
Original workstation modified it and got it running under VB.Net. User was
migrated to a superior workstation with same credentials, id, etc. as before.
When VB.net project debugs, security exception in "unknown module"
immediately occurs.

Copy networked project to local drive, it loads and executes as it should.

Is this the expected behavior or am I missing something?
 
When executables are run from a network share they run under various
security restrictions. I am guess on startup it is trying to do that it
isn't allowed to.

When it's run from a local drive, it has as much rights as the user running
it, so it's fine.
 
Directions to add code group to .NET configuration

1. Open the .NET configuration utility. It resides in
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 and is called
mscorcfg.msc.
2. Expand Runtime Security Policy  Machine  Code Groups
3. Right click all code and select “Newâ€, enter the name and
description below.
4. Click next and select “URL†from the drop down list and enter
the string:
file://<PATH>/*
This will create a code group of any program that
resides in that directory.
5. Click next and select “Full Trust†from the drop down list.
6. Click next and finish. The code group has been created and programs
can be executed from that directory as if they were executed from the
local machine
 
Back
Top