AnsweredAssumed Answered

Debugging problems for Pro SDK in VS

Question asked by gissense on Oct 31, 2016
Latest reply on Nov 19, 2016 by gissense

Like • Show 0 Likes0
Comment • 15

It seems I can't debug an ArcGIS Pro Addin in VS.
Every time it struggles and gives me a System.AggregateException.
It seems like the map is not being loaded well.
I've tried to do some changes in the firewall, but no results.
If I run the project directly, no problems. It happens only if I run it via debug in VS.
Any ideas?

"An unhandled exception of type 'System.AggregateException' occurred in mscorlib.dll
Additional information: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread.
"

No one else has this question

Outcomes

15 Replies

cmacleod-esristaff Oct 31, 2016 8:54 AM
Mark Correct
Correct Answer
Sounds like a timing issue. That is, running on the VM is changing the sequence of execution in the Add-in. From the exception you are making an Async call that you are not awaiting. That async call is failing when you are running on the VM (but I have no idea why). If you use the debugger and look at the inner exceptions property it may give you the actual exception that faulted the task. That said, if you do "await" the async call you can bracket it with a standard "try { } catch" block to trap the exception.

I will need to see your code to assist further.
Like • Show 0 Likes0
Actions
- gissense @ cmacleod-esristaff on Oct 31, 2016 1:42 PM
  Mark Correct
  Correct Answer
  Hello Charles,
  
  Thank you.
  It looks like it has to do with the use of the MapView in the code.
  I created a very simple test AddIn with only 1 button. After commenting the bold lines below, it works like it should.
  The initial problem remains: the MapView is not loading well when debugging (white map), TOC loads only after focussing.
  
  using System;
  using ArcGIS.Desktop.Framework.Contracts;
  //using ArcGIS.Desktop.Mapping;
  using ArcGIS.Core.Geometry;
  using ArcGIS.Desktop.Framework.Dialogs;
  using ArcGIS.Desktop.Framework.Threading.Tasks;
  namespace effe
  {
  internal class Button1 : Button
  {
  protected override void OnClick()
  {
  //testen
  try
  {
  QueuedTask.Run(() =>
  {
  string test = "{ \"xmin\" : 1, \"ymin\" : 2,\"xmax\":3,\"ymax\":4,\"spatialReference\":{\"wkid\":4326}}";
  Geometry geom = GeometryEngine.ImportFromJSON(JSONImportFlags.jsonImportDefaults, test);
  //IDisposable x = MapView.Active.AddOverlay(geom);
  MessageBox.Show("toegevoegd: " + geom.ToString() + " json: " + geom.ToJson());
  }
  );
  } catch (Exception ex)
  {
  MessageBox.Show("FOUTJE: " + ex.ToString());
  }
  
  }
  }
  }
  Like • Show 0 Likes0
  Actions
  - cmacleod-esristaff @ gissense on Oct 31, 2016 3:38 PM
    Mark Correct
    Correct Answer
    I cannot reproduce your error. I opened a new project with the World Topo base map. Can you change your code as follow please: (this will allow you to catch the exception):
    
    protected async override void OnClick() {
    try {
    await QueuedTask.Run....
    
    Also, is there a base map currently drawn in your project or a blank map display? Is the map 2D or 3D?
    1 person found this helpful
    Like • Show 0 Likes0
    Actions
    - gissense @ cmacleod-esristaff on Nov 1, 2016 1:37 PM
      Mark Correct
      Correct Answer
      I tried with the base map and also with only a local featureclass (both 2D). But the results are the same.
      See my response to Wolfgang below...
      Like • Show 0 Likes0
      Actions

wkaiser-esristaff

Nov 1, 2016 8:53 AM

Collin,

I enhanced your 'simple button' add-in a bit using the code snippet below and was able to debug and run the add-in without problems. I think the main issue was that the IDisposable object returned by AddOnOverlay has to be maintained since the added overlay is removed from the mapview when that object is disposed. The code below uses the button click to add a polygon to the overlay and then removes the same polygon on the next button click. I hope this snippet will work for you.

using System;
using System.Collections;
using System.Collections.Generic;
using System.Threading.Tasks;
using ArcGIS.Core.CIM;
using ArcGIS.Desktop.Framework.Contracts;
using ArcGIS.Core.Geometry;
using ArcGIS.Desktop.Framework.Dialogs;
using ArcGIS.Desktop.Framework.Threading.Tasks;
using ArcGIS.Desktop.Mapping;

namespace ProAppModule2
{
    internal class Button1 : Button
    {
        private IList<IDisposable> _addOns = new List<IDisposable>();
        protected override async void OnClick()
        {
            //testen
            try
            {
                // clear any geometries on overlay
                if (_addOns.Count > 0)
                {
                    foreach (var addOn in _addOns) addOn.Dispose();
                    _addOns.Clear();
                    MessageBox.Show("Overlay clear");
                }
                else
                {
                    var symbol = OverlaySymbol;
                    await QueuedTask.Run(() =>
                    {
                        Envelope env = Geom.Result;
                        Polygon poly = PolygonBuilder.CreatePolygon(env);
                        _addOns.Add(MapView.Active.AddOverlay(poly, symbol.Result));
                        MessageBox.Show("toegevoegd: " + Geom + " json: " + env.ToJson() + env.GeometryType);
                        MapView.Active.ZoomTo(env);
                    });
                    MessageBox.Show("zoomed");
                }
            }
            catch (Exception ex)
            {
                MessageBox.Show("FOUTJE: " + ex.ToString());
            }
        }

        private Task<Envelope> Geom
        {
            get
            {
                return QueuedTask.Run(() =>
                {
                    var test =
                        "{ \"xmin\" : 1, \"ymin\" : 2,\"xmax\":3,\"ymax\":4,\"spatialReference\":{\"wkid\":4326}}";
                    return GeometryEngine.ImportFromJSON(JSONImportFlags.jsonImportDefaults, test) as Envelope;
                });
            }
        }

        private Task<CIMSymbolReference> OverlaySymbol
        {
            get
            {
                return QueuedTask.Run(() =>
                {
                    CIMStroke outline = SymbolFactory.ConstructStroke(ColorFactory.BlackRGB, 2.0, SimpleLineStyle.Solid);
                    CIMPolygonSymbol fillWithOutline = SymbolFactory.ConstructPolygonSymbol(ColorFactory.RedRGB,
                        SimpleFillStyle.Solid, outline);
                    return fillWithOutline.MakeSymbolReference();
                });
            }
        }
    }
}

3 people found this helpful

Actions

gissense @ wkaiser-esristaff on Nov 1, 2016 1:34 PM
Mark Correct
Correct Answer
Hello Wolfgang and Charles,

Thanks for responding.
Both your code work, but only if I create a new project during the debugging.
If I want to start debugging with a recent project, it fails to load the mapview.
The problem (in my opinion) is not in the code, but in my environment/settings.
Occasionally I was able to see some exception message:
System.InvalidOperationException: The map viewer is not initialized.
at ArcGIS.Desktop.Mapping.MapView.ValidateCanCallMapViewer(Boolean throwEx)
at ArcGIS.Desktop.Mapping.MapView.ZoomTo(Geometry geometry, Nullable`1 duration, Boolean maintainViewDirection)
at effe2.Button2.<>c__DisplayClass1_0.<OnClick>b__0()....

Are there known issues with a not initializing mapviewer (in debug mode) on a saved ArcGIS Pro project?
Maybe in combination with particular debug settings or other VS extensions (like WebEssentials)?

Best regards,
Collin Kleiboer
Like • Show 0 Likes0
Actions

YLiu-esristaff Nov 3, 2016 12:08 PM
Mark Correct
Correct Answer
I just tested it on latest Pro 1.4 but was not able to reproduce it, new Pro project or existing ones. And a quick search does not show any similar issue/bug reported before either. You probably already did it... but could you try to create a new Pro add-in project and see if it still happens? It would help us narrow down the issue to either the project or your environment.
Like • Show 0 Likes0
Actions
- gissense @ YLiu-esristaff on Nov 3, 2016 12:47 PM
  Mark Correct
  Correct Answer
  Hi Yuan,
  
  I removed all AddIn's, created a new (Pro) project/solution and added a button. Started a debug-session. Same result. Map starts loading (the 3 vertical lines), then suddenly stops. I get the System.AggregateException on a certain moment again.
  Running tasks:
  Not Flagged 5808 Awaiting Async: <Initialize>d__0
  Not Flagged 5807 Blocked System.Threading.WaitHandle.InternalWaitOne Task: <WaitForViewState>b__2c
  
  Regards,
  Collin Kleiboer.
  Like • Show 0 Likes0
  Actions
- wkaiser-esristaff @ YLiu-esristaff on Nov 3, 2016 1:06 PM
  Mark Correct
  Correct Answer
  I it tried on Win 10 - Pro - anniversary edition - VS 2015 - update 3 and both Pro 1.3 (release) and 1.4 (7008). The sample code from above works fine (I had to change the namespace to match my newly created add-in's namespace). Not sure what versions Collin is using.
  Like • Show 0 Likes0
  Actions
  - gissense @ wkaiser-esristaff on Nov 3, 2016 1:11 PM
    Mark Correct
    Correct Answer
    Win 10 pro
    VS Community 2015 update 3
    ArcGIS Pro 1.3
    Like • Show 0 Likes0
    Actions
wkaiser-esristaff Nov 6, 2016 11:59 AM
Mark Correct
Correct Answer
Hi Collin,
I configured a system using the configuration you listed: VS Community 2015 Update 3, Win 10 Pro, and Pro 1.3. I have no problems debugging and running (without debugger) the sample code from your original email. I don't think the problem you are seeing has anything to do with Pro 1.3. Unfortunately there can be various other issues that prevent you from debugging like video drivers, security policy, custom system configuration (like custom well-known folder locations) and more. I would recommend trying to reinstall VS 2015 once more and if that doesn't help contact Esri support.
Like • Show 0 Likes0
Actions
- gissense @ wkaiser-esristaff on Nov 6, 2016 12:07 PM
  Mark Correct
  Correct Answer
  Hi Wolfgang,
  
  Thanks for the research. I'll try to re-install / repair VS as you proposed. I'll share the results.
  Like • Show 0 Likes0
  Actions
  - gissense @ gissense on Nov 7, 2016 12:50 PM
    Mark Correct
    Correct Answer
    VS and Pro repaired, but no effect, unfortunatelly.
    Like • Show 0 Likes0
    Actions
- gissense @ wkaiser-esristaff on Nov 12, 2016 2:47 AM
  Mark Correct
  Correct Answer
  Fully uninstalled and installed VS2015 (Community). And also uninstalled and installed ArcGIS Pro. Installations with firewall and virusprotection disabled. Also done some restarts in between. No effect at all. Still the same problem.
  I'm going to give it a go on a VM.
  Like • Show 0 Likes0
  Actions
- gissense @ wkaiser-esristaff on Nov 19, 2016 12:20 PM
  Mark Correct
  Correct Answer
  When I use a VM (win7, fresh VS2015community, fresh Pro 1.3.1) all goes well, luckily. I can debug again! ;-)
  Thank you all for the help, though!
  Like • Show 0 Likes0
  Actions

GeoNet

The Esri Community

Debugging problems for Pro SDK in VS

Outcomes

Related Content

Recommended Content