Version compability issue?

[3pmilk]

My project group is consisted of one ActiveX.EXE and one Active.dll. Currently both ActiveX components have their version compability set to "Project Compability."

I have been adding, removing and editing methods in existing classes for these components and compile them to "project compability" WITHOUT any problems.

My question is: What would happen if I add new or delete classes in ActiveX.dll and compile both as "project compability?" Will it break my interface and no longer
work with the previous clients?

-- Thanks, Wendy

 

[chogben]

Yes. Once you've released your components on the world you should only ever use binary compability, this will ensure that any changes will not change the interface (known as breaking the contract). Using Project compability will only break the contract if it has to, using no compability will always break the contract every time you compile.

You described a case of a pretty serious sounding upgrade. I would suggest setting no compability and give the project a new name, once you compilied it, set the compability to binary. This will allow your existing solution to work without being overwritten by an incompatible upgrade.