VB.Net .exe's

Rhino · June 9th, 2002, 02:26 AM

OK, it seems pretty easy to create an .exe for a windows app, but is there anythign one would need to do to move the .exe to another PC? Do you have to have the .Net framework installed on the other PC? Or can I just put the .exe on the other PC?

With VB 6, they had that package deployment wizard that would include all neccessary files to install and use your app that you made. I don't see anythign like this in .Net

And Vass, if you read this, my observation on it now, is that in some cases, you can actually use LESS code in .Net than VB 6. Especially stuff like performing sql commands on am OLEDB database. All you do is add a oledbcommand control to your form, on the text property, it brings up a query builder window similar to MS Access query design view. Very slick. Then you just tell it to execute in your code.

vass0922 · June 9th, 2002, 03:04 AM

Only one way to find out

I found this in the VS.NET help...

Quote:

Deployment to computers with the common language runtime already installed could not be simpler. Our simple program can be run directly from a file server (more advanced programs might involve security issues), in which case, no files are placed on the workstation, no entries are made in the registry and, in effect, there is no impact at all on the workstation. This also means that there is nothing to clean up, because there is nothing to uninstall. A related benefit is that running this program cannot break another program, nor can any other program cause this one to stop functioning.

As you would expect, Hello.exe can also be copied to a local volume. In this situation, simply deleting the file is sufficient to uninstall the program and, again, nothing remains on the workstation.

But not sure if that is assuming the framework is already installed

After that it starts getting into assemblies and such and gets really confusing

and I haven't had time to really look into it to really understand it...

What book are you using to learn it?
deitel?
O'Reilly?
http://www.vb-world.net/misc/vbnetuncovered/
I just found a tutorial thingie, I'm gonna read through.. see if I can find out more ..

Rhino · June 9th, 2002, 03:11 AM

Yeah, they seem to be mainly concerned about running like a shortcut to a file on a network. Well maybe I'll have to get a diskette and try it on another PC. Will have to make another app though cuz the one I made connects to a DB, so it wouldn't work anyways.

vass0922 · June 9th, 2002, 03:30 AM

WHOOPS .. just found your answer

Quote:

Top Tip: Remember– you need the .NET Framework before you can run any program created in a .NET language. Just a warning.

On the 2nd page of the tutorial I noted above....

Rhino · June 9th, 2002, 12:39 PM

Man that sucks. Now I'm gonna have to figure out how to install it on other PCs.

I'm using a .Net for dummies book. Not very in-depth cause it covers all .Net languages. I think I will look at your link after work. Thanks Vass.

vass0922 · June 9th, 2002, 01:34 PM

ahhh never had much luck with for dummies books.. not exactly a connieuseur of them though

So far the page isn't too bad, kinda slow though lol

However, its taking things ONE (and only one!) step at a time lol

vass0922 · June 9th, 2002, 03:14 PM

http://www.vb-world.net/misc/vbnetun...d2/index6.html
Very interesting page

THE BEST PART!!

Quote:

New Operators - VB.NET brings with it a few new arithmetic operators to help cut down your code. For example, "X += 4" in VB.NET will do what "X = X + 4" did in VB6. Try playing with these too: "X -= 10, X *= 2", "X /= 13", "X \=13", "X ^= 3", "X &= " OK"

+- operators!!
Man those things are great! LOL
not sure on the X &= " OK" though?

Thought maybe it was logic, but doesn't seem to be...

Hmm just found another one...

Quote:

Default ByVal - By default, all parameters are now passed 'by value' as opposed to 'by reference'. To be safe, make all declarations explicit

strangerstill · June 9th, 2002, 06:40 PM

In Basic, & is the string concatenation operator. You figure the rest out...

vass0922 · June 9th, 2002, 06:43 PM

ahhhh Wunderbar!
Thanks.. duh didn't think about that

UncaDanno · June 9th, 2002, 10:41 PM

You see, that's the whole deal....
With VB6, people harp that the size of the distribution is so large. But that is because it contains the VB6 runtime and any other common dlls that are used by the app. In most cases, however, these dlls are already on the target machine so installing the app doesn't eat up that much more real estate.

With .NET, the siren song is the CLR (Common Language Runtime), aka the .NET framework. Which is likely NOT already on the target machine(s) and which does eat up a lot of resources. That is why M$ is careful to say that :

Quote:

Deployment to computers with the common language runtime already installed could not be simpler.

(emphasis mine).

Part of the effect of .NET is to commoditize developers (coders/bit-flippers). The people who will make the REAL money with the .NET "paradigm" will be the ones who can HOST Web Services.

And guess who the only outfit is that has been anointed by M$ as a certified Web Services host?