[ask] about power pack

[allopiloping]

i have a program that consist rectangle from the powerpack....

but why it can't run in the other computer that doesn't have power pack installed???

another question....
some of my program run well in my computer, but why it can't run well in the other computer....??? the program doesn't using any tools

thx

[alex_read]

You are assuming we all know what the "PowerPack" is here. At a guess, as I for one have no idea what this is, I would assume this is a reference or control or component you are adding to your Visual Studio project and therefore it is probably contained within a DLL or OCX or similar file which requires registering and possibly licencing upon the machine where it is to be used upon.

With regard to the second part of your question, how are you distributing your application, are you creating a setup program properly? Well even before that - what is your application for? what external applications or technologies does it interact with and what are the Operating Systems which you are compiling your project on, and distributing your application to? Can you define "can't run well"? - what behaviours and possibly error messages do you experience when you run this program upon your target environment?
You haven't really given us much information to go on at all here! As another guess, which is all we can do here, I would imagine possibly you aren't creating a setup program correctly for your application, or you are targeting a .Net framework version which is possibly not installed upon the target computer.

[Joacim Andersson]

As Alex mentioned you must distribute all the extra controls you are referencing. In this case you must copy the VBPowerPack.dll file to the destination computer. Since that is a .Net assembly you do not have to register it, just copy it to the same folder as your EXE file will do it.

[allopiloping]

As Alex mentioned you must distribute all the extra controls you are referencing. In this case you must copy the VBPowerPack.dll file to the destination computer. Since that is a .Net assembly you do not have to register it, just copy it to the same folder as your EXE file will do it.

how to do it????

can u give me the code or the way

[jmcilhinney]

The required DLL should already be in your bin folder along with your EXE. Just distribute them both instead of the EXE alone. If it isn't there already then go to the References tab of the project properties and make sure Copy Local is set to True for that reference, then rebuild.

[allopiloping]

The required DLL should already be in your bin folder along with your EXE. Just distribute them both instead of the EXE alone. If it isn't there already then go to the References tab of the project properties and make sure Copy Local is set to True for that reference, then rebuild.

can u give me the detail step to do it???

how to input the power pack dll???

i never do like this

is there any related site???

thx

[jmcilhinney]

Have you looked in your output folder, i.e. the folder your EXE gets created in when you build? Is the PowerPack DLL definitely not there?

[allopiloping]

Have you looked in your output folder, i.e. the folder your EXE gets created in when you build? Is the PowerPack DLL definitely not there?

yes....there's not in there......

how to put in the folder???

[sytto]

If you used default installation and have installed on the C: drive it will be in this folder.

C:\Program Files\Microsoft Visual Basic 2005 Power Packs\3.0\Microsoft.VisualBasic.PowerPacks.dll

[allopiloping]

If you used default installation and have installed on the C: drive it will be in this folder.

C:\Program Files\Microsoft Visual Basic 2005 Power Packs\3.0\Microsoft.VisualBasic.PowerPacks.dll

so when i deploy my project i put the dll into where??

[Joacim Andersson]

In the same folder as the EXE file.

[jmcilhinney]

yes....there's not in there......

how to put in the folder???

You do as I said earlier. You go to the References tab of the project properties, select the PowerPack reference and then set its Copy Local property to True. When you next compile the DLL will be copied to your output folder along with your EXE. You should never have to get libraries from any source other than your output folder. Any libraries you need to explicitly distribute should be copied to the output folder using this approach.

[allopiloping]

You do as I said earlier. You go to the References tab of the project properties, select the PowerPack reference and then set its Copy Local property to True. When you next compile the DLL will be copied to your output folder along with your EXE. You should never have to get libraries from any source other than your output folder. Any libraries you need to explicitly distribute should be copied to the output folder using this approach.

i still can't do it too....

is there anyone can help me???

i will send the whole code...and is there anyone can made it for me???


thx

[jmcilhinney]

Can't do what? It's a fairly simple operation. What have you actually tried and what actually happened? Have you opened the References tab of the project properties?

[allopiloping]

i mean.....after i do what have u said....i still can't make it become portable

how to make become portable???

thx

[jmcilhinney]

So, you've set the Copy Local property of the Power Pack reference to True, correct? If so, the Power Pack DLL will be copied to the output folder along with the EXE. You need to distribute them both but, then, you already know that because I said it in my first post.

[jmcilhinney]

I see you've posted to someone else's thread with this same question. In that thread the OP is asking how to create a Setup project. Are you using a Setup project? If so then why haven't we heard about it? If not then why are you posting to that other thread?

[allopiloping]

i need this two purpose.....

i posted coz it's my first question......so when i see another thread has my other question....so i ask there too.....

now i can do what u say jim.....
i forgot the computer that i want to instal my project there's no .Net framework.....

thx for your kindness