VB 2005 w/ 2.0 framework

[Darin]

I have upgraded our application from .NET 1.1 to .NET 2.0, all works
fine from my local machine.

But, when I put the program on the server and try to run it from the
server (via a mapped drive), I receive:

Menu.exe has encountered a problem and neds to close. We are sorry for
the inconvenience.

When I click on what data does the error report contain, I get the error
signature that has:

P9: system.invalidoperationexception

I have added my \\server\share into the IE7 local intranet sites, and it
still fails. I know when we were using the 1.1 framework we had to
adjust the zone security settings so local intranet was full trust, but
I can't find that option anywhere for the 2.0 framework.

I have set the menu.exe program to enable clickonce settings, and it is
a full trust application. On the signing I created a pfx file that is
setup - and these changes have made no difference.

I am doing some more debugging, but I just want to know if anyone else
has experienced this and what the resolution was?

TIA
Darin

*** Sent via Developersdex http://www.developersdex.com ***

[Paul Clement]

On Wed, 28 Feb 2007 10:40:04 -0800, Darin <darin_nospam@nospameverwrote:

¤ I have upgraded our application from .NET 1.1 to .NET 2.0, all works
¤ fine from my local machine.
¤
¤ But, when I put the program on the server and try to run it from the
¤ server (via a mapped drive), I receive:
¤
¤ Menu.exe has encountered a problem and neds to close. We are sorry for
¤ the inconvenience.
¤
¤ When I click on what data does the error report contain, I get the error
¤ signature that has:
¤
¤ P9: system.invalidoperationexception
¤
¤ I have added my \\server\share into the IE7 local intranet sites, and it
¤ still fails. I know when we were using the 1.1 framework we had to
¤ adjust the zone security settings so local intranet was full trust, but
¤ I can't find that option anywhere for the 2.0 framework.
¤
¤ I have set the menu.exe program to enable clickonce settings, and it is
¤ a full trust application. On the signing I created a pfx file that is
¤ setup - and these changes have made no difference.
¤
¤ I am doing some more debugging, but I just want to know if anyone else
¤ has experienced this and what the resolution was?

There is an MS KB article that documents how to handle this:

http://support.microsoft.com/kb/832742

The 2.0 Framework does not have a wizard but if you launch the .NET Framework 2.0 Configuration
applet you can click on the Runtime Security Policy node, then the Increase Assembly Trust task to
display the Trust an Assembly dialog box. From there you should be able to follow the instructions
in the KB article.
Paul
~~~~
Microsoft MVP (Visual Basic)