ActiveX from standalone app

Main Goal Convert our existing standalone .exe MFC application into ActiveX control. The control is used for complex image display, networking, and processing. Project details The initial conversion work has been already done: our app compiles (Visual Studio 2005, C++) and runs as ActiveX control. You will have to finalize the initial conversion with the following phases: Phase I - Revision 1. Revise the initial ActiveX conversion, make any improvements. 2. Fix the problems that we have currently identified in the existing code: a. Our app runs multiple threads, but apparently they don’t always terminate correctly in ActiveX-converted version b. Certain problems with Windows message dispatching, likely related to 2a. 3. Make ActiveX as independent on the client system (Windows version, browser version, system libraries, etc.) as possible. Phase II ??" Web Deployment Create a package that will be embedded in the web page and will install ActiveX control on the remote client upon request. Requirements: 1. Minimize download size (most probably using .cab archive); 2. The installation on the user side should be as simple as possible. The control should install itself for all users by default. 3. The web page should be able to detect if older version of the control already installed on the client, and automatically replace it with the newer version (if available). Phase III ??" Mouse/keyboard interaction Make ActiveX respond to mouse/keyboard input from the user. Project code We will provide you with the source code for our project; we use Visual Studio 2005, C++; we do not use .NET. The main coding requirement is to insert all ActiveX-related code as #ifdef blocks, i.e.: #ifdef ACTIVEX // ActiveX code here #endif // Regular standalone .exe version code here I.e., by defining/undefining ACTIVEX, we should be able to compile our code in ActiveX/standalone version respectively. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables): a)? For web sites or? other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Windows