6,092
Hi there,
this is for source control... I would like to know which cumulative updates of NAV2013R2 are already included in the NAV2015 RTM, to set a useful branch. Does anybody know?
with best regards
Jens
*This post is locked for comments
Seems really good, I definitely need to look into this Tortoise tool, I still use Mergetool and Object Manager Advanced for these tasks.
Hi Daniele,
I did it my own old-school way by using mercurial (Tortoise HG Workbench ) and tortoisemerge (Tortoise SVN). As split / combine tool I use the NAVObjectSplitter (3.0?) from Carsten Scholling. And a few cmd files.
The screen shot is from the THG Workbench, with the NAV2015 DE tree open. Mercurial as revision control system is pretty much awesome, and it's of course text-based and completely format/syntax agnostic. The only three situations where this is a problem is with headers (version list, date), changed control/variable IDs, and comments section. But this is also the case when you use SVN or Git, so... you get to know the issues and learn where to expect issues when you do a merge.
I have had a look at the new merge cmdlets, but unfortunately, they only use the object sets for the merge, not the history of changesets. I don't see a lot of real-world use cases where using the cmdlets is actually an improvement... the workflow appears to me as not reality-tested. There are very few (read: none) occasions where no manual intervention is needed, and then you're more or less lost with the cmdlets.
Kine has a setup where he's using git, powershell and the merge cmdlets: http://dynamicsuser.net/blogs/kine/archive/2014/07/22/powershell-strong-tool-for-ms-dynamics-nav-developers.aspx
I would love to write an extension to thg to handle the remaining issues of the merge, but I am still drilling into the source code of it. :)
with best regards
Jens
Thanks for sharing!
Out of curiosity...did you use the merge commandlets or just went with the old-fashioned way with code compare?
The object sets can be downloaded from mibuso now: www.mibuso.com/dlinfo.asp
Well I've done the branch and merge now. It appears that the assumption that the C/AL codebase of NAV2015 RTM is based on NAV2013R2 CU10 is the best match. One thing was noteworthy, though: Almost all changes from CU11 in the pages that already had a NAVW18.00 version tag are contained in NAV2015. This isn't the case for tables, codeunits, reports. So, it's a partial.
<edit: spelling, clarity>
Hi Snehanshu,
thank you for the answer. After I've successfully (and quite painfully) installed NAV2015 DE on my machine, I got curious and did some comparisions. As it is, what you state is basically true, but the RTM (Build 37874) seems to be based on Cumulative Update 10, Build 37563. I could identify this on the changes in CU12, CU21 and CU427. Also, all hotfixed objects (previously NAVW17.10.00.?????) and all new/changed objects have the version tag NAVW18.00, but not all objects of NAV2015.
Can somebody from Microsoft please confirm this?
Regarding the painful install: I Installed it on my main laptop, which is Win7 x64 ultimate DE. There are some issues with the installation:
1. As is the case since NAV2013, the default account for the service tier is NT AUTHORITY\NETWORK SERVICE, which apparently doesn't exist in the german Win7. BUT, the installation does an almost full roll-back of everything already installed when the service tier can't be started. This is a PITA. Best would be that the default account actually exists, but scrapping the whole installation because of the account is an overreaction. Nobody cared the last two releases, so what has changed?
2. The installation will likewise fail and roll back if you have other services running on the NAV TCP ports. Since you can't install directly with port sharing enabled, this is also a PITA. It took me about 5 installation runs to get everything right. The root cause of the problem appears to be the "roll back when something goes wrong" behaviour.
3. .net Framework should be installed on the machine BEFORE you try to install NAV2015. The setup actually installs it, but - you can guess it - it requires a reboot to be fully functional. When the setup installs all the components, only to run on an error because of it and rolls the NAV installation back. Painful.
<edit>
I have also installed the RTM on a Win8.1 x64 fully patched. Aside from the .net 4.5.2 problem and the ensuing rollback, the demo installation went through.
with best regards
Jens
<edit: spelling, additional info>
Hi,
Microsoft includes the issues resolved in last commulative hot fix released for it's previous version of product in it's immediate product version release (in other words Microsoft includes the changes made in any cummunlative hot fixes but not the actual hot fixes in new product release). Once the new product version is released, any subsequent hot fixes will be there for all available versions of the software (if it is within software lifecycle support).
When NAV 2015 was released (yesterday), last cummulative hot fix for NAV 2013 R2 was 11 and last commulative hotfix for NAV 2013 was 18. So I am assuming all the code changes incorporated in those hotfixes will be included in NAV 2015. Any subsequent cummulative hotfix will be like -
- Hotfix 12 for NAV 2013 R2
- Hotfix 19 for NAV 2013
- Hotfix 1 for NAV 2015
Hope this information helps.
Thanks
Snehanshu
#1
André Arnaud de Cal...
291,711
Super User 2024 Season 2
#2
Martin Dráb
230,458
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
