Latest Contributions by Wolf

Yes for version 2.5 that is all that's required since release 2.5 of Pro was already running on .Net Framework 4.8 (Home · ArcGIS/arcgis-pro-sdk Wiki (github.com).  However, you should build your add-in with version 2.5 of ArcGIS Pro (and Pro SDK) installed on your development machine because newer (minor version) releases of Pro add functionality to the API that are not available in 2.5.  So if you build an Add-in targeted for 2.5 on a 2.8 development environment (with Pro 2.8 installed) you could potentially use a method or property that is only available in 2.8 and not in 2.5.  So your add-in would work fine on your development machine, but on your 2.5 machine you would experience the 'gray' buttons effect (which implies an exception was thrown on initialization).  ... View more

You can disable the automatic adding of the feature class to the current map by changing the GPExecuteToolFlags.AddOutputsToMap option (which is the default) to GPExecuteToolFlags.None, as shown in the snippet below.   IGPResult result = await Geoprocessing.ExecuteToolAsync("CreateFeatureclass_management", Geoprocessing.MakeValueArray(arguments.ToArray()), null, null, null, GPExecuteToolFlags.None);  After this is done, you can add the layer yourself, as shown in my Button 'OnClick' sample below: protected override async void OnClick() { await CreateFeatureClass("TTT", EnumFeatureClassType.POINT); } public enum EnumFeatureClassType { POINT, MULTIPOINT, POLYLINE, POLYGON } /// <summary> /// Create a feature class in the default geodatabase of the project. /// </summary> /// <param name="featureclassName">Name of the feature class to be created.</param> /// <param name="featureclassType">Type of feature class to be created. Options are: /// <list type="bullet"> /// <item>POINT</item> /// <item>MULTIPOINT</item> /// <item>POLYLINE</item> /// <item>POLYGON</item></list></param> /// <returns></returns> public static async Task CreateFeatureClass(string featureclassName, EnumFeatureClassType featureclassType) { List<object> arguments = new List<object> { // store the results in the default geodatabase CoreModule.CurrentProject.DefaultGeodatabasePath, // name of the feature class featureclassName, // type of geometry featureclassType.ToString(), // no template "", // no z values "DISABLED", // no m values "DISABLED" }; await QueuedTask.Run(() => { // spatial reference arguments.Add(SpatialReferenceBuilder.CreateSpatialReference(3857)); }); IGPResult result = await Geoprocessing.ExecuteToolAsync("CreateFeatureclass_management", Geoprocessing.MakeValueArray(arguments.ToArray()), null, null, null, GPExecuteToolFlags.None); var uri = new Uri(result.ReturnValue); var lyr = await QueuedTask.Run<FeatureLayer>(() => { var newLayer = LayerFactory.Instance.CreateFeatureLayer(uri, MapView.Active.Map, LayerPosition.AddToTop, $@"Lyr-{featureclassName}") as FeatureLayer; return newLayer; }); MessageBox.Show($@"Newly added: {lyr.Name}"); } You can also use the result.ReturnValue GDB  path to find the automatically added layer by comparing all feature layer datasources for the current map. ... View more

You have to change the name of the Layout.  I used this snippet below in a button to change the Layout name, which in turn is then used as the default file name.  Just make sure that you don't use invalid file name characters (like ':'). protected override async void OnClick() { Map map = null; await QueuedTask.Run(() => { var layoutItem = Project.Current.GetItems<LayoutProjectItem>().FirstOrDefault(i => i.Name.Equals ("layout", StringComparison.OrdinalIgnoreCase)); if (layoutItem != null) { var layout = layoutItem.GetLayout(); var defLayout = layout.GetDefinition(); var now = DateTime.Now.TimeOfDay; defLayout.Name = $@"msecs - {now.TotalMilliseconds}"; layout.SetDefinition(defLayout); } }); }   ... View more

This community sample shows how to do this:  arcgis-pro-sdk-community-samples/Map-Exploration/TableControlsDockpane at master · Esri/arcgis-pro-sdk-community-samples (github.com) In the xaml you can specify the CommandParameter:  <Button Command="{Binding DataContext.TableCloseCommand, RelativeSource={RelativeSource AncestorType={x:Type TabControl}}}" CommandParameter="{Binding TableName}" > TableName in this example is of the type string. In the code behind you can use the CommandParameter by simple adding 'param' to your RelayCommand as shown here: public ICommand TableCloseCommand { get; set; } public AttributeTableViewModel() { TableCloseCommand = new RelayCommand((param) => OnCloseTab(param), () => true); } private void OnCloseTab(object param) { // cast the [object] param to the correct type [string] string tableName = param.ToString(); // use your TableName CommandParameter for processing } ... View more

As best practice the SDK team usually recommends to add common code to the Module class and then call the common code from buttons, tools etc. as shown in this example:  https://github.com/Esri/arcgis-pro-sdk-community-samples/blob/19a330dcbe57cdbbde7f0762e9321aa7b411c827/Map-Exploration/OverlayGroundSurface/MakeManyPolygons.cs#L52-52  The GetPlugInWrapper method shown in the reply above only gives you access to the ICommand interface but doesn't give you access to the underlying classes.  You also have to consider the just-in-time (JIT) strategy that is used for all controls in ArcGIS Pro: By default, controls appear enabled, but are not actually instantiated until they are clicked. This just-in-time (JIT) strategy improves resource utilization and startup time by deferring the instantiation of controls until they are initiated by the end user, however, this can be a problem if you try to share common code that is part of an instance of class (for example a Button or MapTool class).  We recommend the Module class singleton for these common code patterns.  You can add them either as 'static' methods (or properties) or add them to the Module class instance.  The Module class instance provides an accessor out-of-box with this property: public static Module1 Current.  You can then use Module1.Current to get to the instance. ... View more