Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Is 22MB too big for dll file ?

Posted on 2004-09-30
6
Medium Priority
?
225 Views
Last Modified: 2010-04-15
Hi everybody
I have dll file with bunch of windows forms and it's pretty heavy about 22MB.
I just wonder how it could affect my application. Due to specification of application would be a little bit hard to spread these forms into different dll files. Each form is base on one mother form, but some forms have some unique elements that can’t be visible on other.
Should I do something with this 22MB or it doesn't matter as long everything works.

Thanks
0
Comment
Question by:knobloch
6 Comments
 
LVL 19

Expert Comment

by:drichards
ID: 12195024
It depends on how you use the components in the dll and how they are constructed.  If you use all or most of the components in each application that invokes the dll, then you might as well keep one big dll.  If you use the dll in several apps and each app only uses a subset of the components, then it would make sense to split it up.  Another reason to split it up would be so you can develop the independent parts withoug rebuilding the whole thing.  If you have a couple of common base clases upon which everything else is built, it might make sense to put those in a separate dll as well.

Without more details, it's not a simple yes/no anwser.
0
 

Author Comment

by:knobloch
ID: 12196625
My application has 10 product catalogs and this particular 22MB dll file contains components for one of the catalogs.
It is used only when user is using this specific catalog otherwise it is not used.



0
 
LVL 14

Expert Comment

by:AvonWyss
ID: 12197354
I have used DLL's with over 100MB in size (many resources inside it) without noticing any problems. The needed parts are paged in and out just as needed, so that there isn't a long load time nor does it block tham much physical memory. No problem.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
LVL 18

Expert Comment

by:armoghan
ID: 12197610
22 MB is very less, the momory size has increased a lot,
But you have to check the client RAMs
and if it is resources i.e. images
They come and go if you are not loosing references in your application.. GC takes care of them
I mean, if you are not opening many images in one time in the application
0
 
LVL 19

Accepted Solution

by:
drichards earned 1600 total points
ID: 12199435
If all the components in the dll relate to the one catalog and they are all needed when that catalog is used, then there is no benefit to your app in splitting up the dll.  There are still the development considerations, but you would best know that.  Unless you plan for the dll to be undergoing major development, then it's probably best to just leave it as is.
0
 

Author Comment

by:knobloch
ID: 12201108
Thanks
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Entity Framework is a powerful tool to help you interact with the DataBase but still doesn't help much when we have a Stored Procedure that returns more than one resultset. The solution takes some of out-of-the-box thinking; read on!
Performance in games development is paramount: every microsecond counts to be able to do everything in less than 33ms (aiming at 16ms). C# foreach statement is one of the worst performance killers, and here I explain why.
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data. But that feeling is fleeting. Attacks these days can happen in many w…
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…

886 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question