Let's begin. To integrate your. NET applications with the application solution on 1C: Enterprise version of this can be one of the following ways: – through the exchange of intermediate files (. Filed under: Peter Asaro. txt,. csv,. xml,. dbf); – upload data to an intermediate store – using a mechanism OLE Automation; – the use of COM-connection – Web-publishing services – the use of Web-expansion for 1C – direct access to the data (Elisy.LinqTo1CSql.81); – Enterra. NET SDK.

The list contains not only the means, nominally included in the 1C, but also standalone products, supplied by 1C (Web-expansion), and third-party developers (Enterra. NET SDK, Elisy.LinqTo1CSql.81). Let's dwell on each of these methods. Exchange via the intermediate files (. Txt,. Csv,.

Xml,. Dbf) It's pretty clear to 1C is formed by sampling the data, which is discharged into the file sharing. Formed file can be used by other software. There's also the opposite situation – third-party program generated the file specified size is loaded and processed by 1C: Enterprise. Naturally, this kind of exchange will require a special treatment (or the rules of exchange) to upload / download files. Disadvantages of this option are obvious – any configuration changes to 1C will require changes to the procedure of export / import files, in case of lazy loading file uploads data may become obsolete, more efforts are needed to protect the information. Such a method suited to the small integration problems (for example, publication of price list on website), you'll have to own techniques develop in the 1C.