|
hello. ive copied my vb,net application from one computer to another. now i get all of these errors: Error 2 Type 'Microsoft.VisualBasic.PowerPacks.ShapeContainer' is not defined. C:\Documents and Settings\Hanzie\My Documents\Visual Studio 2008\DocReg-local\DocReg-local\FrmNieuweTekening.Designer.vb 74 34 DocReg-local I installed on my second computer powepack 3.0 But this doesn't resolve anything. Any help? thanx in advanced.
vb.net |
| Hanzie2 Thursday, November 19, 2009 6:07 PM |
Hello,
thnx for youre replies. I solved it on my second computer by installing powerpack 3.0 and deleted the powerpack 1.0 reference in my program and then referenced it to powerpack 3.0.
Now all errors are gone (thank God)
Greetings,
Hanzie vb.net- Marked As Answer byJeff ShanMSFT, ModeratorThursday, November 26, 2009 2:02 AM
-
|
| Hanzie2 Wednesday, November 25, 2009 5:51 PM |
Are you saying that you copied the project from one computer to another? If so, do you see a reference to PowerPacks 3.0 in the project?
Or are you saying you copied the application iteslf from one computer to another? If so, I wouldn't expect it to work - you would need to use ClickOnce or a Setup to deploy the app.
Steve Hoag
Microsoft
aka the V-Bee |
| shoagMSFT Monday, November 23, 2009 9:53 PM |
If is an assembly reference please make sure the Power Pack 3.0 assembly exists in C:\Windows\Assembly\ folder. Otherwise place the power pack 3.0 dll in your application debug directory and make sure there is a reference to it. Thanks Charlie |
| Charlieit123 Tuesday, November 24, 2009 4:09 AM |
This error could also be caused by having multiple versions of the PowerPacks control. Check the Add Reference dialog to see if there is more than one entry for Microsoft.VisualBasic.PowerPacks and make sure only one is checked. Steve Hoag
Microsoft
aka the V-Bee |
| shoagMSFT Tuesday, November 24, 2009 8:54 PM |
Hello,
thnx for youre replies. I solved it on my second computer by installing powerpack 3.0 and deleted the powerpack 1.0 reference in my program and then referenced it to powerpack 3.0.
Now all errors are gone (thank God)
Greetings,
Hanzie vb.net- Marked As Answer byJeff ShanMSFT, ModeratorThursday, November 26, 2009 2:02 AM
-
|
| Hanzie2 Wednesday, November 25, 2009 5:51 PM |
Hi Hanzie2,
Thank you for sharing your experience here. It will be very beneficial for other community members having the similar questions.
Regards Jeff Shan
Please remember to mark the replies as answers if they help and unmark them if they provide no help. |
| Jeff Shan Thursday, November 26, 2009 2:02 AM |