Compilation Chain issues

Hi all,

I wrote a bunch of BRules and a couple of Assemblies (in different workspaces) that work together to perform calculations. So in the end I have a dependency chain like this:

BR => Assembly => Assembly

Things works like a charm.

Sometimes, after I made changes to an Assembly, I get a weird error saying that OneStream cannot find my assembly. While this is true when it cannot compile correctly (due to errors), it doesn't make sense to me when it compiles fine.

Even if I compile my assemblies before I run the BRules, sometimes it happens.

I'm trying to find out an explanation and I thought that:

1. I run the BRule and OneStream think that Assembly1 - a dependence - is "old", so....
2. OneStream start compiling Assembly1, and, while compiling it, OneStream think that Assembly2 - a dependence -  is "old", so....
3. OneStream start compiling Assembly2

Maybe these compilations are running async and in parallel... And, maybe, the last compilation takes too much time, taking the first one returning the error.

This is just an idea that could explain this issue, but I'm quite sure this is the right way: when I started working on OneStream, my code wasn't affected, IMHO because the assemblies were small enough to be compiled in a reasonable time. But now they are growing up, and the compilation time is growing too.

In any case, I'm wondering it there's a way to solve this annoying issue: I often have to (re)launch the same BRule and, on a customer's perspective, seeing a compilation error (even if fake) doesn't make a good impression.

Thanks

FabioG