I am writing an application that fetches data from MS AX Dynamics once-in-a-very-long-while
The issue with AX (or with the company I am working for) is that AX does not allow cross domains connections.
Currently, we have 2 domains country1.company.com and country2.company.com on our Active Directory (AD) and the application is intended to run on both domains but AX is on country1.company.com. In fact, all country2 users RDP to country1 when they need to work on AX and it is terribly slow given our geographic distances.
To overcome this problem, I am thinking of writing a separate (console) program that runs at country1 such that users can send the data to it and let it query AX and return the results over the network.
The big question is:
Do I have to write the application like a client server thing or can i ride on existing windows features to acheive the same thing? Since I have zero network programming experience, I hope I dont have to go that way…. thanks in advance for any suggestions.
Instead of writing a console app and sockets, you should make use of WCF classes. Yes, it is networking, but anything that talks to any other computer is. You probably want to set up a WCF web service for this kind of feature. Here’s a nice starter app as an example.