In current project consisting of about 600 binaries(dll's,exe's,ocx's etc.,) I need to identify .NetDll's which has COM component, As I can understand, in such scenario's Registration using Regasm is mandatory (if and only if the .NetDll's have COM components),
But, my query ,
1. how to identify such .net Dll's requiring registration(otherwise embedded COM components) how I need to segregate .NetDll's (Registration/Non-Registration).
Also, I used .Net Reflector tool to identify/segregate Dll's(.Net Dll's / Non-.Net Dll's(Win 32's , COM -Dll's), but I need to focus programatically /if available open source tool to throw more light on differentiating (.Net Dll with COM Component and pure .Net dll's).
2. Is the adding interfaces/methods within the above .Net Dll(COM component) same as we would implement in ATL-COM Project(DllRegisterServer - Adding Interface/methods etc., in COM-DLL). ?
3. How also, one determines, the dependency of Windows Services of the above .Net Dll from my project., for eg., Assuming Print_XYZ.dll (.Net Dll with COM component) is dependent on start/stop of windows services (services.msc).
(ie., given a .Net Dll/COM component , how one could one conclude the above mentioned .Net Dll is dependent on print spooler services(windows services).
any assistance in resolving the above queries would be appreciable.
Thanks & Regards,