That works, thank you. However, I did not expect to need to change the generated code.

Well, one option is to use a memory mapped file to get shared access to the data. There is an article here about it: DevGlobalCache – A way to Cache and Share data between processes[^] That's C++ but you may be able to rework it to C# depending on how confident you feel about that sort of thing. Alternatively, you could have one central "cache manager" that loads the cache into memory on system start-up, then the other processes link to it using named pipes or something to load the cache into their local memory when they initialise (or lazy-load the cache as they need it). Or, you could load the cache once, then serialise it out to disk in an easy to read format that can be loaded back when needed. Depending on what is involved in loading the cache, reading a serialised stream in from local disk might be quicker than re-initialising the cache from the ground up each time. The problem with these solutions is keeping the cache synchronised across all instances, but from what you say that doesn't sound like it's going to be a problem for you.

I've found the solution: criteria.SetProjection(Projections.RowCount()); int totalRecordsFound = (int)criteria.UniqueResult();

Simon Stevens wrote: The default value is hard coded as an attribute on the property Thanks, that's what I've been looking for.

using the /nothread option helped, but i still don't know why :/

buchstaben wrote: I guess there is a way using Reflection, so could anyone give me a hint on where to start? This Article[^] might be as good a place to start as any led mike

It looks like your SettingsPropertyValueCollection is getting corrupted, so that the values in the _Indices HashTable doesn't correspond to the size of the _Values ArrayList. The class itself should be pretty well tested, so there might be something in your code that is accessing some memory that it shouldn't. Typically that's only possible when using reflection, unsafe code blocks or calls to unmanaged code. Despite everything, the person most likely to be fooling you next is yourself.

That hurts my eyes. (Not that I should talk. :-O )

Your code here does not show HibernateDAO as static. Also it cannot be static as written due to the generics. You have to make the class a strong type and define it explicitely as static in order to get a static class. All you've done is define a static method inside an instance class. You need something like this: public static class Hibernate { ... }

Pete O'Hanlon wrote: This sounds like you are getting a bit confused architecturally. Don't restart the application - just kill the threads (be aware that this is really frowned upon though). just killing the threads wouldn't help, since i must ensure each background thread runs every main run. a main run simply covers invoking all registered background threads, starting a timer and wait for the timer's and threads' ready-events. if both, timer and all threads are ready, start a new main run. if timer is ready since x seconds, (assuming non-expected exception) the app should ignore the background threads' states and stop current main run. now all background threads have to be killed and invoked again. that's actually what my goal is. architecturally this should be ok, shouldn't?