Latest Contributions by MatthewDriscoll

No exception thrown.  It sits and spins for 5-10 minutes, all others tools are grayed out, the refresh spins, and nothing gets selected.   All features are in a sde database.   ... View more

This worked, calling just the name of the feature class and not the whole path.  I was wanting the default database.  Thank you for sticking with me Rich!  ... View more

This does not seem to successfully get a list of the feature class either, it returns the definitions but not the actual name.  I cannot find any examples of doing this in the snippets or help either.    Probably going to switch to python to do this task, but I would like to avoid that because python takes a lot longer to run. ... View more

Thanks Rich! I did mean feature class, I corrected the question.  When I tried your suggestion I get the error "Non-invocable member ;FeatureClassDefinition' cannot be used like a method.  Below is what I ended up trying, it runs without error, but it still does not see the feature class when it does exist. string projGDBPath = Project.Current.DefaultGeodatabasePath; string FC = TXB.Text; // From a text box in the xaml             string fcFINAL = System.IO.Path.Combine(projGDBPath, FC);             await ArcGIS.Desktop.Framework.Threading.Tasks.QueuedTask.Run(() => {                 using (Geodatabase geodatabase = new Geodatabase(new FileGeodatabaseConnectionPath(new Uri(projGDBPath))))                 {                     try                     {                         FeatureClassDefinition featureClassDefinition = geodatabase.GetDefinition<FeatureClassDefinition>(fcFINAL);                         featureClassDefinition.Dispose();                         ArcGIS.Desktop.Framework.Dialogs.MessageBox.Show("It exists");                     }                     catch                     {                         ArcGIS.Desktop.Framework.Dialogs.MessageBox.Show("It Does Not Exist");                     }                 }             });‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

There really is no "migration" of add-ins from Desktop to Pro.   It really is a completely different SDK, so no comparing apples to apples.   This was the first question I asked when I took the Pro SDK class, hoping it would be a simple change of a couple things in my add-ins.   Python is very similar in both, but the Pro SDK and ArcObjects are very different.  Just dive in and start from scratch, it is not too difficult to pick up the Pro SDK.  I had about a dozen add-ins to redo from Desktop to Pro and was able to find a way to replicate all them.  Good Luck!   ... View more

Thanks Dan.   I think I will try to create a add-in to run the script tool, then add the layer using the add-in (if possible) after the scripts runs as a workaround. Edit:   Using an add-in ended up being a satisfactory work around for me. ... View more

So are you saying that this is not possible in Pro with python?  I tried to test it keeping it simple of using the CURRENT, creating a feature class in the default database and then try adding it.  It always fails with the message being that the new feature class does not exists.   If I do the exact same lines one by one in Pro python window it will work fine.   But doing this in a script or a python toolbox script tool it fails.   So this is just not possible in Pro?  This is a straight forward work flow, and it is not an option? ... View more

It does not appear to be fixed in 2.3. ... View more

Thank you Dan, I will give it a go! ... View more

Any update on this? ... View more

I too would like a timeline for this.  I have twenty users waiting to switch to Pro since 2.0, but our main editors need these tools for precision editing, and some other basic Desktop tools, before we can switch.         ... View more