Getting started with the Web ADF

Getting started with the Web ADF

// Getting started with Web ADF

 

The Web ADF offers a number of ways to get started creating web applications. to create Web applications without writing code, use the Manager Web application. for additional information, see the section titled developing Web applications with Manager or access the help system within the Manager application. manager creates a predefined (pre-defined) web application based on the web mapping application template, ready for deployment. although manager provides a number of options to customize your web application, you may choose to extend it further. for additional information on customizing the Web Application Generated by manager, see the section titled customizing the web mapping application.

Web ADF provides multiple ways to create a web applicationProgram. With Web application managers, we do not need to writeCodeYou can create an application. For other messages, see the following connection title: developing Web applications with Manager or use the help system in the management program. Manager creates a predefined program based on the Web Map application template. Although the manager provides many options for users to customize their own web applications. However, you can further customize your own applications. For more information about customizing Web Applications created by the manager, see the following connection title: customizing the web mapping application.

 

While generating web applications via Manager offers a quick and easy solution to create and deploy a web ADF application, the Web ADF is designed as a full featured development environment with a set of controls, frameworks and APIs to create custom web solutions. since the Web ADF is built on Microsoft ASP. net, developers shoshould be proficient in the techniques and technologies of ASP. net web development. web application development can take alternative forms (form ). client-side development leverages (power, impact) browser technologies (e.g. HTML, JavaScript, CSS) to provide an interactive interface and off load application logic for processing on the client.

Using a quick and easy method provided by the Manager, we can create and deploy the Web ADF application, however, Web ADF is a development environment that creates custom web solutions based on a series of components, frameworks, and APFs. Because Web ADF is built on Microsoft's ASP. NET, developers may benefit from advances in ASP. NET network development technology and technology. The development of Web applications can take various forms. The development of client technology affects browser technology to provide an interactive interface, which can reduce the logic burden of applications by processing the client.

However, browser capabilities are often limited: security restrictions hinder (obstruction, obstruction) Resource Access, remote services can be utilized via HTTP only, and the scripting (SCRIPT) environment provides a somewhat rudimentary (basic) (sometimes unstable) platform for execution logic. server-side development involves packaging application logic in the server or web-tier with access to internal proprietary services and resources. the full-featured (full function), stable (stable), true object-oriented development environment of. net Framework is accessible and extensible. ASP. NET Web controls encapsulate (Compressed) business logic on the server or web-tier and provide presentation (report) content to the client browser. some client-side support content is provided (e.g. javascript) to enable client-side interactivity with the server, but a vast majority of the application logic resides (exists) on the server. the 9.3 web ADF combines both in a hybrid approach to web development by including both client and server logic to balance performance and functionality. the Web ADF provided des server-side Web controls with a Scriptable interface so they can be utilized directly via Javascript in a browser. the ASP. net Ajax JavaScript Library provides a foundation for our web ADF JavaScript library to manage client events and synchronize state with server-side Web controls.

Despite this: the browser's capabilities are still limited, and security settings impede resource access. remote services can only be accessed through HTTP, the script environment is a basic platform for logical execution. The development of servers involves packaging application logic and web-level Internet attribute services and resource access. This full-featured, stable, and object-oriented. NET development environment is easily accessible and scalable. ASP. NET network components compress the business logic on the server or the web layer, and provide the client report content to the client browser. Some client-supported content is submitted for interaction with the server. However, most applications are logically stored on the server. The Web ADF contains a script interface in the server components, so they can be directly exploited through scripts in the browser. The Ajax script class library of ASP. NET provides a function for our web ADF script class library to manage client events and synchronize network controls on the server.

 

As an ADF developer, you need to be familiar with a set of web technologies to be able to take full advantage of web ADF components in a custom ASP. NET web application. These technologies include:

As an ADF developer, you need to be familiar with a series of web technologies so that you can fully develop custom ASP. NET network applications using the Web ADF components. These technologies include:

• C # Or VB. NET in ASP. NET
  • Event handling
  • Page Lifecycle
  • Custom Web controls
• Ajax In ASP. NET
  • ASP. NET callback Pattern
  • ASP. NET Ajax partial PostBack Pattern
  • ASP. NET Ajax Web controls (scriptmanager, updatepanel)
  • ASP. NET Ajax Javascript Library
• Html
• Javascript

You'll also need to be familiar with IIS, the platform on which you will deploy your web applications. topics related to enhancing performance, managing scalability, maintaining state, and monitoring ASP. net worker process operations will benefit you when deploying a custom solution.

You also need to be familiar with IIS, which is a platform where you can deploy your web applications. Enhancing your performance, maintaining your status, and monitoring the operations of ASP. Net staff can benefit you from deploying a custom solution.

As an ASP. NET Web Developer using web ADF components, application requirements combined with your skill level will dictate (required and required) How functionality will be added \ integrated within a web application. in general, functionality is added to Web applications or components to handle user actions, process inputs and generate results. how functionality is packaged for use in a web application depends on whether you are a page or server control developer.

