Latest Contributions by DanielBean

Although this is an old post, I thought I was hitting the same problem in 10.4 for an add-in.  I was changing the python code and making a new .esriaddin file with makeaddin.py, yet the changes were not reflected.  It was not a cache problem, rather it was me not reinstalling the updated esriaddin.  After you make the .esriaddin file, you must double-click on it to execute the installation wizard.  This registers and makes a copy of your updated .esriaddin file to where ArcMap looks for it. If you skip the last step, you run the old python code.  You can verify this by searching for your .esriaddin file, you will find two files.  The one that ArcMap looks at is in the directory C:\Users\<User>\Documents\ArcGIS\AddIns\Desktop10.4\{832e6995-0daa-48aa-940f-0b6a04e3a5fe} or similar and is copied there by the installation utility. So to test changed python code: 1) Save the python code (.py) file 2) Run makeaddin.py  (which writes the local .esriaddin file, but not the one ArcMap looks at) 3) Double-click on the .ersiaddin file to invoke the add-in installation utility and install (Step 3 was missing in the ESRI docs) The correct version will be available in ArcMap,  When debugging, remember to open the ArcMap Python console to see any python code errors. ... View more

Curtis is correct, the original code does function correctly.  The problem was with my test mxd which was already zoomed to the desired extent, so no change was reflected in the test.  Zooming out on the test mxd, then running the code, zoomed the data frame to the extents of the 'Outline' layer correctly.  Thanks to all.  To zoom the data frame to the extents of layer 'Outline' the code would be: for lyr in arcpy.mapping.ListLayers(mxd, 'Outline'):     lyr_extent = lyr.getExtent()     df.extent = lyr_extent ... View more