Rick,

After my recent paid support session I found myself wondering about a comment you made about what version I was on. I am not sure I am clear as to the frequency or 'pairing' that your dll's are getting updated. For example, if I have updated class prg's in the past year, but have not updated wc.dll or wwipstuff.dll in many years, is that an obvious problem?

When updating wc.dll do you ALWAYS have to update wwipstatuff.dll and dotnetbridge and the other dll's?

I today had the "cannot load 32-bit DLL wwipstuff.dll" issue when running in COM and the solution was to restore an older version, not a newer version.

You should always update wwIpStuff.dll with any version updates of the various PRGs. Yes wwIPstuff.dll changes. I try not to do that often, but it's happened on a few occasions. And not updating will break code. wwipstuff.dll is treated like an internal component, meaning it's not intended to be called externally so there should be no direct dependencies on it by anyone's code.

All the products are meant to be updated as a set. If you have mismatched versions of stuff it may or may not work. There's no way to tell. It's not just wwIPStuff.dll but also other lower level helpers in wwUtils and wwApi that can change occasionally and if those get out of sync you'll run into problems.

I know you've customized some of my libraries - but that's a grave you've dug for yourself 😃 Any changes made to the library should be made through copying code into new classes or functions and never updating existing framework code. Anything else you do at your own risk of incompatibility.

+++ Rick ---

Thanks Rick. I asked the question just to confirm what felt obvious. In the very near future we will be using ALL of your latest prg's and dll's and of course subclass any actual mods to class prg's. I will be booking a few more sessions to help us through that process so that you can see what we do and help identify the gotcha's.

I highly recommend to other developers to book one on one sessions with Rick who may have legacy versions of the framework in production and having anxiety with respect to a proper upgrade.

FWIW, the changes we made mostly have to do with our own UI templating system that we built before WWWC had specific tools for similar solutions. We DO have a prg that subclasses many of the WWWC functions, and quite frankly that is what causes trouble most often. It would have been best to post requests and let you add the functionality we thought we needed to add ourselves. Often, it will 'feel' easier to just code it yourself then RTFM.

I am sure some can relate.

You live and learn!