As a Web Developer using the Web ADF component, the requirements of the application and your own technical level determine how the function is added or integrated into a web application. Generally, the function added to a web application or component is used to process user operations, input, and results. How a function is encapsulated and applied to a web application depends on whether you are a package or a developer of a server-side control.

 

 

Page developers add functionality to a Web page using Web controls, handling events on controls or the page, wiring up custom events, adding logic for custom actions to a code file, or packaging related content into user controls. business logic is designed for a specific web application and the developer knows explicitly what the application contains.

Web developers use Web controls to add functions to pages, process events on controls or pages, send custom events, and add logical events to code files for user actions, or encapsulate the relevant content to the user control. The business logic is designed for special web applications, and developers are very clear about what the application contains.

 

Server Control developers extend or create custom composite (hybrid, comprehensive) Web controls designed to encapsulate (Compressed) business logic in a distributable component.

Server developers can expand or create a custom Hybrid Web component,

creating custom Web controls means understanding how to construct a control interface programmatically and leverage (power, impact) control lifecycle with business logic as it operates within a page. the custom web control may be dependent on another control but generally it cannot depend on other page code, controls or content. as a result, Server Control developers must include logic to check for the availability of a component. for example, the page developer knows if a scriptmanager is present within a page, thus he can work with the control reference in the page. server Control developers may not know if the web control they are creating is being utilized (used) in a page with a scriptmanager.

As a result, logic within the custom web control must check for the presence of a scriptmanager and possibly handle situations where one is not available. while creating custom Web controls is more flexible than adding functionality to a page, implementation is more complex. in some cases, an ASP. net web developer will operate as both a page and Server Control developer to take advantage both patterns when creating a custom web solution

Creating a custom web control means understanding how to create a control interface and use commercial logic to affect the lifecycle of the control, just as they operate on the page. A custom web control may depend on another control, but generally, it does not depend on the code, components, or content of another page. Therefore, server-side control development must have certain logic to check the availability of components. For example, if a Web page developer knows that a page contains a script manager, then he can use the reference of these controls on the page. Developers on the server may not know whether the web control they developed will be used by the script manager on the page. Therefore, the control must logically check the possibility of the script manager and handle the possibility of creating a custom control when it does not exist, which is more complex than adding a function to the page, however, her implementation is more complicated. In some cases, an ASP. when creating a custom network solution, the net network developer must assume the dual role of the page and server-side developer to take advantage of the two types.

 

Getting started as a page developer

Getting started with a page developer

Most ASP. NET developers will use Visual Studio 2005 \ 2008 to create custom web applications with Web ADF controls and components. to get started as a page developer, you can open a Web Application Generated by manager, use the web mapping application template integrated with Visual Studio, or create a custom web application from scratch. you may also choose to modify an existing web application by adding web ADF controls or components. A set of tutorials start with the template and progress through more complex topics, such as custom tool implementation and data source specific interaction. the Web ADF provided des a set of out of the box Web controls on which you may choose to handle events. adding custom functionality may involve adding a custom toolbar item that uses Web ADF core classes, using the task framework to display results, creating a Custom User control that contain web ADF controls, or leveraging the Web ADF JavaScript library to take advantage of browser capabilities.

Most ASP. NET developers use vs2005 or 2008 to develop network applications that use web ADF controls or component technologies. As a page developer, you can open an application created with a manager, use the network map application template integrated into vs, or create a custom application. You can also add a web ADF control or component to redefine an existing web application. Many beginners start learning through templates and make progress through complicated topics. For example, the implementation of custom tools and the interaction of specific data sources. WAF contains a series of external components that you can choose to handle events. The function of adding a user may be related to some events, for example, adding a user tool item using the core class of Web ADF and displaying the result using the result architecture; create a user-defined component that contains the Web ADF control or use the Web ADF JavaScript class library to use the browser's functions.

 

Getting started as a server control developer

Getting started with server-side control developers

Server Control developers will either extend an existing web ADF control to add or modify functionality or create a custom composite Web control that contains web ADF controls. this includes des leveraging the Web ADF task framework to extend out-of-the-box web ADF tasks or create new custom Web tasks (Web controls) that can be integrated with Visual Studio and manager. another common situation may involve packaging custom web ADF controls and content in a single composite Web Control for deployment in a portal (e.g. sharePoint), multiview, or template. this process will usually start by creating a custom class library project in Visual Studio and implementing the appropriate interfaces or extending the appropriate classes to generate a custom web control for the desired deployment environment.

