Latest Contributions by Wolf

Windows 8, 64 bit, ArcMap 10.4.1 and Visual Studio 2013 Pro is a supported configuration for the installation of the .Net SDK of ArcObjects 10.4.  Please double check your configuration and if that doesn't resolve your issue please contact Esri support.  ... View more

The main intend for the desktopVersion attribute is ensure add-in compatibility with Pro.  The version ensures that you are not using an add-in with an old version of Pro (let's say 1.2), when the add-in was built using a newer version of Pro (let's say 1.3 or 1.4 beta).  The old 1.2 version of Pro cannot run the 1.3 add-in because the 1.3 API changed (was added on to) and has additional functionality. ... View more

Hi Ted,   To change the target version you have to change the desktopVersion attribute of the AddInInfo tag in your config.daml file.  You can replace your current desktopVersion value with "1.3". ... View more

Hi Ted, I updated the sample @ https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Framework/ProgressDialog and added a progress dialog that iterates through a given number of steps as shown in my post above (see the readme.md for a screenshot of this functionality). ... View more

Hi Ted, I you use the sample @ https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Framework/ProgressDialog and make the update below in the "RunDialogButtonsCancel" class you will get the desired effect.  I will update the sample soon to reflect this capability.  The trick is to create your own ProgressDialog instance and specify the 'maximum steps' parameter. protected override async void OnClick() {   //If you run this in the DEBUGGER you will NOT see the dialog       uint maxSteps = 5;       var pd = new ArcGIS.Desktop.Framework.Threading.Tasks.ProgressDialog(                 "Doing my thing - cancelable", "Canceled", maxSteps, false);        await                 ProgressDialogModule.RunCancelableProgress(                     new CancelableProgressorSource(pd), maxSteps); } ... View more

Hi Horia, I verified your observations and will relay your findings to the developers.  I made a few changes to the custom popup sample https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Map-Exploration/CustomPopup specifically in "CustomPopupTool.cs" and this what I observed: Line 64 instantiates DynamicPopupContent which allows me to customize each page (by overriding "OnCreateHtmlContent"):     kvp.Value.ForEach(id => popups.Add(new DynamicPopupContent(kvp.Key, id))); If I run the code as shown above I do observe that the Title customization is not properly applied, however if I change the code to use the "configured pop-ups" content (from the Pop-ups dock pane) then I get the proper behavior regarding the title.  This is simply done by changing line 64 as follows:       kvp.Value.ForEach(id => popups.Add(new PopupContent(kvp.Key, id))); No as i scroll through my pop-up records i can see that the title changes according to what i specified on the Pop-ups dock pane for that layer.  Finally i can also override the Title property in the overridden "OnCreateHtmlContent" method in order to correct the title as required, but this causes a flash on the title bar as the old title is overridden. ... View more

The current map view requires a 'current' active tool.  You can look at this snippet how to change the current tool: FrameworkApplication.SetCurrentToolAsync("esri_mapping_selectByRectangleTool"); where "esri_mapping_selectByRectangleTool" is the DAML id of the tool. See: https://github.com/esri/arcgis-pro-sdk/wiki/ProSnippets-Framework#set-the-current-tool ... View more

I modified the sample to use the 'selected' layer for the add/delete operations and it appears the same problem you discovered in the Pro UI exists even when I programmatically change the schema - the schema change is always executed on the top most layer (given your pre-conditions).  Everything works as expected after I make the layer name unique.  Maybe for the time being you can append a string to your layer names (like ... "RoadSegment (production)" and "RoadSegment (proposed)" ) in order to work around this issue until a fix is available. ... View more

Hi Horia, My sample always looks at the top most layer to perform its actions (add/delete field) and that seems to work.  When I tried your scenario from the user interface by deleting a field of the layer that is not the top most layer (with your given setup) I also noticed that the field in the top most layer was deleted instead of the field in the layer that I had chosen.  We relayed the scenario to the appropriate developers and I will try a small modification to my sample to check if the behavior fails programmatically as well. Thanks Wolfgang ... View more

I added a new sample to community sample repo: https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Geodatabase/AddDeleteFieldToFromFeatureClass I also tested this sample with a scenario similar to yours by adding two feature classes that are stored in to different geodatabases to my map using the same layer name.  The sample changes the top most layer, I added the new field and it worked as expected: Next I moved my second top layer to the top and added a new field here as well: Finally I deleted the latest newly added field which worked as expected: Maybe you can try the sample and see if it works with your data. ... View more

For future reference you can find this type of information on our GitHub ArcGIS-pro-sdk repository under the requirement section (https://github.com/Esri/arcgis-pro-sdk/wiki#requirements) and in the release notes section: https://github.com/Esri/arcgis-pro-sdk/wiki#release-notes ... View more

I tried the following code (new project and simply adding an AddField button) using the sample data from the community samples (GitHub) repo and it worked without any exceptions.  To catch any exceptions in your code you should always use a try {} catch () {} sequence like in my sample below. internal class AddField : Button     {         protected override async void OnClick()         {             await ExecuteAddFieldTool("test2", "Test 2", "TEXT", 100);         }         private async Task<bool> ExecuteAddFieldTool(string fieldName, string fieldAlias, string fieldType, int? fieldLength = null,             bool isNullable = true)         {             try             {                 var inTable = @"TestLines";                 var workspaceName = @"C:\Data\FeatureTest\FeatureTest.gdb";                 var parameters = Geoprocessing.MakeValueArray(inTable, fieldName, fieldType.ToUpper(), null, null,                     fieldLength, fieldAlias, isNullable ? "NULABLE" : "NON_NULLABLE");                 var env = Geoprocessing.MakeEnvironmentArray(workspace: workspaceName);                 var cts = new System.Threading.CancellationTokenSource();                 var results = Geoprocessing.ExecuteToolAsync ("management.AddField",                     parameters, env, cts.Token, (eventName, o) =>                     {                         switch (eventName)                         {                             case "OnValidate":                                 if (((IGPMessage[]) o).Any(it => it.Type == GPMessageType.Warning))                                 {                                     MessageBox.Show($"{eventName}: {o}");                                 }                                 break;                             case "OnMessage":                             case "OnProgressMessage":                                 MessageBox.Show($"{eventName}: {o}");                                 break;                             case "OnProgressPos":                                 MessageBox.Show($"{eventName}: {o} %");                                 break;                             default:                                 MessageBox.Show($"{eventName}: {o} %");                                 break;                         }                     });                 await results;                 return true;             }             catch (Exception ex)             {                 MessageBox.Show(ex.ToString());             }             return false;         }     } ... View more

After you change the Selection color try to use 'SetDefinition' on your FeatureLayer as in (from API reference guide): public void SetDefinition(    CIMBaseLayer baseLayer ) GetDefinition only returns a copy of ArcGIS Pro's internal settings (not a reference), SetDefinition will then post your changes back to ArcGIS Pro. Also you can find some samples dealing with the CIM here: https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Map-Authoring/CIMExamples ... View more

Hi Jason,   When we release SDKs for .Net we support compatibility with the latest two commercially available versions of Visual Studio, hence, we supported VS 2012 & 2013 compatibility for 10.3 and VS 2013 & 2015 compatibility for 10.4. 10.3.1, is a 'maintenance release' for 10.3 and therefore adds no new functionality.  10.3.1 just as 10.3 supports VS 2013 and VS 2012.  There is a VS 2013 Community Edition available (which replaces VS 2013 Express) that you can use with the 10.3.1 SDK for .Net.  When you install the 10.3.1 SDK the setup might identify Community Edition as 'Express' but everything works with Community Edition. You can install both VS 2013 & 2015 Community side by side on the same development machine. ... View more

Jason,   Which version of the "ArcObjects SDK for the Microsoft .NET Framework" are you trying to install?  The requirements for the latest release (10.4.0) can be found here (scroll to the bottom of the section): ArcObjects SDK 10.4 system requirements—System Requirements | ArcGIS for Desktop ... View more