wordyone

I have just installed the .Net Framework security update and started getting the following error when testing on my development PC:

Request for the permission of type 'System.Data.OleDb.OleDbPermission, System.Data, Version=2.0.0.0, Cluture= neutral, PublicKeyToken=... ' failed.

I am receiving the error in a VSTO Add-in for Word 2007 - this add-in accesses another VB.net assembly that uses oledb to lookup information in an Access db.

Why would this suddenly appear following the yesterday's security update

I am thinking I must need to set some OleDB permission parameters or machine-level security policy in Caspol.exe (or both). Could someone point me in the right direction

Thanks.



Re: Visual Studio Tools for Office OleDbPermission error accessing assembly

Dennis Wallentin

Hi,

Looks like MSFT is shaping up the security which is in the long run good for us all. Anyway, what permissions have You set in the other assembly that access the MDB






Re: Visual Studio Tools for Office OleDbPermission error accessing assembly

kewpcg

I have re-run the Caspol command to apply the full trust to that folder and that seemed to have fixed it. So something in the .Net Framework 2.0 security update made it not recongize full trust had already been applied (I'm guessing).

Note: Tuesday's security update also had the side-effect of making my VSTO add-ins no longer load in Word 2007. In addition to having to reapply full trust, I also had to rebuild all my add-ins to get them to work again.





Re: Visual Studio Tools for Office OleDbPermission error accessing assembly

Dennis Wallentin

Hi,

Thanks for coming back and that You confirm what the source of error is. For the last days I've seen several posts on different forums / maillist that the security update has a negative impact of the settings. From my point of view we should consider it as a bug.