DLL Distribution 1

[SiJP]

I'm a little unsure of what is trying to be achieved here (.net n00b), so researching my scenario is a little confusing - I will try to explain as best as possible.

I have written a vb.net class, and built it as a DLL for COM Interop. I have done this by using VS.net 2002.

I can build this solution, and get a resulting DLL in the obj/release folder ("myName.dll").

Once I copy this dll to my local system32 folder (WinXP) I then can use the DLL through VB on my local machine, with no problems.

I now wish to distribute this DLL to people using my VB app. Is it a simple case of copying the DLL to the system32 folder of target machines?

Or is there a little more too it?!

Thanks

------------------------
Hit any User to continue

 

[TipGiver]

the best way is to add a setup project. With this you can decide if you want any reg entries, place shortcuts of the exe anywhere...

The dll is important for your app, "prequisites" i think is the right word.

It is not good to add the dlls in system folder.If you have any problems adding correctly the setup project,post a new question.

 

[SiJP]

Thanks,

I've had a go a doing one of these, and eveything seems to work ok... the only thing is the installation requires a user interface, with options that I would prefer to set silently. Is there any way to achieve this?

Thanks for your help

------------------------
Hit any User to continue

 

[TipGiver]

That dll is doing something specific and you release it so other DEVELOPERS can use it?

If yes then the other developers should better add a reference to it. If they copy it in system32 vb will work fine as you said before, but it is not the best way to use it. Leave the folder system32 for windows' use.

I'll say an example.
You can install java and write your programs. From the prompt you should compile it using: javac name.class etc.
This won't work because it cant find the javac.exe file. If you grab the java files (exe files like java, javac and many others) and copy in system32 there won;t be any problem. Although the best way is to add the bin folder of the installation in the environment variable $PATH.

So let them use it and let them have to make a setup project. You can use the dlls if they are in:
-the same folder with the executable file.
-system32 folder (better not)
-using a setup project.

 

[chiph]

Don't forget that this is a .net assembly, so any machine on which you intend to run it will have to have the .net runtime installed.

see faq796-1807

Chip H.


____________________________________________________________________
Donate to Katrina relief:

http://s1.amazon.com/paypage/PELYGQVJ8Q7IB/103-6821258-5919825

If you want to get the best response to a question, please read FAQ222-2244 first

 

[SiJP]

TipGiver - good advice. The DLL is not for developers to integrate with, simply for an existing VB app of mine to 'use'.

I'll leave the setup package to do it's stuff, and just have the setup interface as another step for clients to do!

chiph - yep, got that covered! The runtime files are installed with the setup package, if not already there.

Cheers guys!

------------------------
Hit any User to continue

 

[SiJP]

Ok, Another question:

When the dll is 'installed' using the setup package, the name of my applciation appears in the 'Add/Remove Programs' list that windows provides.

The icon next to it is a windows standard one. I already have an icon I want to use, but I can't seem to work out how to add it to my project.

The Common Properties > Build > Application Icon option is disabled (greyed out) and I can't find any properties to add the path..

Any Clues?

Thanks

------------------------
Hit any User to continue

 

[TipGiver]

You cannot "install" a dll. With a setup project all required files (other exe, dlls, txt , ...) are copied in //program files/[company_name]/[application_name] or anywhere else you specify. The icon for a dll is standard.

You can set an icon for the main, and not only, application of yours (.exe) which will appear in the task-bar.

Also there is a default icon for setup projects, which you can change it from its properties. If i am correct, when you right click the setup project (added in your solution) and choose Build the output result will be some files: .exe, .msi, perhaps the .NET Framework and an other one "text file" setup.i_dont_remember_the_extension

 

[SiJP]

Lovely, thanks once again.

------------------------
Hit any User to continue