The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

    • RT @aboutanurse: Patiënten die beademd zijn of langer dan 48 uur op onze IC liggen worden door ons gebeld om terug te komen op de nazorgpol… 18 minutes ago
    • RT @BeiAnja: Der Sechsjährige hat jetzt ein eigenes Handtuch, das er überall mit hinnimmt. Erwarte jetzt, dass er kurzfristig von der Erd… 21 minutes ago
    • RT @NPORadio2: Vijftig jaar oud beeldmateriaal vinden van @ledzeppelin, dat is nog eens een bijzondere ontdekking als je je schuur opruimt.… 27 minutes ago
    • RT @rki_de: #COVID19: Entlassungskriterien aus der Isolierung RKI empfiehlt ab sofort 14-tägige Isolierung und Testung vor Entisolierung v… 28 minutes ago
    • Reminder: check if LUMC Privacy Statement and Gebruiksvoorwaarden are printable or downloadable as PDF. wiert.me/2021/02/26/rem… 1 hour ago
  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,276 other followers

Archive for April 20th, 2016

Detecting the use of “curl | bash” server side | Application Security

Posted by jpluimers on 2016/04/20

From the “let people know when they are stupid” department:

Another reason not to pipe from curl to bash. Detecting curl | bash serverside.

Source: Detecting the use of “curl | bash” server side | Application Security

–jeroen

Posted in Development, Python, Scripting, Software Development | 1 Comment »

Support of import in xsd.exe – Jose Luis Calvo Salanova – Site Home – MSDN Blogs

Posted by jpluimers on 2016/04/20

I tend to forget this: xsd.exe can resolve xs:include, but not xs:import. When using xs:import it will complain about missing types.

Simple solution: reference all imported XSDs (but not included XSDs) on the same command-line:

I was trying to create a C# class with xsd.exe from an schema that imports others schemas like that xsd.exe /c schema.xsd and it fails miserably reporting an error like “The datatype ‘xxx’ is missing.”. Basically xsd.exe doesn’t resolve the schemaLocation attribute.

Dare Obasanjo’s article addresses the problem, and Scott Hanselman had the same problem -and solved it-.

The solution isn’t very nice, but at least it’s simple. You have to tell xsd.exe all the schema referenced, xsd.exe /c schema.xsd importedSchema1.xsd importedSchema2.xsd

Be aware that the C# filename is sometimes generated from all XSD filenames on the command-line (I’ve noticed this when the import is specified before the actual XSD file, if the import is at the end, the name of the import is used.

If my memory serves me right, older versions of XSD.exe could not resolve unix-style relative paths on the command-line, but newer versions do.

–jeroen

via: Support of import in xsd.exe – Jose Luis Calvo Salanova – Site Home – MSDN Blogs.

Posted in .NET, C#, Development, Software Development, XML/XSD, XSD | Leave a Comment »

 
%d bloggers like this: