![]() We hope that sharing this information helps you prepare to update to ArcGIS Pro 3.0 when it is released in June. Because of this, consider coordinating your update to ArcGIS Pro 3.0 for groups of users that work together on projects.įor additional details to consider before updating to ArcGIS Pro 3.0, see Migration from ArcGIS Pro 2.x to 3.0. In summary, while packaging allows ArcGIS Pro 3.0 users to share projects with 2.x users, collaboration will not be as seamless as when everybody is working within the same major version. If you’re looking for extra insurance, before working with your current projects in ArcGIS Pro 3.0, use Save As to save a copy of your 2.x project as a backup before saving it in 3.0. Layer packages, map packages and project packages will contain both 2.x and 3.x content. If you save the project and for whatever reason find that you need a 2.x version, create a project package. However, just because 3.0 documents cannot be opened directly in earlier versions, it is still possible to access them in 2.x if needed. ![]() After updating to ArcGIS Pro 3.0, when you first save a project created in an earlier version, you will receive the following information message.īefore saving a project created in a previous version of ArcGIS Pro, you will be presented with this warning Of course, any 2.9 functionality won’t be present in 2.6, but the document can be used between both versions with no issues.Īs stated previously, projects created or saved in ArcGIS Pro 3.0 cannot be opened directly in ArcGIS Pro 2.x. A user can work on a project in ArcGIS Pro 2.9 and share that project with a user who can open it in ArcGIS Pro 2.6. Within a major release – that is, from one minor release to another minor release – project files (.aprxs) and other Pro document files such as layer files, map files, and so on, are forward and backward compatible. A major release offers the opportunity to make these necessary API changes. With the decision to move to a major release, we were able to take the opportunity to implement functional, performance, and quality improvements that were otherwise not possible while maintaining compatibility with other minor versions of ArcGIS Pro.įinally, we strive to deliver the best public API possible for third-party developers and we need to clean house every once in a while to remove classes and functions that we’ve replaced with something better in the ArcGIS Pro SDK. NET 6 moving forward, it is necessary to stay at the forefront of the software development community. Additionally, with certain third-party components only updating controls to. NET Core) is Microsoft’s latest version which positions Esri and other ArcGIS Pro developers well for future development and enhancements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |