If you are having the need to use DotNet in an older client such as Dynamics NAV 2009 R2 you will problably run into troubles which they have fixed for later versions of Dynamics NAV. I had the problem that I tried to downgrade code using the DotNet type System.String. I didn’t get very far until the compiler started to complain…
Tags
.net 1VM/2VM App Azure Backup Blob Business Central Charts ClickOnce ClickOnce deployment CSIDE Docker DotNet Dynamics NAV Error Exception Extension IIS Language Module Mail Microsoft Dynamics NAV Microsoft Dynamics NAV 2009 R2 Microsoft Dynamics NAV 2017 NAV NavContainerHelper Navision NST OnPrem Performance Port Sharing Powershell Profiles RDLC Repo Report Builder Reports Role Center SOAP SOAP UI SQL Stream Symbol Symbols System.StackOverflowException Tips & Tricks Virtual Table Visual Studio Web Client Web Service Windows Server 2016 Windows Server Backup Windows Task Scheduler XML XMLPort-
Recent Posts
- How-To Compile a Business Central App/Extenssion Manually 2019-03-03
- A package with publisher ‘Microsoft’, name ‘Application’, and a version compatible with ‘13.0.0.0’ could not be loaded. 2019-03-03
- Business Central, CSIDE objects not included in symbols 2019-03-03
- Error accessing Website Microsoft Dynamics NAV 2017 Web Client – Domain Control Validated chain building failed. The certificate that was used has a trust chain that cannot be verified 2017-03-13
- Dynamics NAV: How To Consume An External SOAP Web Service With .Net/Dotnet Interop 2017-02-25
Archive
Blogs
- James Pearson
- Roberto Stefanetti NAV Blog
- JoeBrown
- Comments for DevOps ABCs Blog
- DevOps ABCs Blog
- Dynamics 365 Business Central for Partners
- Freddys blog
- Stefano Demiliani Technical Blog
- David Worthington's NAV Performance Blog
- Freddys Blog
- Totovic Dynamics 365 Blog
- Vjeko.com
- Goprowe AB
- ArcherPoint
- The NAV Viking´s Blog
- Comments for
- Nav Can Be Fun
- Navision-Girl.Com
- LET'S TALK NAV
- Kine's Info
NAVfreak 