-
October 21st, 2009, 09:19 AM
#1
[RESOLVED] vbp reference
Hello,
Suppose I open a vbp file with notepad, then
Code:
Reference=*\G{BF119BF5-25E9-4807-9E24-F35B7E94449C}#c.3#0#..\Utils\utils.dll#Utils-Common
Can you please explain to me a little bit?
Code:
G------???
#c.3#0#..
Where can get the tutorial for this?
Thanks
-
October 21st, 2009, 11:40 AM
#2
Re: vbp reference
Well, let's break that apart shall we....
Code:
Reference=*\G{BF119BF5-25E9-4807-9E24-F35B7E94449C}#c.3#0#..\Utils\utils.dll#Utils-Common
Reference means that this component is referenced through the vb program
Code:
{BF119BF5-25E9-4807-9E24-F35B7E94449C}
Is that particular referenced object's Class ID. A class ID is how it is known on the system. Every object on the system ghas a class id, for example :
Code:
{00020430-0000-0000-C000-000000000046}
Is for stdole2.tlb
And this :
Code:
{20D04FE0-3AEA-1069-A2D8-08002B30309D}
Is for My Computer
Read this article for an explanation of CLSIDs :
http://www.codeguru.com/vb/gen/vb_sy...le.php/c13987/
Back to your, initial question :
Is the version of that current component
Code:
#..\Utils\utils.dll#Utils-Common
Is the path to that component, where it is / will be installed.
So, if I have :
Code:
Reference=*\G{00020430-0000-0000-C000-000000000046}#2.0#0#C:\WINNT\System32\stdole2.tlb#OLE Automation
For example, it means :
Code:
{00020430-0000-0000-C000-000000000046}
is the CLSID
Is the version
Code:
C:\WINNT\System32\stdole2.tlb#OLE Automation
Is the location.
Understand ¿
-
October 21st, 2009, 12:33 PM
#3
Re: [RESOLVED] vbp reference
Understand it mostly except two points.
1)If a dll is updated, is the old one still in the registry?
I mean if the current one is
Code:
Reference=*\G{00020430-0000-0000-C000-000000000046}#2.0#0#C:\WINNT\System32\stdole2.tlb#OLE Automation
How about this?
Code:
Reference=*\G{00020430-0000-0000-C000-000000000046}#1.0#0#C:\WINNT\System32\stdole2.tlb#OLE Automation
2)The version is hex?
-
October 22nd, 2009, 12:58 AM
#4
Re: [RESOLVED] vbp reference
Hello again
Typically, the old file / component will be replaced totally. That is the proper way to do things in any case.
In cases such as having more than one version of a product installed, for instance Office 2003, and Office 2007, or Office 2010, each component will in any case have different CLSIDs.
The second question, about the version. No, that is not HEX. At a guess, I'd say it is just a denotation on how to read the version info.
More questions ¿
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|