For several years I have been talking about Source Code Management and its many benefits. Luc van Vugt has been doing similar things and lately another brother in arms Mike Glue who I have know for many years from my time at IndustryBuilt has joined.
This intro is to kick of a series of blog posts around the area of Building, signing, testing, deploying with more of your code.
We want to show off some of the many things you can make happen and automate for your development team.
We hope you enjoy and look forward to hear all your feedback.
There is an unconfirmed news story just posted on msdynamicsworld.com that Paul White is leaving Microsoft.
Lets wait and see if this story is true or not.
Ever since last year I have wanted to do something inside Visual Studio Code for Source Code Management of Standard Dynamics NAV development.
Why? (You might ask.)
Well Microsoft has introduced Visual Studio Code as the next generation editor at several conferences in 2016. Creating tools in Visual Studio Code that can help manage your Source Code for the existing version might help migrate developers to Visual Studio Code and get use to it before the next version is released.
That said I have also been looking at how to make the entry in to Source Code Management as easy as possible. Many developers are still not using any kind of SCM, something I really have wanted to change for several years, and I think the main reason is the knowledge and time to get started and get setup is just too high. Developers simply give up before they get started.
So what to do about it?
In the last months I got talking to a few developers at Elbek & Vejrup in Denmark that were looking to explore SCM and get their teams up to speed. We discussed the options and we agreed on VS Code as the way forward.
This project has been underway for a while now and we are almost ready to release version 1.
If you are interested in reading about it, contributing or following please feel free to follow the project hosted by my friends at Cloud Ready Software on GitHub
You can also install and play with what is already there by installing the following extension for Visual Studio Code.
When done we hope you just need to install VS Code and the extension and with minimal knowledge of Source Code Management you are up and running with your Code in place in a Git Repository.
We look forward to every ones contributions.
Happy Code. Safe Code.
So it happened. I moved my blog to WordPress. Not that I did not like Office 365’s public site and all the great options that it gave me. Quite the opposite. The simple fact is that Microsoft is about to retire this option, so I just need to get it done before that happens.
I hope you will continue to enjoy my blog.
Did you get your Currency Exchange Rates from Bank of Canada? The format just changed as of June 1, 2017 and you now need to set it up via the new format.
Go to the Currencies page.
Click on Exchange Rate Services
Select New and create one with the following settings
Once you have populated the correct URL as seen above you can use the assist button in the Source Field to populate the nodes from the XML file in the lines.
For the Starting date you need to use the “US_DATE_FORMAT” Transformation Rule. If you don’t already have it you can look in a Cronus Database. It is already defined in the demo data.
To get the currency code you need to pick the 3rd to the 6th character from the FXUSDCAD text string. You can see the string when click the Assist button to pick the Node.
You can do this by creating your own transformation rule looking like this.
As you can see you can test your transformation rule in the bottom of the page by inserting your text and hitting the update on your right. The result will show in the result field.
The bad thing here is that I did not find a way to import multiple currencies with the new format from the Bank of Canada. It doesn’t look like the functionality supports this new format very well or the format is just a little strange.
If you need to find the exchange rates that works for you, Bank of Canada has a website explaining how their service works.
Hope this is use full to you all.
Did you know you can run PowerShell from Visual Studio Code?
One of the biggest strength of VS Code is its diversity and the fact it is very light weight. I have already been using VS Code to do a lot of things with Git for a while because it natively integrates nicely with Git which is a huge plus.
Now a while back I tried to use PowerShell with VS Code but it was just not working well at the time, but recently I tried again and things have changed a lot. If you install the PowerShell extension from Microsoft you can now edit and run PowerShell scripts natively inside VS Code just like you can from PowerShell or PowerShell ISE.
You can find the extension here:
VS Code – One tool to rule them all.
A while back I wrote Let’s clean up NAV #12 – Next Counting Period pointing out that the Next Counting Period field needed to be deleted in Table 27, 5700 and 7380.
Great to see this was done.
As the field was a Text(250) it was taking up a lot of space in the record that has now been freed up.
Thanks Microsoft. Highly appreciated.