Visual Basic .Net - DLL file question

**firewolf** · September 17th, 2003, 05:33 PM

I'd like to know how to create the .dll file so i can use my programs on other computers. The first program I made created the .dll file on its own but I may have changed something and now it does not make the .dll file anymore. Does anyone have an idea as to what I'm doing wrong or must do?

Building Solution
Rebuilding Solution

Building *****
Rebuilding *****

I have tried already, as well as the Configuration Manager to Release and Debug.

**Whir** · September 17th, 2003, 05:35 PM

Usually the program packager grabs all the dlls you need. Do you use that, or just grab all the files in the program's directory and move them to a different PC?

**firewolf** · September 17th, 2003, 05:37 PM

All i do is click Build Solution and/or Build program and it creates all the files.... now except the dll files

**Whir** · September 17th, 2003, 05:38 PM

Hmmm, not sure then. I've never had the problem. Sorry I couldn't help.

**firewolf** · September 17th, 2003, 05:42 PM

It's all right.

Could you explain what you yourself do to make a program so it is accessible on all Window-based operating systems, please? Maybe there is something i'm doing wrong.

**Whir** · September 17th, 2003, 05:46 PM

I just use the program packager. I've never had a problem with it yet. I don't use .NET either though, I'm still using VB6. I could install VB.NET and see if I could find the option you're looking for, but I'd have to wait until tomorrow. My roommate has the discs at work.

**firewolf** · September 17th, 2003, 05:48 PM

That'd be great

Please do so if you have the time.

Also, one thing, what is "program packager" is that another program or is it part of VB?

**Whir** · September 17th, 2003, 05:53 PM

It's probably the same as using Build Solution in VB.NET. It grabs all the relevant files that the executable needs, and packages them all into an installer executable.

**firewolf** · September 17th, 2003, 06:06 PM

this is what I do and where the files go...

**vass0922** · September 17th, 2003, 06:23 PM

1. Why do you want a dll? Its not needed to make it work on other machines. You only use a DLL if you want to call it from another application. You'll want to compile as an EXE

2. ANY Machine you want to run it on will REQUIRE the Stinkin' .NET Framework (automatically installed for your bugginess satisfaction via Win2k SP3).

Otherwise, when you compile the file should show up in the bin folder unless its throwing an error.

Are you sure you're BUILDing and not just debugging?

If you only have one file a packager isn't really necessary unless you want a single click install your app into a folder, and the .net framework (lemme tell ya its a PITA!!!! ) to get it working correctly.

**firewolf** · September 17th, 2003, 06:33 PM

i sent a program to a friend and it asked for that .dll file

i debug and release (options for building),

long ago i had vb4 but my knowledge just decided to take a permanent vacation and im back to sqaure one

**vass0922** · September 17th, 2003, 06:42 PM

Oh you sent him an exe and it requested the .dll?

Ummm what's teh DLL name?

Does he have the .NET Framework installed?

**firewolf** · September 17th, 2003, 07:20 PM

i sent him every file vb made and no he doesn't have nor need .net framework, visual basic .net has it in itself to create programs for other computers that do not have the vb program, or so it says

**vass0922** · September 17th, 2003, 07:38 PM

No he does not need VB.NET installed

He DOES need the .NET framework

If you find a link that says otherwise, I'd suggest he install it.

You see the problem with VB.NET is it doesn't compile into machine language. It compiles it MSIL (Microsoft Intermediate Language) Its kinda like Java. It compiles it into a intermediate language that when you double click the application its then INTERPRETED. Its kind of a hybrid language.

SLOW startups are the worst which VB.NET pretty much requires.