Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsVB SyntaxEnterprise DevelopmentDatabase AccessControlsCOMWin APICrystal ReportDeploymentGeneralGeneral 2
Related Topics
VB.NET / ASP.NETMS SQL ServerMS AccessOther Database ProductsMore Topics ...

VB Forum / COM / November 2005



Tip: Looking for answers? Try searching our database.

In Binary Compatibility

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
neerajb@noida.nospamhcltech.com - 21 Nov 2005 12:03 GMT
Hi

I am changing one function signature i.e adding one more parameter in VB6
Binary compatibility component.Now on compiling i am getting a dialog box
giving the options for No compatibility and Preserve Compatibility.

What should i do?I want to maintain the Binary compatibility

Neeraj
Jan Hyde - 21 Nov 2005 13:37 GMT
"neerajb@noida.nospamhcltech.com"
<neerajbnoidanospamhcltechcom@discussions.microsoft.com>'s
wild thoughts were released on Mon, 21 Nov 2005 04:03:03
-0800 bearing the following fruit:

>Hi
>
[quoted text clipped - 3 lines]
>
>What should i do?I want to maintain the Binary compatibility

Maintain compatability then. The issue is that the exe you
compile referencing the new dll will fail if it is installed
on a PC that still has the old DLL. Avoiding this can be
difficult.

If you break compatability then existing exes referencing
the old dll can still run (side be side if need be) with
exes referencing the new dll. This is probably the prefered
method.

Jan Hyde (VB MVP)

Signature

Foresight: Sage's Saga (J. A. Mc)

[Abolish the TV Licence - http://www.tvlicensing.biz/]

Wendell Buckner - 22 Nov 2005 16:09 GMT
If you have other executables that are dependent on this DLL then I would
not "break" the DLL... I would create a new method with the desired
additional parameters that I needed... If you only have one client for the
DLL then I don't see any problem with "breaking" the DLL... I personally
don't "break" DLL's anymore because I have so many different clients
dependent on the DLL's that I create that it's more important for me to
maintain backward compatibility...

In my development phase I set a DLL to either no compatibility or project
compatibility until a DLL is released then it always set to binary
compatibility...

> "neerajb@noida.nospamhcltech.com"
> <neerajbnoidanospamhcltechcom@discussions.microsoft.com>'s
[quoted text clipped - 20 lines]
>
> Jan Hyde (VB MVP)
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.