Latest Contributions by Wolf

Try this .Net method: System.IO.Path.GetFileNameWithoutExtension (thePathVariable);‍ ... View more

Please open the config.daml file of you add-in project and find you custom button, then change the text in the caption attribute from "DataPreparation" to "Data Preparation" or "Prepare Data" (please note the space between words).  Then rebuild and run the add-in. ... View more

Hi Jonas,  I tried this using ArcGIS Pro 1.4.1 (same build as yours) and VS 2015 Update 3, C# and can't find any problems.  Having experienced similar issues in the past I usually traced it to another add-in, in which case removing all add-ins fixed the problem.   In a rare case I traced an issue to left-over configuration files (in the Pro / bin folder) that I played with on previous installations of Pro and then forgot to remove before upgrading my Pro version.  If you have done anything like this, I recommend to uninstall Pro, check for any left over files, remove them, and then reinstall Pro.     ... View more

I tested this issue using the following environment: Windows 10 - Creator Update - Version 1703 ArcGIS Pro 1.4 ArcGIS Pro SDK 1.4 Visual Studio 2013 - latest update .Net 4.6.2 developer pack I was not able to duplicate your problem, I am able to build and debug existing Add-ins and create new ones - below my screen shot will running VS 2013 in the debugger: At his point I would recommend to remove ALL add-ins from your well known add-in folder(s).  My best guess is that at this point you have some other add-in that might cause the exception.  By default your add-ins are stored here: <my documents folder>\ArcGIS\AddIns\ArcGISPro\   ... View more

I am upgrading one of our test machines to Windows Creator update in order to check this specific problem.  I have another machine with Windows 10 Creator update running ArcGIS Pro 1.4 and Visual Studio 2017 and was able to build/compile/debug existing add-ins from the community samples site, however, in VS 2017 the templates are not available to create a new add-in.  I will take a while to update one of my VS 2013 machines, but I will report my finding back on this thread. ... View more

Links in your text are working now 🙂  the links under resources (bottom) haven't been updated. Thanks & gr8 job, Wolf ... View more

Tried Chrome and Chrome shows a login prompt for the 'Prototype Lab Demo Portal' but i received this error after i logged in:   We're sorry, but you need additional privileges to access this site. Please contact servicedesk@esri.com for assistanc ... View more

Great blog Mark!  Your UI looks impressive.  I was not able to download the prebuilt add-in for some reason (stuck at the loading icon - maybe because I am using Edge), but I am able to check out your code on GitHub 😉  thanks much. - W ... View more

The ArcGIS Pro SDK is not built on top of ArcObjects instead it is using "64 bit Engine level ArcObjects" somewhat similar to what "ArcGIS Enterprise" (formerly ArcGIS Server) is using.  Also currently we only extend ArcGIS Pro through Add-ins and Configurations so it's not possible to build a standalone 64bit application using the Pro SDK with the exception of a minimal functional subset demonstrated here:  https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/CoreHost  here is the ProConcept for stand alone Pro apps: https://github.com/Esri/arcgis-pro-sdk/wiki/ProConcepts-CoreHost  ... View more

Hi Kirk,  Your question is probably best answered in a Microsoft c# Forum because the answer is found in the way Microsoft's Task-based Asynchronous Pattern (TAP) works.  In general "Wait" will synchronously block until the task completes. So the current thread is literally blocked waiting for the task to complete. As a general rule, you should always use 'await' in the context of ArcGIS Pro SDK asynchronous coding.  - Wolf ... View more

Hi Christopher,  I tried this sample from the community samples:  https://github.com/esri/arcgis-pro-sdk-community-samples/tree/master/Editing/ConstructionTool and changed the code by commenting out the "Use edit operations ..." region in AttributeButton.cs and instead uncommented the "#if OrUseThis" section following the above region.  I think this closely reflects the workflow you describe above.  I then used the community sample dataset and ran the sample  and was able to execute the update multiple times.  Maybe you can see differences between the sample and your implementation.  Also I used Pro 1.4 for this. ... View more

 Sorry, but I misunderstood your workflow requirements, I was under the impression that your Shapefile schema is somewhat predictable (hence the template reference) and not totally dynamic.  My suggested workflow would only work if your Shapefile output always contains data of the same type like for example tax parcels, streets, or utility data and depending on your output schema type you could then use a template to generate the required Shapefile.  If your output Shapefile is totally dynamic and is depending on an unknown input schema then this will not work.  I had already relayed your workflow requirements to our product engineers and they are still checking on various GeoProcessing task input parameter options to see if schema creation can be made easier with the current release of ArcGIS Pro.  If we find a better option (over adding one field at a time) we add the answer on this thread, but I also added your 'add multiple fields' tool to our requirement list of the next release.  ... View more

 You are correct in your assessment of these limitations.  Needless to say some limitations are coming from limitations of the Shapefile standard, like the field name length and the GUID data type.  To get your workflow done I can only suggest to create a FGDB feature class template that works around these Shapefile limitations by using field names shorter than 10 characters and changes the data types to Shapefile supported types (i.e. GUID turns into a text field).  In this scenario field names shouldn't differ anymore (allowing you to map those fields) and you shouldn't get a '999999 error' for unsupported field types.  ... View more

 You are correct the DDL (Data Definition Language) which is used to define different structures of a database is not part of the ArcGIS Pro API.  So currently you have to use GeoProcessing tasks to manipulate Feature Classes and their structure.  I tried the workflow that you described and used a File Geodatabase Feature Class as a template for a new FGDB Feature Class.  I also made sure that my 'template Feature Class' contained field names with more than 10 characters.  However, I didn't experience the truncation of the attribute names that you described above nor did I get any errors.  I then used the 'Feature Class To Shapefile' GeoProcessing task which truncated my field names to 10 characters which is the length limit for shape file field names.  I was also able to use the 'Alter Field' GeoProcessing task to change field names with names longer than 10 characters without getting any errors. ... View more