ActiveX Control Software Installation VC++/ASP.Net

We at [login to view URL] needs an ActiveX control to install our software onto a client’s computer. The control needs to be able to communicate with our pre-existing .Net structure on our servers (bi-directional), as well as communicate and execute the installation module(s) on the client’s system. What we need is an ActiveX control / component, written in Visual C++, as well as an ASP.net structure to install our software on the clients machine. The goal is to have the ActiveX control able to communicate with our .Net structure on our server to customize the install of the software. The actual customization of the install (specification of installation directory, options, etc) will be handled in ASP.Net; the ASP.net code would then make specific calls to the ActiveX control to execute those commands. The ActiveX control would then download and install (preferably by executing the components) the required components onto the client's machine; the status of the installation should be displayed within the ActiveX control itself, as well as querying / posting status back to the server-side code. The control must be able to accept / return specific parameters from / to the server as well as accept / return parameters to the installer components. Exact implementation can vary depending on the coder's input. ActiveX control should be coded in Visual C++. Full source code will need to be released on completion. ## Deliverables We want the ActiveX control to be as object-oriented as possible, to allow addition of component modules with little or no source modification. There are two situations that the ActiveX control will need to handle: 1) The ActiveX control will keep a collection of component objects that are passed from the source html (within the object tag is one option; open to other options). The ActiveX control will need to enumerate all the objects that are within the collection, holding to a certain order, and provide mechanisms for executing those objects in that order. 2) The ActiveX control will receive the component specified on the server, and instead of holding the file in the collection it will download and install the component immediately. Added functionality of doing the install of the component in the background while still accepting instructions from the server (or IE continues to browse) would also be a recommended feature. Here are some sample (pseudo-code) functions and parameters for the control: [login to view URL](<objectName>, <objectID>, <source>, <parameters>) -function will add the object specified into the collection -<objectName> = descriptive name of the object component -<objectID> = id value (int) of the object -<source> = location where the source object is found (url to an exe file most likely) -<parameters> = list of parameters that need to be passed to the object on execution (can be null string) -returns the success/failure of adding the component to the collection [login to view URL]() - function that will return all object names and IDs listed within the collection [login to view URL]() - function will execute all objects within the collection; for each object it will: 1) retrieve object from server based on source string 2) execute object, with the parameters specified 3) remove object from collection, and remove component downloaded from client's machine. 4) proceed to next object until component is empty. · Control will also need to show a status bar showing the progress of downloading the objects, as well as report back to the server when function is complete. · Returns success / failure of executing all component(s) [login to view URL](<objectName> or <objectID>) · Function will execute one single object in the collection; functionality will be the same as above with the exception of step 4 · Returns success / failure of executing components Additional error reporting mechanisms will be needed, if the component module object returns an error code other than "0" the control will need to report this back to the server. Any additional exceptions raised for the control itself can be passed to the parent (server). Other functions for the control can be generated as needed. An additional control to execute one specific component module will A couple example component modules will be provided when ready for testing. The coder will create the ActiveX control as well as testing code (html pages showing the functions in use). Checklist: ActiveX control, with functions (source included) ASP.Net server test pages, demonstrating functionality of ActiveX control. ## Platform Visual C++ ActiveX Windows 2000 Server ASP.Net (C# preferred, just for test pages, not a big deal)