Re: Minimum permissions for Microsoft Exception Application Block

From: Ivan Medvedev [MS] (ivanmed_at_online.microsoft.com)
Date: 01/20/04


Date: Tue, 20 Jan 2004 08:59:30 -0800

There is a tool called PermCalc that we are going to ship in the Whidbey
release that does just that. Speaking of FxCop, it is very possible to write
FxCop plug-ins (or "rules") that utilize its call graph and other analysis
capabilities. See FxCop team blog which points to the necessary
information - http://blogs.msdn.com/fxcop
--Ivan
http://blogs.dotnetthis.com/ivan
http://www.dotnetthis.com
This posting is provided "AS IS" with no warranties, and confers no rights.

"Keith Patrick" <richard_keith_patrick@hotmail.com> wrote in message
news:%23$WpqVH3DHA.1752@tk2msftngp13.phx.gbl...
> Well, I *was* working on a tool that does just that, in addition to
> examining .xml documentation files to alert users to undocumented and
> unhandled exceptions, but I'm hung up trying to decompile code into
symbolic
> types. Maybe if there is a way to hook into FxCop's call graph, it would
go
> pretty quickly...
>
> "Azad" <anonymous@discussions.microsoft.com> wrote in message
> news:853B9260-2CCE-4EB3-A7FB-224DC6404016@microsoft.com...
> > Hi,
> >
> > I was wondering why the Microsoft team hasn't specified the minimum
> permissions required for the assemblies that are shipped with the
exception
> application block, although the required references (system.security,
> system.security.permissions) have been included in the AssemblyInfo file.
> The minimum permissions have been identified for other application blocks
> such as the configuration management or the data application block. Now I
> have to figure it out by myself. Does anyone know what the minimum
> permissions should be for the exception block?
> > Another question that I have, and this might be just wishful thinking:
> > Is there a tool that would examine my assemblies in a Visual Studio
> solution and then tells me what the minimum permissions should be? That
> might be a cool feature for the next release of Visual Studio!
> >
> > Thank you for your response,
> > Azad
>
>



Relevant Pages

  • Re: Minimum permissions for Microsoft Exception Application Block
    ... permissions required for the assemblies that are shipped with the exception ... The minimum permissions have been identified for other application blocks ... > Is there a tool that would examine my assemblies in a Visual Studio ...
    (microsoft.public.dotnet.security)
  • Re: FxCop does anyone use it ?
    ... For instance it founds out if you catch Exception if you could have ... >the same time we developed our framework, so we find "new" warnings on old ... Internal MS code breaks many guidelines. ... We could never have complied to so many guidelines without FxCop. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Catching generic exceptions
    ... Thanks for the input it is interesting to hear of other peoples experience with FxCop. ... >have to display the exception in a user friendly way. ... >exceptions in a other pieces of code that are non-GUI applications or do not ... This allows you to ignore the specific warnings only in the ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: FxCop being a bit OTT?
    ... Dave wrote: ... I'm using FxCop to go through my code and it's showing bad things in my code. ... It is saying that you should never ever catch a general exception, and since in my foolishness I'm catching all errors in my user interface I've got a fair few of these in my code. ... I'm doing this so that if a user presses a button if for some reason my code fails the worst case scenario for the user is either a usefull error message of a generic one asking them to send in an error log file rather than having the whole application fall over because I missed a pottential exception. ...
    (microsoft.public.dotnet.languages.csharp)
  • Localizing text in an exception.
    ... I am running the code for a code assembly through FXCop here and it seems to ... FXCop says that I should be grabbing the text from a string resource so that ... exception text most likely to only be seen by a developer. ... and take the time localize my exception strings into other languages? ...
    (microsoft.public.dotnet.general)