Printable View
how many projects have you got open in VB? 1? The main MSN client I bet.
Have you compiled the other 3-4 or so projects that the client uses? I bet not.
If yes, then have you added a new referenc eto the compiled dll, and REMOVED the old project reference.
Woka
Quote:
Originally Posted by Wokawidget
You are absolutely correct! Ive never dealt with multi layered apps, never even seen one until now.
Ive fixed all the other issues except that one, i referenced all the others by putting in the project its using, but this one doesnt have one, so im kinda lost, is there a post # in here, or a thread you know of i could look at that could explain more on this so i can learn more about this, and get the MSN app working?
i started with a new instance of VB6, and loaded the MSN Messenger Client.vpg file, but received error upon error, all the same thing, its all references.. As ive said, i fixed all of them except the ones that reference something outside of a class or layered project already within the group.Quote:
Originally Posted by Wokawidget
can u post a screen shot of the error msg...and a screen shot of the references in the project when the error occurs.
Cheers,
Woka
I have some question regarding the XP button...
I don't know what is the reason:
After I make the project group, I getting some error msg like "version 15.0 of ... \vbXPButton.ocx is not registered. The control will be upgraded to version 17.0".
Althought I clicked OK, it still show me the same error msg next time when I open the project group
Beside this, I'm using vbXPButton.ocx at another project, when I press F5 to run the project, I goes to IE with address "C:\Program Files\Microsoft Visual Studio\VB9\XPButton.html"... I have no idea on how to solve this...
Any help please?
Thanks
VB9?
VB6 = VS 6
VB7 = VS 2001
VB8 = VS 2003
VB9 = VS 2005
I think :s
From that I am assuming that you are using a control built in VB6 in VS 2005?
I am afraid I have never tested this, and I have no idea at all why F5 is redirecting you to vbXPButton.html...that's nothing to do with the code I wrote. Are you trying to use this in a web project at all????
Woka
I'm using it in VB6.Quote:
Originally Posted by Wokawidget
umm... is it I just use the vbXPButton.ocx, then add it in under Project -> References?
or I need to create a vbg?
Check to make sure that your app is set as the startup... and not the control's project...
-tg
Open up vbXPButton.vbp in VB6. Click build/compile.
Then open your blank project and go to Components and browse to the newly compiled OCX.
Regarding having a previous app using it and getting it to use the newly compiled version, without needing to recompile your app, you need to set binay compatibility on the build options for vbXPButton.vbp and point it at the old OCX. This keeps means the registered OCS keeps the same GUID.
Woka
OK, let's said I compiled the ocx, then I put it inside "C:\Testing" folder, this folder will have my vb project files as well.Quote:
Originally Posted by Wokawidget
Then I go to Components and browse to the OCX. Click apply & ok button.
But when I move the whole folder "C:\Testing" to "D:\Testing", then I open the vb project again, the refering ocx file location changed :confused:
sorry... can explain to me what are the differences between binay compatibility & project compatibility? :blush:
Errrr....well the OCX gets registered in the registry with C:\Testing\vbXPButton.ocx
Open up regedit and do a search for this.
So when you move your folder and then run the exe it's going to check the registry and then look for the folder c:\Testing...which you have removed.
Copying the folder is essentially as doing an app deployment manually...so you would also need to call RegSvr32 to register the OCX. Open a CMD prompt and type:
RegSvr32 "D:\testing\vbXPButton.ocx"
But this is a VERY bad idea. If you indend to move things around, or put them on a different machine then you really should use an installer for this as that's what they are designed for...copying the files, and then registering the ocx's and dlls.
VB6 ships with the Package and Deployment wizard for this.
Woka
Just because a DLL or OCS has the same name, woof.dll, doesn't means it's the same thing, and each time you build it a new GUID is assigned to it for the registry.
If you compile the OCX into a folder ..\BinCompat\vbXPButton.ocx and use this as the "base" ocx, and then set this OCX for binary compatibility, and then compile the OCX to a diff folder ..\ReleaseOCX\ then this one will be used by your PC, but when compiling it looks at ..\BinCompat\vbXPButton.ocx and uses the same GUID...so you can keep compiling the OCX and your EXE file will still run as the GUID stays the same in the registry.
Woka
Here's some links on the compatibility subject:
http://support.microsoft.com/kb/161137
http://www.visibleprogress.com/vb_bi...patibility.htm
Hope this helps.
WOka
In my sig there's a short walkthrough on setting & using the compatibility, along with a brief description on why it works the way itdoes.
-tg
Hey Woka, the menu for your vbSysTray does not support sub-menus? :(
That's right. I don't think I added that functionality in.
Woka
Will you have time to add such functionality then? :)Quote:
Originally Posted by Wokawidget
Hi,
Sorry, I have no intention of modifying any of my VB6 code in the near future I am afraid. Very busy.
I have supplied the source so I don't have to do things like this, which gives other developers free reign to add functionality of their choice. Why don't you code the functionality?
Woka
Newb
im trying to copy it to my project,but i need to add something... like a reference?
how do i copy the buttons? what do i need to do?
That makes no sense :)
Can you explain in more detail.
Cheers,
Woof
i want to use the winXP buttons on your Zip file..
how do i do it?