In this topic
- ArcWeb libraries have been removed
- FindPlace task has been removed
- ESRI.ArcGIS.Server.WebControls library has been removed
- ADF and ADF.Connection libraries have been deprecated
- Separate libraries for ArcGIS Server local connections
- Support for 64-bit applications
- Support for coded value domain and subtype descriptions
- Support for standalone tables
- Support for related data
- New Identify control
- New ZoomToScale control
- New GoToLocation control
- New Extent property on Full Extent command
- Preserve Extent or Scale with the Print Task
ArcWeb libraries have been removed
The ESRI.ArcGIS.ADF.ArcWebServices.dll and ESRI.ArcGIS.ADF.Web.DataSources.ArcWebService.dll have been removed from the product. ArcWeb services are no longer available.
The FindPlace task depended solely on ArcWeb services. Since ArcWeb services are no longer available, the FindPlace task has been removed. To emulate FindPlace task capabilities, use the FindAddress task with the ESRI_Places_World geocode service on ArcGIS Online's tasks server.
The ESRI.ArcGIS.Server.WebControls assembly, which represents the architecture of the .NET Web ADF prior to the 9.2 release, has been fully removed at the ArcGIS Server 10 release. This assembly was delivered in the 9.2 and 9.3 for the purposes of easing the migration to the new architecture. The current and latest architecture offers all of the functionality available in the old architecture.
ESRI.ArcGIS.ADF.dll and ESRI.ArcGIS.ADF.Connection.dll have been deprecated and may be removed from the product in a future release. To use ArcObjects functionality in an application add references to the Local libraries, ESRI.ArcGIS.ADF.Local.dll and ESRI.ArcGIS.ADF.Connection.Local.dll. See the section Separate libraries for ArcGIS Server local connections for more information. If ArcObjects functionality is not required and/or you want to create a pure 64-bit application, add references to the Core libraries ESRI.ArcGIS.ADF.Core.dll and ESRI.ArcGIS.ADF.Connection.Core.dll. See the section titled Support for 64-bit applications for more information.
Any components that work with ArcGIS Server over a local connection require ArcObjects Primary Interop Assemblies and COM proxies. ArcObjects is only supported in a 32-bit environment. As a result, components that depend on ArcObjects have been separated into distinct libraries, five of which are new in 10:
- ESRI.ArcGIS.ADF.Local
- ESRI.ArcGIS.ADF.Connection.Local
- ESRI.ArcGIS.ADF.ArcGISServer.Local
- ESRI.ArcGIS.ADF.Web.DataSources.ArcGISServer.Local
- ESRI.ArcGIS.ADF.Web.UI.WebControls.Layout
- ESRI.ArcGIS.ADF.ArcGISServer.Editor (existed before 10)
Support for 64-bit applications
To create an ADF application that supports deployment in a pure 64-bit environment, do not reference assemblies that require ArcObjects (see the previous item). To use classes in the ESRI.ArcGIS.ADF and ESRI.ArcGIS.ADF.Connection libraries, reference the Core libraries, ESRI.ArcGIS.ADF.Core.dll and ESRI.ArcGIS.ADF.Connection.Core.dll.
We now have better support for querying and displaying the description values for domains and subtypes in ArcGIS Server map services.
The Query task can now query based on the code -or- description value stored with domains and subtypes. The Query task configurator in Manager and Visual Studio will allow you to continue to use the code. The Search task only supports inputting the code value.
The Search, Query and MapTips controls now have a ShowCodedValueAsDescription property that determines whether the code or description is displayed. By default, it shows the description. You must use Visual Studio or edit the markup directly to change this – it is not exposed in Manager.
If the domain is standalone, it will display either the code or description. If the domain is part of a subtype, the code is always displayed.
The Query and Search task can query layers or stand alone tables in an ArcGIS Server map service. When querying a stand alone table, it is assumed that there are related feature classes that will become highlighted when the selected results are ‘pushed’ between tables.
Users can now define layer definitions on stand alone tables at either the map resource or task level. (This needs more testing and refinement)
If you query, search or identify a layer that has related stand alone tables, you can access these child records in the Identify Callout and Task Results control.
Use the Identify tool in the Web Mapping Application template or the Search/Query task to query a feature class in an ArcGIS Server map service and return related rows.
- The Identify tool allows you to access related rows in a child table that is one level deep. The parent and child records can be added to the TaskResults panel and highlighted.
- Using a Search or Query task to query a layer or table that has related child tables will display the related rows as additional nodes in the Task Results control. The related rows are fetched on demand when the node is expanded. Unlike the Identify tool, there are no limits on the depth of related data which can be returned.
A new MapIdentify control has been added to the ADF (in ESRI.ArcGIS.ADF.Web.UI.WebControls). Several properties on the MapIdentify control such as tolerance and layers to identify can be set explicitly. The Identify tool in the Web Mapping Application uses the new MapIdentify control. The Identify tool cannot be configured in Manager.
A new ZoomToScale control has been added to the ADF (in ESRI.ArcGIS.ADF.Web.UI.WebControls). The control is included in the Web Mapping Application template. The ZoomToScale control uses the primary map resource to determine how it functions at runtime. If the primary map resource is a cached service, a user can select from a list of cache levels If the primary map resource is dynamic, a user can enter the scale in a text box.
The GoToLocation control has been added to the ADF (in ESRI.ArcGIS.ADF.Web.UI.WebControls). The control is included in the Web Mapping Application template. At runtime the user can enter a location (coordinate) and zoom to or pan to the location. Several options can be modified, such as the label text and zoom factor.
The FullExtent command has a ‘Configuration’ property that takes in the <minx,miny,maxx,maxy> for the extent too zoom to when the command is clicked. By default, the FullExtent command uses the full extent of the primary map resource.
A set of new properties on the Print Task enable the preservation of scale or extent when creating a print layout. The properties can also be modified in Manager. By default map scale is maintained when generating a print layout.