make COM dll or exe ??
-
Dear All, I am developing an application in MFC VC++ Version 6.0 for Windows 2000. The application consists of two modules : the application itself, and the other module is Autoupdate feature. I have to integrate the autoupdate application with the application, but at same time there is no major data exchange b/w the two modules. I need to pass only two parameters to the autoupdate : The url containing the new exe , the version number and the name of exe. The autoupdate feature is used to update the application exe. The autoupdate feature itself doesnot need any further upgradations So is my questions is that whether it is advisable to make ::: a) the autoupdate feature as a COM component. OR b) the autoupdate module as a seperate EXE which should be called on click of a button from the application OR c) put whole of the code of autoupdate in the application it self. OR d) any other way...which i am not thinking of. Please send your useful suggestions stating what is the most appropriate way . Feel free to ask any further queries in this regards, Thanks Rohit Dhamija
-
Dear All, I am developing an application in MFC VC++ Version 6.0 for Windows 2000. The application consists of two modules : the application itself, and the other module is Autoupdate feature. I have to integrate the autoupdate application with the application, but at same time there is no major data exchange b/w the two modules. I need to pass only two parameters to the autoupdate : The url containing the new exe , the version number and the name of exe. The autoupdate feature is used to update the application exe. The autoupdate feature itself doesnot need any further upgradations So is my questions is that whether it is advisable to make ::: a) the autoupdate feature as a COM component. OR b) the autoupdate module as a seperate EXE which should be called on click of a button from the application OR c) put whole of the code of autoupdate in the application it self. OR d) any other way...which i am not thinking of. Please send your useful suggestions stating what is the most appropriate way . Feel free to ask any further queries in this regards, Thanks Rohit Dhamija
Why don't you opt for a normal Dll for Autoupdate.exe. Expose a function say "UpdateApp(...)" from that Dll, and it will have 2 parameters as you said. Whenever you have to update/upgrade/change the EXE/module, call that function of DLL. Please tell me whether my understanding is wrong.
-
Why don't you opt for a normal Dll for Autoupdate.exe. Expose a function say "UpdateApp(...)" from that Dll, and it will have 2 parameters as you said. Whenever you have to update/upgrade/change the EXE/module, call that function of DLL. Please tell me whether my understanding is wrong.
Yeah,That will be fine.:) Rohit