"Ivan" <Ivan@discussions.microsoft.com> wrote in message
news:D91E77B8-2643-457A-A371-CE6D103459EE@microsoft.com...
> Thanks, I've solved my problem.

"Robert Bruckner [MSFT]" wrote:

> FYI: Visual Studio 2005 Beta 1 (download from
> http://lab.msdn.microsoft.com/vs2005/) contains a nice command line tool
> related to code access security: PermCalc. After installation it is located
> at \Program Files\Microsoft Visual Studio 8\Common7\IDE\Permcalc.exe
>
> PermCalc estimates all necessary security permissions that must be granted
> for every dll entrypoint in order to avoid security exceptions at runtime.
> This estimation is done by performing static IL analysis. Permcalc is also
> integrated into the VS Whidbey UI. In order to get the list of necessary
> permissions for all custom assembly entry points, you would just run e.g.
> permcalc -progress -library CustomAssembly.dll
>
> Therefore you can more easily identify which missing security permission
> asserts and grants cause the execution of custom assemblies to fail. Note:
> PermCalc can even analyze dlls compiled with older versions of the .NET
> Framework (e.g. VS 2003).
>
> --
> Robert M. Bruckner
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Ivan" <Ivan@discussions.microsoft.com> wrote in message
> news:D91E77B8-2643-457A-A371-CE6D103459EE@microsoft.com...
> > Thanks, I've solved my problem.
>
>