[RESOLVED] Deploy without .NET Framework

[mahbub73]

I created a simple exe sized 50Kb (which generates random number within user given range) by VB 2008 on .NET framework 2.0. which is about 22MB.

Is there any way that, I can distribute this file with 1 or 2 dll file and without distributing the complete .NET framework 2.0?

In case of .NET framework 3.5 the installer size is about 200MB. It is very difficult to distribute those file on the web.

Is there any solution. Pls help me.

[techgnome]

In much the same way Java apps can't run w/o the Java RunTime installed.... .NET apps cannot run w/o the FW installed.

-tg

[Lord Orwell]

if you use the actual installer from vb, it automatically checks to see if .net 2.0 is installed and if not, it will prompt them to download it from microsoft. win 7 comes with it.

another option you have is to change your targeted framework to 1.1. It's included in every win install since xp, but you shouldn't have to do anything as 2.0 is a pushed download through automatic updates, and if a user doesn't have it installed by now, it's their own fault. Most new games require it. Even my video card's control panel requires it.

[mahbub73]

Thanks for your kind reply.

[techgnome]

another option you have is to change your targeted framework to 1.1.

Only if running vb2003 .... vb2005 could only target 2.0, and VB2008+ targets 2.0, 3.0, 3.5 so the only way to target 1.1 is with vb/vs2003.

-tg

[Lord Orwell]

Only if running vb2003 .... vb2005 could only target 2.0, and VB2008+ targets 2.0, 3.0, 3.5 so the only way to target 1.1 is with vb/vs2003.

-tg

thanks for the info

[dilettante]

A JVM download is only about 10MB. The main difference with .Net is that you don't just need the CLR but also the vast set of Framework libraries.

To use a Java application you can't usually get by with the JVM alone, but you can pick and choose various "framework" subsets.

A big plus with .Net is that even though the Framework is large it has almost everything you'll ever need, and most of the visible widgets (controls, etc.) are consistent with the Windows look and feel, being based on native components underneath.

Java frameworks seem to multiply like roaches, and those containing widgets may have been designed for Mac, Linux, or what have you (whatever the author thought looked good?) and so it can sometimes be hard to make a Java application look "right" on Windows.


While I'm no particular fan of .Net there is a lot of wisdom in its approach (huge monolithic Framework) because even though it presents some pain to download that monster... once you have it you're all set. Well, until the next one comes out!