I gave your method a try, I actually posted to the list about the exact
thing before I got your email.
Worked fine for me, I use the sdk compiler so I had to make a new make file
but that was very
I would suggest adding a tidbit about what references you need to make
in the new dll. I used
esperantus, rainbow, system, system.data, system.drawing and system.web.
The actual compile time for the dll went from about 20 seconds to a
blink of the eye as it
was compiling 10K instead of 790K. I did observe that if I re-compiled the
module's dll, pages that
did not even have that module still redid the JIT compilation.
Thanks a bundle. Now all I have to do is figure out a way to get it to JIT
compile faster. Maybe when
I get money I'll add a gig of ram to it and a faster cpu. It takes about
30 seconds each time I re-compile
the dll to load the page(JIT compile part).
I really really hope that future versions of .net will allow
pre-compiling the client code into the dll. There
isn't any benefit to JIT compilation for me and it sure does slow things down.
At 05:21 PM 1/5/2004 -0700, you wrote:
>Cory was nice enough to show me how to make Private Module Assemblies that
>I could just Plug-Into Rainbow. We both agreed that I should document my
>findings, and as a result, I give you this guide.
>The document also talks about how to debug your plug-in modules from
>within VS.Net while Rainbow is running.
>Please let me know if you find any errors.