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?
--
Lawrence E. Shafer