<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ImportGeodatabaseDeltaAsync Obsolete in .NET Maps SDK Questions</title>
    <link>https://community.esri.com/t5/net-maps-sdk-questions/importgeodatabasedeltaasync-obsolete/m-p/620803#M7604</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So in 100.7 the static&amp;nbsp;GeodatabaseSyncTask.ImportGeodatabaseDeltaAsync method is obsolete.&amp;nbsp; The replacement method is now a class method so requires a&amp;nbsp;GeodatabaseSyncTask object, which in turn requires a Uri of a service to Create.&amp;nbsp; This makes no sense, having made this a static method was the correct move a few iterations ago.&amp;nbsp; Why should one need to Create a&amp;nbsp;&lt;SPAN&gt;GeodatabaseSyncTask object?&amp;nbsp; This method should be available offline, there is no reason to need a connection to the underlying service to merge deltas from an already downloaded delta database into an already offline database.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;What is the driver behind this?&amp;nbsp; Why would you change something back to the previous less robust approach?&amp;nbsp; Guess I am rolling back to 100.6&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://community.esri.com/migrated-users/3050"&gt;Morten Nielsen&lt;/A&gt;‌&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://community.esri.com/migrated-users/4061"&gt;Michael Branscomb&lt;/A&gt;‌&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Edit:&amp;nbsp; Would appear this change occurred&amp;nbsp;at 100.6, so rolling back to 100.5.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 03 Feb 2020 19:37:40 GMT</pubDate>
    <dc:creator>JoeHershman</dc:creator>
    <dc:date>2020-02-03T19:37:40Z</dc:date>
    <item>
      <title>ImportGeodatabaseDeltaAsync Obsolete</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/importgeodatabasedeltaasync-obsolete/m-p/620803#M7604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So in 100.7 the static&amp;nbsp;GeodatabaseSyncTask.ImportGeodatabaseDeltaAsync method is obsolete.&amp;nbsp; The replacement method is now a class method so requires a&amp;nbsp;GeodatabaseSyncTask object, which in turn requires a Uri of a service to Create.&amp;nbsp; This makes no sense, having made this a static method was the correct move a few iterations ago.&amp;nbsp; Why should one need to Create a&amp;nbsp;&lt;SPAN&gt;GeodatabaseSyncTask object?&amp;nbsp; This method should be available offline, there is no reason to need a connection to the underlying service to merge deltas from an already downloaded delta database into an already offline database.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;What is the driver behind this?&amp;nbsp; Why would you change something back to the previous less robust approach?&amp;nbsp; Guess I am rolling back to 100.6&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://community.esri.com/migrated-users/3050"&gt;Morten Nielsen&lt;/A&gt;‌&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://community.esri.com/migrated-users/4061"&gt;Michael Branscomb&lt;/A&gt;‌&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Edit:&amp;nbsp; Would appear this change occurred&amp;nbsp;at 100.6, so rolling back to 100.5.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Feb 2020 19:37:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/importgeodatabasedeltaasync-obsolete/m-p/620803#M7604</guid>
      <dc:creator>JoeHershman</dc:creator>
      <dc:date>2020-02-03T19:37:40Z</dc:date>
    </item>
    <item>
      <title>Re: ImportGeodatabaseDeltaAsync Obsolete</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/importgeodatabasedeltaasync-obsolete/m-p/620804#M7605</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/6566"&gt;Joe Hershman&lt;/A&gt;&amp;nbsp;It appears this&amp;nbsp;change&amp;nbsp;was done in May 2017, so many versions ago (100.3&amp;nbsp;I think?), and you should see the same thing in 100.6. Note that you don't need to load the task to perform the import - you don't even need a valid URL. It's a mistake in the API that you just pointed out (thank you for that!).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So&amp;nbsp;there's actually an API bug here.&amp;nbsp;For now I'd recommend you use:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;new GeodatabaseSyncTask("").ImportDeltaAsync(geodatabaseInstance, pathToDelta)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will under the covers actually call the correct code path, and we'll have a better static method available for Update 8.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Feb 2020 20:08:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/importgeodatabasedeltaasync-obsolete/m-p/620804#M7605</guid>
      <dc:creator>dotMorten_esri</dc:creator>
      <dc:date>2020-02-03T20:08:52Z</dc:date>
    </item>
    <item>
      <title>Re: ImportGeodatabaseDeltaAsync Obsolete</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/importgeodatabasedeltaasync-obsolete/m-p/620805#M7606</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Back in 100.3 in changed to the static method (I could not recall the version this changed).&amp;nbsp; In 100.6 it has changed back to an instance method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;GeodatabaseSyncTask constructors are internal.&amp;nbsp; The CreateAsync method requires a Uri, which does not accept an empty string and from quick testing will fail&amp;nbsp;with fake Url or if offline.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;This fails....&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE class="line-numbers language-csharp"&gt;&lt;CODE&gt;&lt;SPAN class="keyword token"&gt;var&lt;/SPAN&gt; st &lt;SPAN class="operator token"&gt;=&lt;/SPAN&gt; &lt;SPAN class="keyword token"&gt;await&lt;/SPAN&gt; GeodatabaseSyncTask&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;&lt;SPAN class="token function"&gt;CreateAsync&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;&lt;SPAN class="keyword token"&gt;new&lt;/SPAN&gt; &lt;SPAN class="token class-name"&gt;Uri&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;&lt;SPAN class="string token"&gt;"http://nothing"&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;;&lt;/SPAN&gt;&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Feb 2020 20:44:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/importgeodatabasedeltaasync-obsolete/m-p/620805#M7606</guid>
      <dc:creator>JoeHershman</dc:creator>
      <dc:date>2020-02-03T20:44:03Z</dc:date>
    </item>
    <item>
      <title>Re: ImportGeodatabaseDeltaAsync Obsolete</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/importgeodatabasedeltaasync-obsolete/m-p/620806#M7607</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Oh right!&amp;nbsp;I forgot you have to create it async. Sorry. Just use the deprecated method for now. It'll still work &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also after double checking you're right this was introduced in 100.7, not 100.3. My bad! I got down the wrong path in the git history.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Feb 2020 20:55:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/importgeodatabasedeltaasync-obsolete/m-p/620806#M7607</guid>
      <dc:creator>dotMorten_esri</dc:creator>
      <dc:date>2020-02-03T20:55:16Z</dc:date>
    </item>
    <item>
      <title>Re: ImportGeodatabaseDeltaAsync Obsolete</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/importgeodatabasedeltaasync-obsolete/m-p/620807#M7608</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Feb 2020 21:00:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/importgeodatabasedeltaasync-obsolete/m-p/620807#M7608</guid>
      <dc:creator>JoeHershman</dc:creator>
      <dc:date>2020-02-03T21:00:48Z</dc:date>
    </item>
  </channel>
</rss>

