NET component, interface, or even Python library which changed between August and September which is causing the crash, and send that information to Esri. Maybe in your complex work you can identify the exact DLL. It appears that 3.0.2 is not experiencing this issue just those of us on 2.9.x. You might provide some of the common elements you are seeing in machines experiencing this issue as well as the common elements in machines not experiencing this issue. Please provide more information to Esri in this thread. Don't treat Esri like the Giant's Fred Snodgrass, a baseball player with a great career, lots of career bests and a great hitter, but is only known for dropping a fly ball during the 1912 World Series. I applaud Esri for the tens of thousands of days I have used ArcGIS without issue, and do not blame them for something slipping through the cracks in a system as complex as theirs. Therefore, I provide them with information about the bug and my system setup. I, too, want results and for ArcGIS Pro to stop crashing so I can do my work. Microsoft hopes that by changing and fixing such components on the inside, that existing software will continue to work well, since they merely call the functions that have been fixed. NET are black box components, developers can't delve into them to see how they do what they do. I think Microsoft just releases them on their own schedule. NET Updates to see if it breaks anything in any software written by said vendors. Esri is having a hard time merely reproducing the issue, so how could they have warned us? I could be wrong, but I don't think Microsoft gives all vendors a chance to preview all of their Windows and.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |