I just got a look at this message, the only thought I had here is that you
might be seeing the security system writing out the .cch file. This file is
basically a cached version of the policy with assorted evaluations
precomputed.
I believe that the cache is not in fact computed all at once, but rather the
machine policy precomputations are written out on the first run and then per
user information on a subsequent run. After that the cache is good until
policy/evidence changes.
The purpose of the cache is to avoid expensive ResolvePolicy calls when the
application is loaded and instead just do some fairly simple parsing.
This might explain some of what you're seeing but it doesn't seem like a
complete answer to me. Snoop around for .cch files being created, it might
put you on the right path.
-Rico

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
Rico Mariani
CLR Performance Architect
--------------------------------------------------
> Folks -
>
[quoted text clipped - 22 lines]
>
> Ice
Ice - 30 Mar 2004 22:30 GMT
Well you made me look for files that are getting modified when the app
closes and I think the app.exe.ini files that get updated are the culprit.
The bigger the file, longer it takes to update it. The first instance of
the app started is responsible in updating the .ini file when it closes.
ice
> I just got a look at this message, the only thought I had here is that you
> might be seeing the security system writing out the .cch file. This file is
[quoted text clipped - 45 lines]
> >
> > Ice
Ice - 31 Mar 2004 15:44 GMT
I think this could be a good argument for "fewer" assemblies.
ice
> Well you made me look for files that are getting modified when the app
> closes and I think the app.exe.ini files that get updated are the culprit.
[quoted text clipped - 69 lines]
> > >
> > > Ice