ImportGeodatabaseDeltaAsync Obsolete

Question

So in 100.7 the static GeodatabaseSyncTask.ImportGeodatabaseDeltaAsync method is obsolete.  The replacement method is now a class method so requires a GeodatabaseSyncTask object, which in turn requires a Uri of a service to Create.  This makes no sense, having made this a static method was the correct move a few iterations ago.  Why should one need to Create a GeodatabaseSyncTask object?  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.

What is the driver behind this?  Why would you change something back to the previous less robust approach?  Guess I am rolling back to 100.6

Morten Nielsen‌

Michael Branscomb‌

Edit:  Would appear this change occurred at 100.6, so rolling back to 100.5.

JoeHershman · Answer

Thanks

SomeGISGuy · Answer

Oh right! I forgot you have to create it async. Sorry. Just use the deprecated method for now. It'll still work 🙂

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.

JoeHershman · Answer

Back in 100.3 in changed to the static method (I could not recall the version this changed). In 100.6 it has changed back to an instance method. GeodatabaseSyncTask constructors are internal. The CreateAsync method requires a Uri, which does not accept an empty string and from quick testing will fail with fake Url or if offline. This fails.... var st = await GeodatabaseSyncTask.CreateAsync(new Uri("http://nothing"));‍