The main features of this release focus on Chilkat’s Ai class, enabling interactive AI response streaming directly into embedded desktop application browsers. It supports Azure, custom base URLs for OpenAI-compatible providers, and local providers like Ollama. ✨ New Features Ai Real-Time Streaming AI Responses to Embedded Browsers in Desktop Apps — Stream AI responses […]
Previous Version: Chilkat v11.1.0 Release Notes The main addition in v11.2.0 is the Chilkat.Ai class, and the Chilkat.StringBuilder.MarkdownToHtml method. Ai: The Chilkat AI class provides a unified API for interacting with different AI providers: OpenAI, Google, Claude, xAI, Perplexity, and DeepSeek. It provides functionality for conversation management, multimodal inputs, and streaming mode. Markdown to HTML […]
Starting with the v10.0.0 release (end of September 2024), Chilkat moves to standard semantic versioning. Prior to this release, for various technical reasons, Chilkat was stuck with versions 9.5.0.xx, where only xx changed. For this first leap to semantic versioning, where the major version changes to 10 (from 9), there are no backward incompatible changes. […]
A Chilkat user graciously reported an error in the example at http://www.example-code.com/phpExt/xades_facturae_3_2_es.asp “I use it to sign TicketBAI XML files and FacturaE in Spain. I noticed that the FacturaE signatures weren’t validating properly on some government websites with an error something like “the signature is not a correct xades signature”. The namespace “etsi” was replaced […]
In Chilkat v9.5.0.90, the Id attribute is automatically generated and added to the “Signature” tag when an XML digital signature is created. This results in a Signature that begins like this: <Signature xmlns=”http://www.w3.org/2000/09/xmldsig#” Id=”signature-1502-9002-7096-7873″> Why did Chilkat do this? It is because if you or somebody else wishes to subsequently add an Encapsulated Timestamp to […]
(Chilkat is going to begin posting about the ongoing work with customers involving smart cards and tokens used for signing PDFs and XML invoices, etc.) Chilkat is helping a customer with XML Signatures for Guatemala Fel Factura Electronica, which is to sign XML that begins like the following: <?xml version=”1.0″ encoding=”utf-8″?> <dte:GTDocumento xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” Version=”0.1″ […]
Question: I am user of your component and I have problem with signing XML files. I got (invalid) ds:Signature with same not replaced text “TO BE GENERATED BY CHILKAT” in tree node (SigningCertificate|xades:Cert[1] and SigningCertificate|xades:Cert[2]) The SigningCertificate|xades:Cert[0] is valid. … CkXml object1; object1.put_Tag(“xades:QualifyingProperties”); object1.AddAttribute(“xmlns:xades”,”http://uri.etsi.org/01903/v1.3.2#”); object1.AddAttribute(“xmlns:xades141″,”http://uri.etsi.org/01903/v1.4.1#”); object1.AddAttribute(“Target”,”#xmldsig-0d264d45-0a6a-4431-8e74-35463a71756c”); object1.UpdateAttrAt(“xades:SignedProperties”,true,”Id”,”xmldsig-0d264d45-0a6a-4431-8e74-35463a71756c-signedprops”); object1.UpdateChildContent(“xades:SignedProperties|xades:SignedSignatureProperties|xades:SigningTime”,”TO BE GENERATED BY CHILKAT”); object1.UpdateAttrAt(“xades:SignedProperties|xades:SignedSignatureProperties|xades:SigningCertificate|xades:Cert|xades:CertDigest|ds:DigestMethod”,true,”Algorithm”,”http://www.w3.org/2000/09/xmldsig#sha1″); object1.UpdateChildContent(“xades:SignedProperties|xades:SignedSignatureProperties|xades:SigningCertificate|xades:Cert|xades:CertDigest|ds:DigestValue”,”TO BE […]
Question: The examples refer to a type certificate or “.pfx”. My certificate is a “.pem” or “.cer” file. Can I generate an XAdES-BES enveloped digital signature to insert in my xml file? Which method should I use to load the certificate into memory and apply the password? Answer: A private key is needed to create […]
Chilkat has found what it believes to be a bug in the internal XML canonicalization functionality in some other software systems. Chilkat’s XML canonicalization is correct, whereas some other established implementations are incorrect. Chilkat is adding a Behavior in v9.5.0.79 to allow for the bug to be reproduced so that XML signatures produced by Chilkat […]
Chilkat’s Online XML Signature Validator: http://tools.chilkat.io/xmlDsigVerify.cshtml gob.es FacturaE online validator: http://sedeaplicaciones2.minetur.gob.es/FacturaE/ ETSI Signature Conformance Checker (requires credentials) http://signatures-conformance-checker.etsi.org Validate UBL: https://www.moj-eracun.hr/exchange/validateubl UBL 2.1 e-Invoice Validation: https://joinup.ec.europa.eu/solution/ubl-21-e-invoice-validation-service/about FatturaPA (fatturapa.gov.it) http://sdi.fatturapa.gov.it/SdI2FatturaPAWeb/AccediAlServizioAction.do?pagina=controlla_fattura ADSS Signing Server: https://account.ascertia.com/demos/xmlsignatureverificationstep1 apis.gometa.org hacienda (Costa Rica) XML Validator: https://apis.gometa.org/validar/ RTR Signatur-Prüfung https://www.signatur.rtr.at/de/vd/Pruefung.html ICP-Brasil https://verificador.iti.gov.br/verifier-2.6.2/ Weryfikacja Podpisu Elektronicznego https://weryfikacjapodpisu.pl/index.html XmlValidation.com: https://www.xmlvalidation.com/ I don’t trust this validator. Change the signed XML document […]
Chilkat has resolved problems relating to the creation of XAdES-BES XML signatures for documents sent to www.csioz.gov.pl. These fixes will be available starting in Chilkat v9.5.0.76. At the time of this post (31-Oct-2018) 9.5.0.76 is not yet released. Contact support@chilkatsoft.com for a pre-release if desired. Chilkat has worked with a customer to successfully sign […]
Chilkat v9.5.0.75 will include features to make it easy to generate XAdES-BES and XAdES-EPES signatures for electronic invoicing and tax reporting for many countries. The goal is to provide an easy and inexpensive solution for these complicated requirements. Chilkat has been working with customers in Spain, Italy, Hungary, India, Brazil, Costa Rica, and elsewhere to […]
