is there any standard to describe the xml format which is created by CreateKnxProd about createknxprod HOT 12 CLOSED

Bad news: The used dlls don't exist in current ETS5 any more. And the dlls in the CV directory don't support version 20 of the scheme. :(

from createknxprod.

The xml is the same as the files in a knxprod-file. I just put everthing in one file. You can get the xsd of the xml from ETS dll Knx.Ets.Xml.ObjectModel.dll:

using (var fileStream = new FileStream("knx.xsd", FileMode.Create))
using (var stream = DocumentSet.GetXmlSchemaDocumentAsStream(KnxXmlSchemaVersion.Version14))
{
while (true)
{
var buffer = new byte[4096];
var count = stream.Read(buffer, 0, 4096);
if (count == 0)
break;

    fileStream.Write(buffer, 0, count);
}

}

from createknxprod.

@thelsing
Would it also be possible to use a more recent schema version with is used in latest ETS5.x?
Only the latest schema contains the required stuff for KNX data secure for example.

from createknxprod.

Sure. You only need to regenerate the xml class from xsd. I used xsd.exe + search and replace. I want to use the generator forked in my github account for this.

from createknxprod.

This one:
https://github.com/mganss/XmlSchemaClassGenerator

from createknxprod.

@thelsing
Could you elaborate a bit more what is needed to get a recent XML schema from ETS5.7 like this
<xs:schema xmlns:knx="http://knx.org/xml/project/20" and use it with this tool?

Do I just have to copy the two DLLs Knx.Ets.Xml.ObjectModel.dll and Knx.Ets.Xml.ObjectModel.XmlSerializers.dll from the ETS5.7 dir to the ETS4 folder which contains the converter engine DLL and overwrite the existing DLLs which have the same name?

The two DLLs in the ETS5.7 dir contain schema20. The DLLs in the ETS4 dir (converter) contain only schema11.

from createknxprod.

I would switch to the dlls from ETS 5.7.

Maybe the signing process needs to be changed a bit, but I can do this when we can create a xml in the new schema.

So the steps are:

1. get a xsd from ets 5.7 dlls.
2. create a new Xml.Project.cs with the xmlSchemaClassGenerator (It seems I already did this for schema version 17.)f
3. change references to dlls from ETS5

Now you should be able so create and save the new xml format.
If we are lucky signing still works with the ETS5 dlls. If not we will have to experiment a bit.

from createknxprod.

We really need to update to the latest schema 20. This is also required for data secure stuff.
@thelsing Could you do that again?

from createknxprod.

I'll try. The problem is that the ETS4 dlls probably don't support this schema. So I need to use the dlls from ETS5. Let's hope that the methods are still the same for ETS5.

from createknxprod.

Steps for generation of code from xsd:
XmlSchemaClassGenerator.Console.exe -e -0 knx.xsd
s/Xml.Project/CreateKnxProd.Model/ on Xml.Project.cs
Change type of ReplacesVersion to string

from createknxprod.

So sad.
So the only option to get new ETS features working in the future somehow, is to „reuse“ existing signed product databases and try to emulate an existing product.

from createknxprod.

This is fixed in dev-branch.

from createknxprod.