Security problem with dotnet framework 2.0

  • Thread starter Thread starter Tom Edelbrok
  • Start date Start date
T

Tom Edelbrok

Until recently I was running VB.NET under Visual Studio 2003 with .NET
Framework 1.1. I had to run mscorcfg to add my network share under machine,
code group, local intranet, etc to grant permission for the network share
'file:\\myserver\mysharename\*'. This has all worked great for the past 8
months.

However, I just installed Visual Studio 2005. For some reason I didn't get
the linke to mscorcfg in my CONTROL PANEL ~ ADMINISTRATIVE TOOLS so I
downloaded and installed the SDK for .NET Framework 2.0, and then the
mscorcfg utility showed up in Control Panel. I went into mscorcfg for
Framework 2.0 and added a new child under code group for machine (etc etc)
to permit my network file share for projects.

But in spite of all this, none of my VB.NET projects work properly any more.
Both VS2003 and VS2005 projects constantly complain that the 'location is
not trusted'.

My mscorcfg settings worked in the past - so what's stopping them from
working now?

Thanks in advance,

Tom
 
Figured it out. I had to remove my network share UNC from the trusted zone
of Internet Explorer Security, then re-add it.

Tom.
 
Back
Top