My VB.NET application uses an access-style .mdb database. If I launch the app (and db) from a network share, when the app attempts an OLEDB connection to the DB, I get
"The application attempted to perform an operation not allowed by the security policy. The operation required the SecurityException ..."
And
"System.Security.SecurityException: Request for the permission of type System.Security.Permissions.SecurityPermission, mscorlib, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 failed."
I previously was given a solution on this forum that uses mscorcfg.msc to create a Trusted Assembly which is the networked executable. Once the local PC trusts the app, everything is fine. Bummer is that when I create a NEW build of the application (which is all the time), that Trust is broken and has to be done over again by hand on every workstation - a big pain.
Does anyone know of an automated way to deploy that Trust Assembly? Maybe with an installer, maybe by the application itself? Maybe via Active Directory Group Policy? And make it stick through new builds? Or maybe the access .mdb needs the trust?
Thanks in advance!
-frank
"The application attempted to perform an operation not allowed by the security policy. The operation required the SecurityException ..."
And
"System.Security.SecurityException: Request for the permission of type System.Security.Permissions.SecurityPermission, mscorlib, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 failed."
I previously was given a solution on this forum that uses mscorcfg.msc to create a Trusted Assembly which is the networked executable. Once the local PC trusts the app, everything is fine. Bummer is that when I create a NEW build of the application (which is all the time), that Trust is broken and has to be done over again by hand on every workstation - a big pain.
Does anyone know of an automated way to deploy that Trust Assembly? Maybe with an installer, maybe by the application itself? Maybe via Active Directory Group Policy? And make it stick through new builds? Or maybe the access .mdb needs the trust?
Thanks in advance!
-frank
