G
Guest
HI
i've programmed to dialogs in C#. Each in one assembly. They have a COM/Interop Interface, so I could inetgrate them in an old C++ App. If the user calls a dialog for the first time, the startup time is very slow. After it is Disposed and the user calls it again or the other dialog, the startup time is much more faster for each of them
I guess, the cause of this big time diference is, that something of .NET (like CLR/Interop) is starting up the first time. Perhaps somebody has an explanation for that behaviour and a solution to initialize the the .NET-Part from C++ at the beginning of my C++-App, so the first startup of one C#-dialog need no extra time
Thanks and regard
Ralf
i've programmed to dialogs in C#. Each in one assembly. They have a COM/Interop Interface, so I could inetgrate them in an old C++ App. If the user calls a dialog for the first time, the startup time is very slow. After it is Disposed and the user calls it again or the other dialog, the startup time is much more faster for each of them
I guess, the cause of this big time diference is, that something of .NET (like CLR/Interop) is starting up the first time. Perhaps somebody has an explanation for that behaviour and a solution to initialize the the .NET-Part from C++ at the beginning of my C++-App, so the first startup of one C#-dialog need no extra time
Thanks and regard
Ralf