ArcGIS 10.0 and 10.1 Deprecation Plan Released

Mike Hogan tweeted that the Esri deprecation plan for ArcGIS 10.0 and 10.1 is now available. It can be found here. Much of what it contains is not new as Esri has been pretty good about getting information related to 10.x out. Some of the more interesting things (to me) include (comments in parens are mine):

ArcGIS Server 10.0 is the last release with support for 32-bit operating systems. The next release of ArcGIS Server (10.1) will run natively as a 64-bit application, requiring 64-bit operating systems. (I heard about the native 64-bit move at the Esri UC but I didn’t know that included dropping 32-bit. It’s not a big deal for me but I can imagine it’ll be an impact for many.)

ArcGIS Server 10.0 is the last release supporting publishing non-optimized map documents (MXD files). The next major release will only support publishing optimized maps (MSDs) as that is the best practice for map publishing. (There you have it, no more serving from MXDs after 10.0.)

ArcGIS Server 10.1 will be the last planned release for the ArcGIS Server Web ADFs (Application Developer Framework) for both Microsoft .NET and Java. (We had a small “wake” in San Diego for the ADFs. I won’t shed a tear when it’s “official.”)

ArcGIS Server 10.1 will no longer support local connections (DCOM connections) from Web ADF applications. ArcGIS Server 10.1 will be a web services (REST and SOAP) server only. (This is actually pretty major and the document details the impacts. If you have any ADF code doing editing and such, read this!)

There’s a lot of good information in the document, especially pertaining to ArcGIS Server so it’s definitely worth a read.

Advertisements
This entry was posted in arcgis desktop, arcgis server, arcims, esri, gis and tagged , . Bookmark the permalink.

3 Responses to ArcGIS 10.0 and 10.1 Deprecation Plan Released

  1. Pingback: Tweets that mention ArcGIS 10.0 and 10.1 Deprecation Plan Released « geoMusings -- Topsy.com

  2. Jason says:

    Did they go from not running natively at 64 bit to only supporting 64 in a .1 release?

    • Bill Dollins says:

      It looks that way. I wonder if that was the driver behind the DCOM change. 64-bit COM is doable but why bother if you’re going to kill the ADFs anyway?

Comments are closed.