Boby Francis

• Jun 15th, 2006

 

IN Visual Basic have 3 types of Compatibilites is there.

1) No Compatibility :- New GUID created, references from other components will not work

2) Project Compatibility :-Default for a new component <Not as critical to mention this one>

3) Bianary Compatibility :-GUID does not change, references from other components will work

rameshpvb

• Feb 9th, 2007

 

General Definition : Different systems (e.g., {programs}, {file formats}, {protocols}, even {programming languages})


that can work together or exchange data are said to be compatible.



o Visual Basic?s Version Compatibility feature is a way of enhancing your components while maintaining backward compatibility with programs that were compiled using earlier versions. The Version Compatibility box, located on the Component tab of the Project Properties dialog box, contains three options:


No Compatibility:

o Each time you compile the component, new type library information is generated, including new class IDs and new interface IDs. There is no relation between versions of a component, and programs compiled to use one version cannot use subsequent versions.Project Compatibility:o Each time you compile the component the type library identifier is kept, so that your test projects can maintain their references to the component project. All class IDs from the previous version are maintained; interface IDs are changed only for classes that are no longer binary-compatible with their earlier counterparts. Note This is a change in Project Compatibility from Visual Basic 5.0, where all class IDs and interface IDs in the project changed if any one class was no longer binary-compatible.


o Important For the purpose of releasing compatible versions of a component, Project Compatibility is the same as No Compatibility.


Binary Compatibility:

o When you compile the project, if any binary-incompatible changes are detected you will be presented with a warning dialog. If you choose to accept the warning, the component will retain the type library identifier and the class IDs. Interface IDs are changed only for classes that are no longer binary-compatible. This is the same behavior as Project Compatibility.


o If, however, you choose to ignore the warning, the component will also maintain the interface IDs. This option is only available when the compiler determines that the change was in the procedure ID or signature of a method.


o Note:: When people talk about Version Compatibility, they?re usually referring to Binary Compatibility.