c# - Can you programmatically interact with Component-Based Servicing (TrustedInstaller)? -
I am trying to learn how to programmatically interact with program-based servicing (CBS) Originally Trusted Installer and Other Services For the packages which have been set up, with the aim of being able to interrogate CBS for them, and any other information they can get on the installed packages. Here's one.
Basically using C / C ++ / C # (not pick) I would like to interact with this through an API. This link is related to the API that I could get and it is not too much, but here's another one which gives some details but nothing really about the API I can use to communicate with it. This is under a package manager, in order to set up a CBS based package, you can negotiate through the command line. The best quote from that final link is:
"Different APIs ( those which are not publicly available ) to serve CSB operating system components are available for their client installation . "
All this can say, but I am not ready to give up at home either at least most of these % WINDIR% \ servicing
In which for start is CbsApi.dll
, while it seems that it is registered as a COM DLL to do nothing to expose publicly any sections or functions. It looks like the API is used in such sub-folders such as Packages
, session
, culture O
, are version
, etc.
I do not know that many people will try to do so by leaving themselves and those who were basically asking the same question two years ago and it does not look like "public no" API like they The walnut also broke.
So now I am at this point to contact for help and ask the community whether anyone has done the job of the hidden API for this, or to face the challenge and see that they can know. Any information that helps me move one step forward is appreciated.
The correct way to access CBS by programming is to have your customers from the API who try to fulfill Based on its basis, it will be included in it or both, which contain documents in Windows SDK, CBS installation is an implementation description and should not be used directly. Less information is available from publishers for triangular reasons, a combination of the fact that reliance on the details of implementation rather than contracts is a bad practice and whatever you want to do with CBS is easy and easy.
Comments
Post a Comment