My last blog about my VSCode extension dates from July 2018. I have been upgrading/maintaining it meanwhile, and I am definitely not going to blog about all new small features and fixes (yes, quite necessary as well ;-)) every single time, but for this one, I really felt that an update wouldn’t hurt.
Tag Archives: Language
CRS AL Language Extension – File Management
Time for the next round of functionality I added in my VSCode Extension (the CRS AL Language Extension) – a functionality that manages your filenames (and pre/suffix). Hold your horses – this is going to be a long one ;-). You don’t want to know how many hours I spent on this functionality – many points of feedback from the community, and even some pullrequests from some (for all of which I’m very thankful!) has made it into the functionality it is today.
How to prepare Dynamics NAV Extensions for multi language support
If your Dynamics NAV customers operate in a number of countries, you must ensure that the software complies with country-specific laws, regulations and common business practices to meet legal obligations for activities conducted in each country.
CRS Al Language Extension – Running Objects
This was the first major feature that I tried to add. Namely, being able to run an object without having to change and save the launch.json. The easiest way to find the functionality is in the Command Palette. Just search for “>crs:run”, and it will give you all options:
CRS Al Language Extension
I have been wanting to write this blog for a while. But I’m going to keep it a short one, as I’d like to go into a few topics separately, and I don’t want to swallow too much in one big blogpost with the possibility with some (important?) details would get lost.
Thing is – I wrote an Extension. And I’m not talking about an Extension for Business Central in VSCode. No. Well – I did write a few of those as well, but that’s not what this blog is about. I made a VSCode Extension…
How to Add my Custom Language Pack to W1 Version?
Install the new language pack on the target computer with W1. To do this, select and click each of the three .msi files listed below, one after the other. The order is not significant:
NAV2016 Data Upgrade process and language settings [update]
In the previous post I explained why automatically running Codeunit 2 Company Initialization during the data upgrade could be a problem. Main problem is the language used during the data upgrade. It can’t be set with the Start-NAVDataUpgrade cmdlet and as a result the company initialization is executed in ENU instead of the local language.