Re: INFO - This is a no-op custom action for component....
- From: "Abhishek R [MSFT]" <abhishekr@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 14 Jan 2008 12:37:55 -0800
This means that the MSI action for that component was neither "install" nor
"uninstall", so DIFxApp had nothing to do.
In general, MSI calls DIFxApp specifying a component and how the component's
state is changing. i.e. "absent->installed" or "installed->absent" or
something else. Depending on this information provided by MSI, DIFxApp
installs or uninstalls the component. In the case below, the component state
was changing somehow, but it was neither an install or an uninstall. So
DIFxApp did nothing (by design).
"Nick Rivers" <nrivers@xxxxxxxxx> wrote in message
news:%230cdKSrVIHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
Hello DIFx team members,
can you please explain this MSI log file entry:
MSI (s) (74!90) [08:07:54:005]: PROPERTY CHANGE: Adding
NoOp_{FF188C4F-4EC3-4357-A61F-7D57447B0534} property. Its value is 'TRUE'.
DIFXAPP: INFO - This is a no-op custom action for component
My_Driver_Package. The NoOp_{FF188C4F-4EC3-4357-A61F-7D57447B0534}
property has been set to TRUE.
Or is it more MSI related?
thanks,
-Nick
.
- References:
- DIFx: INFO - This is a no-op custom action for component....
- From: Nick Rivers
- DIFx: INFO - This is a no-op custom action for component....
- Prev by Date: Re: Driver Pre-Installation problem
- Next by Date: Ndis IM Driver
- Previous by thread: DIFx: INFO - This is a no-op custom action for component....
- Next by thread: Ndis IM Driver
- Index(es):
Relevant Pages
|
