More weekend hacking
Actually most of my weekend hacking wasn't GUI related at all. Most of it has gone into refactoring the existing source code to reduce duplication (as they all evolved from the same code base, the new permview.exe tool) and to move the different tools into plugins.
Plugins are often overrated, and overused, but in this case I know some of them requires quite a lot of memory (e.g. finding all public callers) and many planned (i.e. in a dark corner of my mind) plugins will too have high memory requirements. How much ? well probably more than I have right now, so there's no point having all plugins around at the same time unless necessary (or for a limited number of assemblies).
To make this easier the tool operates on working sets which are simply a list of assemblies
and a list of plugins (with their options) to load. So it's possible to work with few assemblies
I also did some low-level class to help generating dot files and couldn't resist trying them off for a new kind of graph (funnier than refactoring the existing ones :-). This graph shows the dependencies between assemblies, in this case the Mono.Security.dll dependencies.
The graph shows all assemblies referenced by
From a security point of view the graph adds two major informations.
And, of course, being both red (unsafe) and accessible from partially trusted callers is far more risky than only one of them could be.
Like the previous graphs assembly dependencies can get very ugly. In fact the worst cases I've seen
is for data providers.
They have a lot of dependencies themselves (and some even have unmanaged dependencies not
show in the graphs) and they often links to
4/25/2005 18:35:58 | Comments
The views expressed on this website/weblog are mine alone and do not necessarily reflect the views of my employer.