One Assembly Versus Multiple Assemblies
-
Hi - can some one help me out here please - I'm new-ish to C#. What are the performance implications of creating all my objects (forms, classes etc) inside one assembly versus splitting up the application over multiple assemblies? I would prefer to keep every thing in one as I find it easier to work with and I won't get the cyclic error where by a form in one refers to a form in another which refers back to the original etc. If I do put eveything in one assembly, will the application take longer to start up? Will opening forms be quicker using the one as the app won't need to open more than one assembly to find the correct opened form etc? Thanks
-
Hi - can some one help me out here please - I'm new-ish to C#. What are the performance implications of creating all my objects (forms, classes etc) inside one assembly versus splitting up the application over multiple assemblies? I would prefer to keep every thing in one as I find it easier to work with and I won't get the cyclic error where by a form in one refers to a form in another which refers back to the original etc. If I do put eveything in one assembly, will the application take longer to start up? Will opening forms be quicker using the one as the app won't need to open more than one assembly to find the correct opened form etc? Thanks
-
MarkB123 wrote:
can some one help me out here please
Sure why not, click here[^] I always enjoy helping the Google impaired.
I like. Less blatant than the original which practically required a tiny URL to slip past any but the blindest. :-D
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
-
MarkB123 wrote:
can some one help me out here please
Sure why not, click here[^] I always enjoy helping the Google impaired.