Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 266 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Adapting Dotnet usage - Moving into Cloud development
Ferro
Member Posts: 6
Hello all,
As you know, in AL development, when you change your target:"OnPrem" to "Cloud" to follow the Universal Code Initiative, your dotnet variables and some functions blow up. I lost count of all the modifications that I had to do to XML/HTTP/web request-related variables and file management, so I thought it would be a good idea to create a thread where we can all share our findings and help each other.
This could serve as a guideline for future developers because this topic is not easily found online.
I'll start with an easy one:
Some examples using the XmlDocument datatype to replace the Dotnet XmlDocument:
As you know, in AL development, when you change your target:"OnPrem" to "Cloud" to follow the Universal Code Initiative, your dotnet variables and some functions blow up. I lost count of all the modifications that I had to do to XML/HTTP/web request-related variables and file management, so I thought it would be a good idea to create a thread where we can all share our findings and help each other.
This could serve as a guideline for future developers because this topic is not easily found online.
I'll start with an easy one:
Some examples using the XmlDocument datatype to replace the Dotnet XmlDocument:
variable declaration -> XMLDocVariable: DotNet XmlDocument; -> XMLDocVariable: XmlDocument; XMLDocVariable:= XMLDocVariable.XmlDocument(); ->XMLDocVariable:= XmlDocument.Create(); XMLDocVariable.AppendChild(......... -> XMLDocVariable.Add(......... XMLDocVariable.Save(BodyOutStream); ->XMLDocVariable.WriteTo(BodyOutStream); XMLDocVariable.Load(RespInStream); ->XmlDocument.ReadFrom(RespInStream, ResultXmlDoc);
0
Comments
local procedure AddBasicAuthorizationHeader(Uri: Text; Username: Text; Password: Text; var HttpRequest: HttpRequestMessage); var DotNet_CredentialCache: DotNet CredentialCache; DotNet_NetworkCredential: DotNet NetworkCredential; DotNet_Uri: DotNet Uri; begin if (Username = '') then exit; DotNet_Uri := DotNet_Uri.Uri(Uri); -> HttpRequest.SetRequestUri(Uri); ?? DotNet_NetworkCredential := DotNet_NetworkCredential.NetworkCredential(Username, Password); DotNet_CredentialCache := DotNet_CredentialCache.CredentialCache(); DotNet_CredentialCache.Add(DotNet_Uri, 'Basic', DotNet_NetworkCredential); HttpRequest.Credentials := DotNet_CredentialCache; end;Any thoughts?