So with the new release there has been a whole raft of changes. I’ll continue to update on the updates that I personally have found useful and hopefully you will too. Firstly since the AOS is no longer a Windows service, it won’t be possible to open “Services” and manually stop, start and restart it. The way to do this in AX is now to run the command prompt with Administrative privileges and run the “iisreset” command. To redeploy AX you’ll need to navigate to C:\CustomerServiceUnit and then right click AOSDeploy.cmd and click run as administrator. Microsoft recommends the minimum of 2 cores for AX. I’m running mine of D4v2 and it seems to be running fine. If you haven’t upgraded your VM’s to the new Dv2 series, I’d recommend it. Apparently the performance improvements are as much as 35% extra with probably only a 5% (approximately) increase in cost. It’s a no brainer really. If you loaded your VM’s on the old D series Cloud Service, you’ll need to create a new Cloud service and then merge your VM’s. If you don’t know how to do this, drop me a line in the comments and I’ll explain it in more details. Then there’s also a cool new reference diagram. I love visuals and I’m constantly drawing pictures like the one below when debugging code. So it’s good to see Microsoft make a very visually appealing diagram. Then finally when it comes time to export and import models, it looks as if the Powershell tools won’t be working just quite yet. I could be wrong, but by the looks of the below article, it looks as if you can only use ModelUtil for now. AX Wiki article That’s all for now. Hopefully more to come soon. Peace! The post Further thoughts on AX (7) appeared first on Betastack .
↧