Server developers can either extend an existing web ADF control to add it, or redefine the control function, or create a custom control that contains a Hybrid Web ADF component. She includes extending external web ADF tasks by affecting the Web ADF task architecture, or creating a new custom network component that can be integrated into Vs and manager. Another common situation may be the packaging of custom web ADF components and the ability to accommodate a small component. These operations usually start by creating a user class library project in Vs, so that the appropriate interfaces can be implemented or the appropriate classes can be extended to generate a custom network component, to meet the specific requirements of the deployment environment.

 

 

Getting started with data sources in the Web ADF

In either case, business logic in a page or control may require working with one or more data sources at the same time. it is important to understand the relationship between Web ADF components and APIs which extends lidate (enhanced, is ** combined) and use different data sources using a common public methodology. from a data source perspective (perspective, viewpoint), the web ADF provides custom Web controls to display and interact with map, geocode, and geoprocessing data from multiple data sources. this capability is based on a common data source API (common API for short) designed so that web ADF controls can interact with different data sources in the same way. the following development paths are available, increasing in complexity and functionality from path I to IV.

 

In any case, the business logic of the page or control requires the same or multiple data sources to work at the same time. Understanding the relationship between the Web ADF component and APIS is very important. She uses a common method to associate and use different data sources. From the perspective of data sources, Web ADF provides custom Web controls to display maps, interact with maps, and encode and process data from multiple data sources. This capability is built on common data source interfaces, so Web controls can interact with a variety of different data sources in the same way. The following development routes are optional. From route I to Route IV, the development complexity and functions are being enhanced.

 

in general, the best practice is to start with the simplest path available and select a more complex path only when necessary. selecting a more complex path depends on the functionality you need in your application. developer paths I, II, and III are specific to the Web ADF. if you can accomplish the task you need using the out-of-the-box Web controls, use path I. if you wowould like to customize the Web ADF to work with all data source types by using generic functionalities in the common API, use path II. if you want to customize the Web ADF to work with a specific data source implementation of common API functionality, use path III. see the section titled working with the common data source API for more information.

In general, the final practice method is to start from the simplest and select a complicated one only when needed. Select a complex route application to your application based on the features you need. The development routes I, II, and III all point to the Web ADF. If you can use external controls to complete the work you need, you can select the first development path. If you want to customize the Web ADF and call a public function API to use all types of data sources in your work, select the Development Route II. If you want to define a web ADF so that it can work with a specified data source to implement functions in the common API, please use the development path III. View more messages by using the common data source API.

 

To utilize functionality associated with a specific data source (such as An ArcGIS Server object or an ArcIMS Service), a data source specific API may be provided. this option is associated with developer path IV and offers the most functionality since you are working directly with the data source's API. note that most APIs can be used independent of (independent of) the Web ADF controls and common data source API. A set of data source specific components are installed with the Web ADF to support ArcGIS Server and ArcIMS. both data sources are discussed below:

To use the function of associating with a specific data source, a specific API interface of the data source should be implemented. These options are all associated with the developer path IV and provide the most features, because you need to work directly with the data source API. Note that all API interfaces are called independently of the Web ADF control and universal data source APIs.

A series of specific data source components are installed with the Web ADF framework to support ArcGIS and ArcIMS services. Both data sources will be discussed later.

 

 

ArcGIS Server data sources are supported by two APIs: ArcObjects and soap. in the Web ADF, both ArcGIS Server local and Internet data sources are built on the soap API, however local data sources also offer access to ArcObjects API. see the section on ArcGIS Server implementation for more details. since the soap and ArcObjects APIs can be used apart from the Web ADF, two separate and distinct sections discuss their capabilities. working with the ArcGIS Server soap API discusses the implementation and use of standard soap based proxies and value objects for stateless communication with ArcGIS Server services. working with the ArcObjects API discusses programming techniques and capabilities of working with both coarse and fine-grained ArcObjects remotely via ArcGIS Server. arcGIS Server also provides the ability to customize and extend functionality on the server. in the ArcGIS Server ArcObjects API discussion, see the section titled extending ArcGIS Server for additional details.

The ArcGIS Server data source is supported by two APIs: arcobject and soap. In the Web ADF framework, both the local ArcGIS Server and Internet data sources are built on the soap API. However, the local data source still provides the arcobject access method, for more information, see ArcGIS Server implementation.

Because the soap and arcobject APIs can be used outside the Web ADF, two independent and unique options are used to discuss their capabilities. Working with the ArcGIS Server soap API discusses implementation and use of standard soap based on proxies and value objects. The working with the ArcObjects API discusses coding technology and the ability to remotely work with arcobjecgs objects that are both rough and confidential through ArcGIS Server. ArcGIS Server also provides the ability to expand and customize on the server. For the discussion of ArcGIS Server arcobject API, please refer to the following connection extending ArcGIS Server for more details.

 

ArcIMS data sources are supported by the pure (full). Net ArcIMS API. See the section titled working with the ArcIMS API for more details.

The ArcIMS data source is fully supported by the ArcIMS API under. net. View the working with the ArcIMS API to obtain more detailed information.