We are using a couple of DLLS and OCXS in our application, and I have tried unsuccessfully to use them with the XBundler plugin I bought - whats the best way for us to move forward and maybe run some tests to see if we can get this functionality working?

There are some known issues with specific DLLs that can be fixed following the next steps:

1) If your DLL links with MSVCR80.dll, you could make a static linking with MSVCR80.dll using the linking switch /MT (More information can be found at: http://msdn2.microsoft.com/en-us/library/abx4dbyh(VS.80).aspx)  After that, compile again and it should work correctly with XBundler

2) If your DLL links with MFC4x.dll, please, go to the "Advanced Options" panel and set the option "Active Context". Also, download and Unzip the file http://www.oreans.com/XBundler.zip in the same folder as your application to protect. After that, protect again and see if it works. Notice that the file XBundler.ini is only required in protection time (not required for your protected application)

If the problem persists or your DLL does not meet any of the above conditions, it will be great if you send us your application and the DLLs that you plan to bundle which cause the problem, so we can reproduce the problem here. If you cannot send the unprotected application, it will be great also if you send us any test application that we can use to reproduce your problem.

About OCXs, please, keep in mind that bundled OCXs cannot be registered (as they are not visible for external applications like regsvr32).