the runinstaller charge wmi provider assembly
i am formulating decoupled wmi provider category library. all i have review points towards including something along lines:
[system.componentmodel.runinstaller(true)]
public category myapplicationmanagementinstaller : defaultmanagementinstaller { }
i accumulate purpose designation since windows wmi infrastructure needs wakeful structure wmi provider before used.
my doubt - "installer" ran? msdn says installer invoked "during designation an assembly", nonetheless i am certain means occur context category library containing wmi provider.
i underneath sense an involuntary deputy manually controlling installutil.exe opposing public containing wmi provider, nonetheless changes i provider recognized windows wmi infrastructure unless i manually run installutil management prompt. i possess accessory during development, nonetheless an concentration controlling provider deployed machines - then?
it seems runinstaller / defaultmanagementinstaller multiple operative morally - correct?
Comments
Post a Comment