Latest Contributions by MarkCederholm

I'm seeing the same issue when sharing from ArcMap 10.4.  Also, I get a System.NotSupportedException when I try to query related records in Runtime .NET 10.2.7.  [I don't see this problem when querying geodatabases created using the Sync framework.]  Hopefully, the Quartz release and mobile map packages will fix this problem. ... View more

I had a great time presenting this (before I caught an annoying bit of bronchitis for the rest of the DevSummit).  Here's a link to everything:  http://www.pierssen.com/arcgis10/server.htm ... View more

Hey, sorry my live demo was such a bust.  In hindsight, I should have presented the final widget code and compared it to the original standalone app.  Also, I completely forgot to get into Chrome debugging.  No logical excuse.  To be frank, I'm still trying to shake off the bronchial crap that I'd picked up in Palm Springs.  In any case, here's the link to everything:  http://www.pierssen.com/arcgis10/server.htm ... View more

Attached is a simple example of the approach I'm taking.  I definitely think that Behaviors are a great way to make the MapView more MVVM friendly. ... View more

In my opinion, creating a UI element within a view model is a violation of MVVM.  However, I also feel that way about using a handle to a UI element to perform an operation, which is exactly what the tutorial example does.  The example could be fixed specifically by passing the extent as the command parameter, but the fact is that the MapView is not very MVVM friendly in the first place: ideally, properties like extent and scale should be bindable to the view model bidirectionally. I have an application that loads different layouts based on a given configuration.  I don't include MapViews in the layouts, because I don't like the dependency on Runtime.  So yes, I search the layout for a designated MapView container, create a MapView, and wire it up inside the view model code, which I shouldn't be doing if I want a pure MVVM design*.  I'm not happy about it, but I haven't found another approach that I like any better. *After thinking about it some more, I decided to segregate the code better.  Now the app is in three basic components:  1) loader (loads the layout and creates the MapView), 2) view model (just a view model, nothing more), and 3) behavior (handles all interaction with the MapView). ... View more

BTW, there's no setup for 10.3 because VS 2013 doesn't come with an out-of-the-box setup project.  I'm dropping support for this app anyway, and will not create a version for 10.4.  I strongly recommend migrating to ArcGIS Runtime.  Collector and AppStudio are also viable approaches for non-programmers. ... View more

You need to make sure it’s also installed on the ArcReader machine. See the FAQ for other tips. --Mark ... View more

I'll try turn this into a lightning talk. ... View more

No error: the session just hangs until I kill it.  I went ahead and ran the command line upgrade instead, and it worked fine.  Bit of a head scratcher, though. ... View more

I'm trying to import a 1.2 project into 1.3 using the GUI, and it just sits there.  It has a custom widget, but I already copied my custom widgets into the widgets folder.  Did I do something wrong? ... View more