.NET file size? *RANT*
-
**Begin RANT** Man, I was in for a shock my friend just gave me an app, his first in C#, and the setup file was like 20-30Megs in size? This thing only had a couple of forms. Is this true? This is my one reason I write code that I distro off my website in straight C Win32API the file size is way smaller. This can't be true can it? Someone please tell me he messed something up while creating the distro... This would totally defeat the purpose of distro files over the NET if the setup files total 20-30 megs for a couple of forms???? Sheesh... **END RANT** HomeNuke ---- "Nuke'd Your Home, Yet?" Run your own PostNuke based web server from home http://www.homenuke.com
My msi package is 9 MB with Acrobat reader and about 10 large images in it...the installer without those files is <= 1MB. Your friend really screwed something up... David Stone dstone@newcenturytitle.com
Procrastination is like masturbation; it's all good until you realize you just screwed yourself. -Writing on a bench at college -
It probably included the .NET runtime. Your users will need that installed but you can always package it separately from your application insatller. Todd Smith
I haven't been able to package it with...how do you??? David Stone dstone@newcenturytitle.com
Procrastination is like masturbation; it's all good until you realize you just screwed yourself. -Writing on a bench at college -
**Begin RANT** Man, I was in for a shock my friend just gave me an app, his first in C#, and the setup file was like 20-30Megs in size? This thing only had a couple of forms. Is this true? This is my one reason I write code that I distro off my website in straight C Win32API the file size is way smaller. This can't be true can it? Someone please tell me he messed something up while creating the distro... This would totally defeat the purpose of distro files over the NET if the setup files total 20-30 megs for a couple of forms???? Sheesh... **END RANT** HomeNuke ---- "Nuke'd Your Home, Yet?" Run your own PostNuke based web server from home http://www.homenuke.com
His setup included the .NET runtime or CLR, which is 20-25mb (I think...) This is only necessary if the target system does not already have it installed. (Which is probably most systems currently.)
Bruce Duncan, CP#9088, CPUA 0xA1EE, Sonork 100.10030
Arthur-Anderson, proud sponsor of the Corporate Make A Wish Foundation. -
**Begin RANT** Man, I was in for a shock my friend just gave me an app, his first in C#, and the setup file was like 20-30Megs in size? This thing only had a couple of forms. Is this true? This is my one reason I write code that I distro off my website in straight C Win32API the file size is way smaller. This can't be true can it? Someone please tell me he messed something up while creating the distro... This would totally defeat the purpose of distro files over the NET if the setup files total 20-30 megs for a couple of forms???? Sheesh... **END RANT** HomeNuke ---- "Nuke'd Your Home, Yet?" Run your own PostNuke based web server from home http://www.homenuke.com
-
C# doesnt cater to small desktop applications well at all. C# for small desktop applications is like using a rocket engine to get a kite off the ground.
Mark A wrote: using a rocket engine to get a kite off the ground But that would be really cool to see.
-
C# doesnt cater to small desktop applications well at all. C# for small desktop applications is like using a rocket engine to get a kite off the ground.
Mark A wrote: C# doesnt cater to small desktop applications well at all. C# for small desktop applications is like using a rocket engine to get a kite off the ground. Right now you're probably right, but in a year or two the .NET runtime will be as readily available in every desktop as shell32.dll, user32.dll or gdi32.dll.
Eddie Velasquez: A Squeezed Devil
Checkout General Guidelines for C# Class Implementation -
Mark A wrote: C# doesnt cater to small desktop applications well at all. C# for small desktop applications is like using a rocket engine to get a kite off the ground. Right now you're probably right, but in a year or two the .NET runtime will be as readily available in every desktop as shell32.dll, user32.dll or gdi32.dll.
Eddie Velasquez: A Squeezed Devil
Checkout General Guidelines for C# Class ImplementationEddie Velasquez wrote: Right now you're probably right, but in a year or two the .NET runtime will be as readily available in every desktop as shell32.dll, user32.dll or gdi32.dll. How do uop come that conclusion Eddie ? just curious. Regardz Colin J Davies
Sonork ID 100.9197:Colin
I am sick of fighting with Martin, I think I will ignore his posts from here on in, and spend the time working on articles instead. Christian Graus
-
Eddie Velasquez wrote: Right now you're probably right, but in a year or two the .NET runtime will be as readily available in every desktop as shell32.dll, user32.dll or gdi32.dll. How do uop come that conclusion Eddie ? just curious. Regardz Colin J Davies
Sonork ID 100.9197:Colin
I am sick of fighting with Martin, I think I will ignore his posts from here on in, and spend the time working on articles instead. Christian Graus
Colin Davies wrote: How do uop come that conclusion Eddie Well, service packs, upgrades, etc. The adoption of (and transition to) .NET (the new "Win32": in the sense of a bunch dlls that make up the os) will be faster (IMO) than that of Win32 from Win16 and from DOS to Win16. Why? Well internet makes a hell of a difference!
Eddie Velasquez: A Squeezed Devil
Checkout General Guidelines for C# Class Implementation -
Colin Davies wrote: How do uop come that conclusion Eddie Well, service packs, upgrades, etc. The adoption of (and transition to) .NET (the new "Win32": in the sense of a bunch dlls that make up the os) will be faster (IMO) than that of Win32 from Win16 and from DOS to Win16. Why? Well internet makes a hell of a difference!
Eddie Velasquez: A Squeezed Devil
Checkout General Guidelines for C# Class ImplementationI'm wondering, how long it will take for popular Net apps to appear. I don't even think its included in XP yet ? [ unsure ] And I haven't seen a big push by MS to flood the bandwidth with it yet. I really think its going to trickle onto PC's over the next few years. Anyhow, Lets arrange to discuss this on 19/July/2003 :-) Regardz Colin J Davies
Sonork ID 100.9197:Colin
I am sick of fighting with Martin, I think I will ignore his posts from here on in, and spend the time working on articles instead. Christian Graus
-
I'm wondering, how long it will take for popular Net apps to appear. I don't even think its included in XP yet ? [ unsure ] And I haven't seen a big push by MS to flood the bandwidth with it yet. I really think its going to trickle onto PC's over the next few years. Anyhow, Lets arrange to discuss this on 19/July/2003 :-) Regardz Colin J Davies
Sonork ID 100.9197:Colin
I am sick of fighting with Martin, I think I will ignore his posts from here on in, and spend the time working on articles instead. Christian Graus
Colin Davies wrote: don't even think its included in XP yet I think it will be included in SP1. Colin Davies wrote: I'm wondering, how long it will take for popular Net apps to appear. I remember when I wondered how long it would take for popular Win32 apps to appear. :) I think it will be pretty soon, at least compared with the Win16 and Win32 adoption rate.
Eddie Velasquez: A Squeezed Devil
Checkout General Guidelines for C# Class Implementation -
Colin Davies wrote: don't even think its included in XP yet I think it will be included in SP1. Colin Davies wrote: I'm wondering, how long it will take for popular Net apps to appear. I remember when I wondered how long it would take for popular Win32 apps to appear. :) I think it will be pretty soon, at least compared with the Win16 and Win32 adoption rate.
Eddie Velasquez: A Squeezed Devil
Checkout General Guidelines for C# Class ImplementationYes, that makes me think about how "ready" .NET is for a 64 bit OS. I guess thats at the compiler level rather than Intermediate Language level. Regardz Colin J Davies
Sonork ID 100.9197:Colin
I am sick of fighting with Martin, I think I will ignore his posts from here on in, and spend the time working on articles instead. Christian Graus
-
He must be including the .NET run-time along with the app. Actually .NET applications are generally quite a bit smaller than C++ apps (with the same functionality).
Actually, thier about the same as long as you don't statically compile with the CRT in your C++ apps. I frequently compile with the ATL library and some of my smaller exe's are only about 4K.
-
Yes, that makes me think about how "ready" .NET is for a 64 bit OS. I guess thats at the compiler level rather than Intermediate Language level. Regardz Colin J Davies
Sonork ID 100.9197:Colin
I am sick of fighting with Martin, I think I will ignore his posts from here on in, and spend the time working on articles instead. Christian Graus
The only type that is bit sensitive would be IntPtr, and it was built to handle that change. The CTS has defined types so that they are strict, unlike C/C++ where only a relation is held between them. Some types defined by the CTS are Int16, Int32, Int64; I think we can all tell what the numbers mean :) While the CTS is 64 bit ready; the CLR is not. Currently there is no 64bit implementation of the CLR; not to say that there won't be there just isn't one yet. James "Java is free - and worth every penny." - Christian Graus
-
Mark A wrote: C# doesnt cater to small desktop applications well at all. C# for small desktop applications is like using a rocket engine to get a kite off the ground. Right now you're probably right, but in a year or two the .NET runtime will be as readily available in every desktop as shell32.dll, user32.dll or gdi32.dll.
Eddie Velasquez: A Squeezed Devil
Checkout General Guidelines for C# Class ImplementationEddie Velasquez wrote: Right now you're probably right, but in a year or two the .NET runtime will be as readily available in every desktop as shell32.dll, user32.dll or gdi32.dll. Yeah but if they keep changing it like MFC then we have to distro apps with that anyways like I do now with MFC42 :( Code4Food ---- "There is no try; only do or do not" -Yoda
-
Sounds like the setup had the .NET RunTime included.
You don't need to sleep to see a nightmare Anne Clark [sighist]
-
His setup included the .NET runtime or CLR, which is 20-25mb (I think...) This is only necessary if the target system does not already have it installed. (Which is probably most systems currently.)
Bruce Duncan, CP#9088, CPUA 0xA1EE, Sonork 100.10030
Arthur-Anderson, proud sponsor of the Corporate Make A Wish Foundation. -
Eddie Velasquez wrote: Right now you're probably right, but in a year or two the .NET runtime will be as readily available in every desktop as shell32.dll, user32.dll or gdi32.dll. Yeah but if they keep changing it like MFC then we have to distro apps with that anyways like I do now with MFC42 :( Code4Food ---- "There is no try; only do or do not" -Yoda
Code4Food wrote: Yeah but if they keep changing it like MFC then we have to distro apps with that anyways like I do now with MFC42 .NET's builtin versioning of assemblies prevents this scenario (bye, bye dll hell)
Eddie Velasquez: A Squeezed Devil
Checkout General Guidelines for C# Class Implementation -
Code4Food wrote: Yeah but if they keep changing it like MFC then we have to distro apps with that anyways like I do now with MFC42 .NET's builtin versioning of assemblies prevents this scenario (bye, bye dll hell)
Eddie Velasquez: A Squeezed Devil
Checkout General Guidelines for C# Class Implementation -
So we don't need to include the .NET runtime? Everytime I build an install I include the crazy MFC24 DLL (if I used MFC) I don't think most systems will have .NET installed on them yet. Code4Food ---- "There is no try; only do or do not" -Yoda
-
That sounds good what about the fact that people can decompile your code/dll? Are they going to solve that? Code4Food ---- "There is no try; only do or do not" -Yoda
Well, there are pretty good decompilers for native code (granted, the output isn't as nearly as complete as an IL decompilation) and that hasn't stopped development. There are superb Java decompilers and that hasn't stopped java development either. There are good .NET obfuscators that will deter most reverse engineering, but if your code is so sensitive it shouldn't be out there anyway, expose it as a web service or something.
Eddie Velasquez: A Squeezed Devil
Checkout General Guidelines for C# Class Implementation