Vous êtes ici: Home | QBS Blog
QBS Blog

Part 1 - Microsoft Dynamics Development Preview

Microsoft released during Christmas an Azure Virtual Machine where you can play around with the new Development Environment. In the coming months I will blog about the new NAV development environment.

In this first post you will find information about Azure subscription and how you can create your first app.

Have fun and stay tuned!

If you want to keep up with the latest from Microsoft you need to have an Azure subscription. 
Information can be found on: 
You can start with a free subscription.

Microsoft -Dynamics -Development -Preview -Add -Subscription -640x 213

So welcome in the Azure World!

The developer preview will be updated on a regular basis. Be aware that it is a preview so things you make can be broken in a next version. Follow the NAV team blog to see if a new version is available: https://blogs.msdn.microsoft.com/nav/category/announcements.

Microsoft -Dynamics -Development -Preview -640x 130 (1)

If you run into any issues, please log them on GitHub project: https://blogs.msdn.microsoft.com/nav/category/announcements/

So it is time to get started!

The new Azure Virtual Machine (VM) can be created via http://aka.ms/navdeveloperpreview and provide the parameters to create it.

Microsoft -Dynamics -Development -Preview -Custom -Deployment -640x 499 (1)

The deployment will start and will take some time to finish

 Microsoft -Dynamics -Development -Preview -Dashboard

In the end, you will see the VM with additional information.

Microsoft -Dynamics -Development -Preview -Dashboard -2-640x 231

When you click on Server1, the VM information will be displayed

Microsoft -Dynamics -Development -Preview -Essentials -640x 251

Make sure you stop the VM in case you don’t require this.Once stopped (and thus dislocated) the hours won’t be invoiced by Microsoft.

Start a remote desktop application and connect to the virtual machine by using the DNS name label. When you stop / start your VM a new IP address will be provided, so connecting via the public IP address will work only once.

So it is time to get started !

Start the new Development Environment called Visual Studio Code

If you compare the old (left) against the new (right) one, there are not that many changes :-)

Microsoft -Dynamics -Development -Preview -compare -640x 276 

There is no Object Designer anymore, so you can start directly with coding. NB: Don’t type too fast as most of the information you want to see can be inputted via IntelliSense.

First you need to select a folder to store your files.

Microsoft -Dynamics -Development -Preview -Folder -640x 209

So start coding !

Create a file with the extension .al. This is a pre-requisite for NAV IntelliSense to work !

It is straight forward to create a new file newtables.al and to create your first table

Microsoft -Dynamics -Development -Preview -first -table -640x 637

Compiling [F5] results in an error message, when you check the created app.json you are can see what issues may occur.

 Microsoft -Dynamics -Development -Preview -Compiling -640x 452

The installed NAV version is US, so the locale should be US.

As this is an addition to the standard NAV application, the standard navx files should be in C:\TEMP.

 Microsoft -Dynamics -Development -Preview -TEMP-640x 127

When everything goes as it should press [F5] to publish your app.

Microsoft -Dynamics -Development -Preview -Publish -640x 94

Jan Boes QBS Group
Jan Boes
Senior Developer at QBS group

Read also:

Blog: Part 2 - Preview on the Microsoft Development Environment