Browse by Tags

Tagged Content List
  • Blog Post: Working with Images (BLOBS) between Dynamics Ax and external applications (UPDATED: 06/01/2010)

    (updated the 05/01/2010 and 06/01/2010) The idea Whenever you need to transfer data in a platform specific format (like Images), the easiest way of doing this is to create an envelope (in Xml) and put the data in an encoded format in this envelope. Here’s a schema that shows such a scenario:   The...
  • Blog Post: Memory leaks and profiling with .Net

    I wrote some moths ago an article about the GC and highlighted some particularities (unsafe and unmanaged code, disposing and finalizing, etc). When you are developing with .Net you will be sometimes faced to memory or resource leaks. Especially if you are using the BC.Net, since the BC.Net is using...
  • Blog Post: The CLR for X++ programmers

    Dynamics Ax offers since Ax4 a .Net support ( BC.Net, EP and CLR objects with X++ ). As a matter of fact .Net will have a more and more important influence on Dynamics Ax since .Net is the glue of the Microsoft product stack . Sharepoint, BizTalk, SQL Server, Analysis Services, Microsoft Project, Workflow...
  • Blog Post: using the BC.Net with Ax2009 et Ax4 on the same machine might result in a AccessViolationException

    I was working on a case where a partner was having problems with the Business Connecter for Ax2009. Calling a method on the AOS resulted under certain circumstances in a AccessViolationException: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication...
  • Blog Post: X++ in the BC.Net AppDomain and on the AOS

    As I already wrote before , the BC.Net is an Ax-client and as an Ax-client able to execute X++-code. So your X++ method are by default executed within the calling AppDomain . In order to identify the AppDomain in which the X++ is executed we write two methods (GetClientProcess and GetServerProcess...
  • Blog Post: Troubleshooting a simple BC.Net application

    Here's a simple checklist if you have problems to connect to the AOS (Dynamics Ax 4) with the BC.Net. Your code might look like this: 1: Microsoft.Dynamics.BusinessConnectorNet.Axapta ax; 2: string configuration = " C:\\Sample.axc " ; //see step 3 3: 4: ax = new Microsoft.Dynamics.BusinessConnectorNet...
  • Blog Post: The .Net Business Connector (BC.Net) and the IIS

    BC.Net client application The BC.Net is designed to be a client application in a non multithreading context. This is why the assembly is deployed in the bin-directory of the Dynamics Ax client . The following schema describes the standard scenario you might find described on msdn and many excellent...
Page 1 of 1 (7 items)