<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Dotnet D365 on Chris McKelt - Remembering Thoughts</title><link>https://blog.smarttechventures.au/tags/dotnet-d365/</link><description>Recent content in Dotnet D365 on Chris McKelt - Remembering Thoughts</description><generator>Hugo -- 0.147.2</generator><language>en</language><lastBuildDate>Mon, 03 Dec 2018 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.smarttechventures.au/tags/dotnet-d365/index.xml" rel="self" type="application/rss+xml"/><item><title>D365 FO OData proxy generation</title><link>https://blog.smarttechventures.au/articles/posts/d365-fo-odata-proxy-generation/</link><pubDate>Mon, 03 Dec 2018 00:00:00 +0800</pubDate><guid>https://blog.smarttechventures.au/articles/posts/d365-fo-odata-proxy-generation/</guid><description>&lt;h2 id="to-create-the-d365-finops-c-odata-proxy-do">To create the D365 FinOps C# OData Proxy do:&lt;/h2>
&lt;p>1. Install the following plugin&lt;/p>
&lt;p>&lt;a href="https://marketplace.visualstudio.com/items?itemName=Unchase.unchaseodataconnectedservice" target="_blank">https://marketplace.visualstudio.com/items?itemName=Unchase.unchaseodataconnectedservice&lt;/a>&lt;/p>
&lt;p>2. Using a Visual Studio Standard Library project and add a new ‘Connected Service’&lt;/p>
&lt;p>&lt;img alt="image" loading="lazy" src="https://raw.githubusercontent.com/chrismckelt/chrismckelt.github.io/master/_posts/posts/images/2019/12/clip_image0014.png">&lt;/p>
&lt;p>&lt;img alt="image" loading="lazy" src="https://raw.githubusercontent.com/chrismckelt/chrismckelt.github.io/master/_posts/posts/images/2019/12/clip_image0024.png">&lt;/p>
&lt;p>&lt;img alt="image" loading="lazy" src="https://raw.githubusercontent.com/chrismckelt/chrismckelt.github.io/master/_posts/posts/images/2019/12/image.png">&lt;/p>
&lt;p>3. Open the &lt;em>Reference.cs&lt;/em>  file in VS Code (&lt;em>VS Code seems to handle the file better than Notepad++ and Visual Studio)&lt;/em>&lt;/p>
&lt;p>4.  Search for the EDMX mega string in the file&lt;/p>
&lt;p>&lt;em>private const string Edmx  = @”[mega big xml string we need to change]”&lt;/em>&lt;/p></description></item><item><title>Dynamics 365 Field services mobile app debugging</title><link>https://blog.smarttechventures.au/articles/posts/dynamic-365-field-app-creating-a-resco/</link><pubDate>Sun, 11 Dec 2016 00:00:00 +0800</pubDate><guid>https://blog.smarttechventures.au/articles/posts/dynamic-365-field-app-creating-a-resco/</guid><description>&lt;p>This is an overview of how to build and debug a Dynamics 365 Field Services Mobile Application using &lt;a href="https://www.resco.net/woodford-overview/" target="_blank">Resco’s Woodford&lt;/a> mobile framework (JavaScript library)&lt;/p>
&lt;p>&lt;em>Please let me know if you have a better way to manage this development life cycle. Id be keen to improve the experience.&lt;/em>&lt;/p>
&lt;h1 id="what-does-the-mobile-application-look-like">What does the mobile application look like?&lt;/h1>
&lt;p>The project solution on disk&lt;/p>
&lt;p>&lt;img alt="image" loading="lazy" src="https://user-images.githubusercontent.com/662868/120943838-fa4d6d00-c763-11eb-9aeb-7607ff5b6027.png">&lt;/p>
&lt;p>This project uses TypeScript with VS Code.   Typescript helped catch lots of issues before deployment.&lt;/p></description></item></channel></rss>