Have to Break Compatibility every time???
I just compiled a DLL project in VB6, set the project to binary compat. (to the dll I just compiled) and closed the project.
What am I missing here? This is the message I get:
I did not add any enum values.
Is DCAgentLib.ClientStateEnum public?
I was about to cry like a little girl, so I brought a fresh mind in to look at it.
It's happened to all of us!
Congratulations, you just gained experience. Your aptitude has not changed. [grin]
2 Days ago I moved a class location in the hierarchy but was interupted before I deleted the previous reference.
I once spent about 8 hour debugging a paradox database.
The real Entrepreneur
At least it sounds like you understand compatibility. I worked on an application once that contained on the order of 25-40 DLLs and ActiveXEXEs. And they (existing project team) *weren't* using binary compatibility. I tried and tried to explain that it needn't take 2 days to build a VB project. And that using compatibility would be painful one time (getting the source code control straightened out), as opposed to painful every single day.
If using VB6 - Set Project properties to Project Compatibility in the Component tab of the Properties dialog box.
Fog Creek Home