Development of the GUS Standard Interface Development of your own driver complying to the GUS Standard Interface can be sped up by using the GUSInterface.dll assembly in your .Net-capable project (C#, managed C++, VB.Net or other). GUSInterface.dll contains the definition of two (2) interfaces IGus and IGusGetSetParameter. The IGus defines the methods that are specified in the GUS version 1 standard. IGusGetSetParameter contains the methods GUS_GetParameter and GUS_SetParameter defined in the GUS version 2 standard. So in order to be sure you project is exposing the correct interface implementation, define your implementation classes subclass of IGus and if you want to implement version 2 of the standard, also of the interface IGusGetSetParameter. Both interfaces are defined in the namespace QED.GUS. The GUSInterface.dll assembly has to be referenced in your project. Please consult the documentation of your development environment how to do this. Besides these interface, GUSInterface.dll contains an abstract class GusAbstractImplementation implementing these interfaces in abstract methods. Using this class can replace using the interfaces described above. You can also subclass this abstract class and implement the abstract methods. In combination with the test program you can test your interface as the development progresses. The XML format The XML scheme GusDeviceInfo.xsd defines the XML format how to report the available parameters in the device. It defines which kind of parameter can be transmitted with all its properties, its limitations and /or restrictions. When this file GusDeviceInfo.xsd is read by the tool xsd.exe (with option /c)it generates source code that can be included in your project. It automatically generates all classes to read and write the XML format, transmitted between the supervisory program and the device. Further info is available on: https://docs.microsoft.com/en-us/dotnet/standard/serialization/xml-schema-definition-tool-xsd-exe In order to write or read an XML string, use the XMLSerializer and De-Serializer respectively as described on the Microsoft page: https://msdn.microsoft.com/en-us/library/system.xml.serialization.xmlserializer(v=vs.110).aspx