VB .NET Exe's

[mastermind94]

hi yall

i wrote a project on VB .NET and build it and everything, the machine i used have VS.NET installed and Win2K. I want to run my application on a computer without VB.NET and running Win98SE. What r the runtime files that i need to distribute with the exe file? like, in VS 6.0, i add MSVBVM60.DLL and MSCOMCTL.OCX and it worked... which ones r for .NET?

Thanks

[dis1411]

you only need one thing: the .net framework... u should find it on your windows component updates cd

[Chuki]

so when we distribute are projects, programmed and compiled in vb.net as a safe measure we will have to package the .NET framework with it? Thats gonna suck. Sometimes I send my packages over the internet and some of my clients have dialup and live in the boonies.

Theres got to be an easier way isn't there?

[VBDon]

I think future releases of Windows are gonna include the framework so therefore over a period of time must people will have the framework installed anyway.

[dis1411]

yeah.. maybe for the time being switch back to vb6

[Cander]

This is EXACTLY why I keep preaching to people telling them to learn the FRAMEWORK, how it works, how to use it, everything about it, BEFORE you start writing apps.

Something to consider.

If you work in a intranet office environment, it is not an issue.

For outside distribution, just provide a seperate link to the .NET framework, the 21 meg one, not the huge SDK. Your users will only need it once, then they will never have to download it again. And despite dial up speed, 56k can still download 21 megs in a reasonable amount of time. Just download while you sleep.

[mastermind94]

Microsoft should include VisualBasic's Runtimes in all windows versions... it is a pain to distribute an application that is 100kb in size and u have to include msvbvm60.dll which is about 1MB and the mscomctl.ocx which is 1MB also, unless u use APIs but, still a pain. gr!

[trojjer]

Erm - OK, so when you package all of the essential runtime files in with your application, it does take up some extra space... But how about using the VS6 package and deployment tool?

It includes all of the essential dependencies that the program requires within the standard InstallShield compressed CABs, and the user is also provided with the familiar GUI during installation.

P.S: That's just for client based VS6 apps - I'm not sure about .net...

[mastermind94]

nah, vs6 and .net are 2 completely different thing

[trojjer]

Oh - I heard VB.net being mentioned, but I kinda got the impression that it concerned VS/VB6 as well...

P.S: VB.NET requires similar runtime dependencies as VB? (like "MSVBMVM60.DLL", or whatever it is?)

Ah, the framework...? Nevermind then...

[Magiaus]

fusion..? fusion comiples the vb6 runtimes and all needed files into one solid exe and well often it is smaller than before because of decompilation and rebuild using asm. very nice. i imagine bitarts will do one or .net or maybe they won't who knows

[Smithy006]

conclusion:

It's clear that the future of windows programming will be based around .net and when all of the old windows Oses are phased out .Net will be a good move.

But as for the present, i feel that current solutions revolving around things like fusion and VB6, or other specialised installation procedures are the way to go in win32 development.

One thing to note, C++ has been with us through DOS, Windows 3.11, 95, 98, Me, Xp. Delphi and Java have also been with us for long periods of time as well.

Long Term Compatibility = One of these langauges or other langauges such as realbasic www.realbasic.com

Regards,

Smithy

[Bucho]

I am just finding this out.. that to distribute an application you'll also need to distribute the damn framework file that's 21 megs.. this is very uncool if you want to make things simple for your users, and if you dont want them to have to download huge files. If you're selling something this will turn people off majorly, i'm guessing.
My real app is only 1.5 megs for christ sake, tacking on 21 just seems wrong.

[Magiaus]

well also ms recomends getting the framework on its windows update site and all the os after windows.net will have it. and don't forget cable and dsl. you have to deciede on your bigest market and go with whats best. modem users and internet deploy maybe you should use vb6 and fuse it or pack it with the windows installer that came out a year or so ago... but .net is where it going from here on in for us poor MS programmers.

At least the user doesn't need the framework to see a .net web site. unlike that whole dhtml project flop in vb6.