I didn’t realize something .. but since April this year, I have been blogging for a full 10 years. Not THE most important topic ever created – definitly not when Microsoft announces big new things like Microsoft 365 and such – but hey, it’s holiday-season ;-). I still remember why I started blogging: I just …
Permanent link to this article: http://www.waldo.be/2017/07/14/10-years-waldos-blog/
You might remember this post: http://www.waldo.be/2017/02/20/make-the-new-developer-tools-available-on-a-local-machine/ Well, back in those days, I might have forgotten a few bits ;-). Namely to enable the in-client visual designer. Well, there is not much to it – you can simply edit the web.config-file, and add the designer-attribute in it.. . With PowerShell, you can do it with:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
$NAVWebConfigFile = "C:\inetpub\wwwroot\Navision_main\Web.config" $NAVWebConfig = [xml](Get-Content $NAVWebConfigFile) $designerKey = $NAVWebConfig.SelectSingleNode("//configuration/DynamicsNAVSettings/add[@key='designer']") if ($designerkey) { $designerkey.value = "true" } else { $addelm = $NAVWebConfig.CreateElement("add") $keyatt = $NAVWebConfig.CreateAttribute("key") $keyatt.Value = "designer" $addelm.Attributes.Append($keyatt) | Out-Null $valatt = $NAVWebConfig.CreateAttribute("value") $valatt.Value = "true" $addelm.Attributes.Append($valatt) | Out-Null $NAVWebConfig.configuration.DynamicsNAVSettings.AppendChild($addelm) | Out-Null } $NAVWebConfig.Save($NAVWebConfigFile) |
…
Permanent link to this article: http://www.waldo.be/2017/07/06/create-an-offline-development-preview-enable-the-in-client-visual-designer/
When you want to experience the new developer tools, you need to set up a VM on Azure. Now, this takes a while. On top of that, it’s all “preview”. As in: “might crash”. And in: “if it crashes, there might not be a decent way out”. I was able to completely mess up my …
Permanent link to this article: http://www.waldo.be/2017/07/04/nav-developer-preview-fix-script/
Loading ...