|
Hi Justin,
since renaming of the C# bindings is done, the usage
described has also to be changed.
I'll try to explain you :
the project no more expose the namespace
"libvirtBindings", in place the new namespace is "Libvirt".
The Libvirt namespace expose all types needed (struct,
enum...)
Now there is more classes to expose API methods
:
- virConnect... methods (virConnectOpen,
virConnectNumOfDomains,etc) are in the "Connect" class. For example,
"virConnectOpenAuth" is "Connect.OpenAuth" method in bindings,
"virConnectNumOfDomains" is "Connect.NumOfDomains"
In the same manner :
virDomain... methods are in the "Domain"
class
virEvent... in the "Event" class
virInterface... in the "Interface" class
virNetwork... in the "Network" class
virNode... in the "Node" class
virSecret... in the "Secret" class (even if nothing is
binded in it :S but it will be)
virStoragePool... in the "StoragePool"
class
virStorageVolume... in the "StorageVolume"
class
virStream... in the "Stream" class
There is some exceptions in fact :
- there is a class "Library" which expose
"virGetVersion" and "virInitialize" methods
- the class "Errors" which expose error related
methods (for example "virSetErrorFunc" or "virConnResetLastError")
Best regards,
Arnaud
|
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list