It's always painful to write (and read) the full name "Dynamics Ax .Net Business Connector" and because BC stands for "Business Connector" and because we do have a COM and a .Net Business Connectors, the easiest to write and less ambiguous abbreviation for the "Dynamics Ax .Net Business Connector" is BC.Net
Still wondering why I don't get much results on Google for "BC.Net" ;-)
Alternatives would be ".NetBC" or ".Net BC" - but seriously...
Aif, WebServices, BC.Net, troubleshooting and architecture (formerly http://blogs.msdn.com/floditt)
10 August 2011
Why I'm using BC.Net as abbreviation for .Net Business Connector
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2011
(21)
-
►
July
(10)
- Redefining (mapping) Dynamics Ax EventLogs
- Dynamics Ax EventIds
- AOS service does not stop and stays pending (what ...
- My first AIF project is finally flying :-)
- Windows PowerShell Cookbook
- Windows EventLogs with X++
- Authenticating a user with user-name and password ...
- Authentication of the different components in Ax 2...
- PowerShell script to restart Windows (AOS) service...
- Links about the Ax 2009 batch-framework
-
►
July
(10)
0 commentaires:
Post a Comment