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 API App Azure Backup Beware Blob Business Central Charts ClickOnce ClickOnce deployment CSIDE Docker DotNet Dynamics NAV Error Error Message 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 Snapshot Debugger SOAP SOAP UI SQL Stream Symbol Symbols System.StackOverflowException Telemetry Tips & Tricks Virtual Table Visual Studio Web Client Web Service Windows Server 2016 Windows Server Backup Windows Task Scheduler XML XMLPort-
Recent Posts
- When does xrec work? 2023-05-13
- Tag: 0000G92 – Sales Header must not be temporary 2023-04-19
- Business Central: Multiversion Branch With Preprocessor Directives 2023-04-07
- Business Central Error Message: Unable to read data from the transport connection 2023-02-02
- Business Central: Cannot determine the frame size or a corrupted frame was received. 2023-02-02
Archive
Blogs
- The BC Docs Librarian
- Stefan Maroń
- James Pearson
- Roberto Stefanetti 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
- Marije Brummel Blog | Business Central, Azure and more...
- Vjeko.com
- Goprowe AB
- ArcherPoint
- The NAV Viking´s Blog
- Comments for
- Nav Can Be Fun
-
NAVfreak 