.NET Application Size of EXE

Hi Experts,

We are presently developing a medium scale ERP software for which the development platform is .Net 4.0 (VS 2013), with Vb.Net language. , Crystal report, third party tools from Syncfusion are also used extensively.

As the project is expanding we have concerns about the size of the EXE file., presently the exe file size is around 23 MB.

We like to get knowledge about issues / limitations / compatibility that can arise with higher EXE file size (around 50 MB), from point of view of client usage and development environment both.

Regards.
TeamARCAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

käµfm³d 👽Commented:
What kind of devices are the client machines?
0
vastoCommented:
Fire your architect! 23 mB exe means you are writing everything like in 1990
0
TeamARCAuthor Commented:
Client Devices are Destkop PC's
0
Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

käµfm³d 👽Commented:
Then I'd be inclined to somewhat agree with the above sentiment:  That's really small in terms of today's executables.
0
Jacques Bourgeois (James Burger)PresidentCommented:
50 MB on todays computer that have 4 GB on average? And knowing how .NET manages code in memory? This means nothing.

What you have to consider is not the size of the application, it's the size of the data in memory.

I would be more afraid of a 1KB .exe that creates an array of 10,000,000 strings in memory might cause problems than I would be of a 50 MB .exe

It's the design of the application and the way it handles things in memory that is important. What can cause trouble is loading a whole table from your database when you need to display only a few records. What can cause trouble is creating a lot of objects that are not disposed of properly.

These are the types of things that should concern you as far as size is concerned.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TeamARCAuthor Commented:
Thanks for your suggestions and vital inputs.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.