Two months ago I started to use the RELEASE_NOTES.md files feature in FAKE to describe FAKE’s own changelog. It’s working pretty well with FSharp.Formatting and the whole process got much easier for me. One of the intersting side effects is that I didn’t use the develop branch any more. Pre-release packages can be pushed directly from master.
So in order to make it easier for new contributors I will follow standard git workflow and remove the develop branch completely. Please send your pull request directly to the master branch.
We are still porting one of our products from Dynamics NAV 2009 R2 (Classic Client) to NAV 2013 R2 and found another strange issue:
On Dynamics NAV 2009 R2 Classic client (Build 6.00.33494):
FORMAT(13.5671,0,'<Integer,4>'); ==> 0013,5671
FORMAT(13.5671,0,'<Precision,0:0><Integer,4>'); ==> 0014
But on Dynamics NAV 2013 R2 (Build 7.10.36281) we get:
FORMAT(13.5671,0,'<Integer,4>'); ==> 0013,5671
FORMAT(13.5671,0,'<Precision,0:0><Integer,4>'); ==> 0013
Not sure if it is that important for practical purposes, but it’s breaking some of our unit tests. ;-(
At the moment we are porting one of our products from Dynamics NAV 2009 R2 (Classic Client) to NAV 2013 R2. We have thousands of unit tests and most of them work out of the box.
But now my colleague Matthias Schäfer found a very strange issue. Consider this snippet:
On Dynamics NAV 2009 R2 Classic client (Build 6.00.33494) we get the same message twice:
But on Dynamics NAV 2013 R2 (Build 7.10.36281) we get:
Weird, isn’t it?
Update 1
This is what the Dynamics NAV compiler is emitting:
We assume this is what the Dynamics NAV compiler should do: