Flowman workflow platform page control -- Ext. Net V1.0

Source: Internet
Author: User

Flowman page control -- Ext. Net V1.0

Most customers who have tried flowman with a positive attitude towards its concise and beautiful interface. In fact, the technicians used a small tool during the development of the interface, at the beginning of this day, we will use four articles to share some of its usage methods with technical enthusiasts.

 

Ext. net, this name may be somewhat unfamiliar, but we should be quite familiar with extjs and coolite. In fact, ext. net, formerly known as coolite, is a Rename of this product after coolite is developed to Version 1.0. Ext. net is based on. net Framework 3.5 supports ASP. net Ajax web control, which is developed based on the cross-browser extjs library and simplifies the development steps, including a wide range of Ajax applications.

 

Ext. NET is open-source. Because Ext. net is based on extjs, so it is inevitable that there will be problems such as extjs control running large and slow, but because of its beautiful interface, it reduces the energy of a lot of artists, you can save a bunch of JS Code and use Ext. net simple configuration to get a very dazzling page effect, so that programmers can focus on the preparation of background code. In addition, ext. Net's Ajax + JSON operations are simple and convenient, so it is a good choice for enterprise applications.

Ext. Net official download: www.coolite.com

Extjs official download: www.extjs.com

Ext. Net's biggest disadvantage: There are many bugs in the development phase.

 

Ext. Net configuration method:

 

1. Download Ext. net from the official website: (the current version is coolite. 0.8.2 , Ext. net1.0 is Beta and is not yet open for download)

Http://www.coolite.com/download/

 

2. Reference in the project

Click reference in the project and add Ext. net. dll and Ext. net. Utilities. dll references through browsing.

 

3. Added toolbox

Add tab Ext. net in the toolbox. Add file: Ext. net. dll.

 

4. Modify the Web. config file and set it as follows:

<? XML version = "1.0"?> <Configuration>

<Configsections>

<Sectiongroup name = "system. Web. Extensions" type = "system. Web. configuration. systemwebextensionssectiongroup, system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 ">

<Sectiongroup name = "scripting" type = "system. Web. configuration. scriptingsectiongroup, system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 ">

<Section name = "scriptresourcehandler" type = "system. Web. configuration. scriptingscriptresourcehandlersection, system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "requirepermission =" false "allowdefinition =" machinetoapplication "/>

<Sectiongroup name = "WebServices" type = "system. Web. configuration. scriptingwebservicessectiongroup, system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 ">

<Section name = "jsonserialization" type = "system. Web. configuration. scriptingjsonserializationsection, system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "requirepermission =" false "allowdefinition =" everywhere "/>

<Section name = "profileservice" type = "system. Web. configuration. scriptingprofileservicesection, system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "requirepermission =" false "allowdefinition =" machinetoapplication "/>

<Section name = "authenticationservice" type = "system. Web. configuration. scriptingauthenticationservicesection, system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "requirepermission =" false "allowdefinition =" machinetoapplication "/>

<Section name = "roleservice" type = "system. Web. configuration. scriptingroleservicesection, system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "requirepermission =" false "allowdefinition =" machinetoapplication "/>

</Sectiongroup>

</Sectiongroup>

</Sectiongroup>

</Configsections>

 

<Appsettings/>

<Connectionstrings/>

<System. Web>

<! --

Set compilation DEBUG = "true" to insert debugging

Symbols into the compiled page. Because this

Affects performance, set this value to true only

During development.

-->

<Compilation DEBUG = "false">

 

<Assemblies>

<Add Assembly = "system. Core, version = 3.5.0 . 0, culture = neutral, publickeytoken = B 77a 5C 561934e089 "/>

<Add Assembly = "system. Data. datasetextensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = B 77a 5C 561934e089 "/>

<Add Assembly = "system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "/>

<Add Assembly = "system. xml. LINQ, version = 3.5.0 . 0, culture = neutral, publickeytoken = B 77a 5C 561934e089 "/>

<Add Assembly = "system. Design, version = 2.0.0 . 0, culture = neutral, publickeytoken = B 03f 5f 7f 11d 50a 3A "/> </Assemblies>

 

</Compilation>

<! --

The <authentication> section enables Configuration

Of the Security Authentication mode used

ASP. NET to identify an incoming user.

-->

<Authentication mode = "Windows"/>

<! --

The <customerrors> section enables Configuration

Of what to do if/when an unhandled error occurs

During the execution of a request. Specifically,

It enables developers to configure HTML error pages

To be displayed in place of a error stack trace.

 

<Customerrors mode = "remoteonly" defaultredirect = "genericerrorpage.htm">

<Error statuscode = "403" Redirect = "noaccess.htm"/>

<Error statuscode = "404" Redirect = "filenotfound.htm"/>

</Customerrors>

-->

 

<Pages>

<Controls>

<Add tagprefix = "asp" namespace = "system. Web. UI" assembly = "system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "/>

<Add tagprefix = "asp" namespace = "system. Web. UI. webcontrols" assembly = "system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "/>

</Controls>

</Pages>

 

<Httphandlers>

<Remove verb = "*" Path = "*. asmx"/>

<Add verb = "*" Path = "*. asmx" Validate = "false" type = "system. Web. Script. Services. scripthandlerfactory, system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "/>

<Add verb = "*" Path = "* _ appservice. axd "Validate =" false "type =" system. web. script. services. scripthandlerfactory, system. web. extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "/>

<Add verb = "Get, head" Path = "scriptresource. axd" type = "system. Web. Handlers. scriptresourcehandler, system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "Validate =" false "/>

</Httphandlers>

<Httpmodules>

<Add name = "scriptmodule" type = "system. Web. Handlers. scriptmodule, system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "/>

<Add name = "directrequestmodule" type = "Ext. net. directrequestmodule, ext. Net"/>

</Httpmodules>

</System. Web>

 

<System. codedom>

<Compilers>

<Compiler language = "C #; CS; CSHARP" extension = ". cs" WarningLevel = "4" type = "Microsoft. CSHARP. csharpcodeprovider, system, version = 2.0.0 . 0, culture = neutral, publickeytoken = B 77a 5C 561934e089 ">

<Provideroption name = "compilerversion" value = "v3.5"/>

<Provideroption name = "warnaserror" value = "false"/>

</Compiler>

</Compilers>

</System. codedom>

<! --

The system. webserver Section is required for running ASP. NET Ajax under Internet

Information Services 7.0. It is not necessary for previous version of IIS.

-->

<System. webserver>

<Validation validateintegratedmodeconfiguration = "false"/>

<Modules>

<Remove name = "scriptmodule"/>

<Add name = "scriptmodule" precondition = "managedhandler" type = "system. Web. Handlers. scriptmodule, system. Web. Extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "/>

</Modules>

<Handlers>

<Remove name = "webservicehandlerfactory-integrated"/>

<Remove name = "scripthandlerfactory"/>

<Remove name = "scripthandlerfactoryappservices"/>

<Remove name = "scriptresource"/>

<Add name = "scripthandlerfactory" verb = "*" Path = "*. asmx "precondition =" integratedmode "type =" system. web. script. services. scripthandlerfactory, system. web. extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "/>

<Add name = "scripthandlerfactoryappservices" verb = "*" Path = "* _ appservice. axd "precondition =" integratedmode "type =" system. web. script. services. scripthandlerfactory, system. web. extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "/>

<Add name = "scriptresource" precondition = "integratedmode" verb = "Get, head" Path = "scriptresource. axd "type =" system. web. handlers. scriptresourcehandler, system. web. extensions, version = 3.5.0 . 0, culture = neutral, publickeytoken = 31bf3856ad364e35 "/>

</Handlers>

</System. webserver>

 

<Runtime>

<Assemblybinding xmlns = "urn: Schemas-Microsoft-com: ASM. V1">

<Dependentassembly>

<Assemblyidentity name = "system. Web. Extensions" publickeytoken = "31bf3856ad364e35"/>

<Bindingredirect oldversion =" 1.0.0 . 0-1.1.0.0 "newversion =" 3.5.0.0 "/>

</Dependentassembly>

<Dependentassembly>

<Assemblyidentity name = "system. Web. Extensions. Design" publickeytoken = "31bf3856ad364e35"/>

<Bindingredirect oldversion =" 1.0.0 . 0-1.1.0.0 "newversion =" 3.5.0.0 "/>

</Dependentassembly>

</Assemblybinding>

</Runtime>

 

</Configuration>

 

5. Add Ext. Net reference to the page

<% @ Register Assembly = "Ext. Net" namespace = "Ext. Net" tagprefix = "Ext" %>

 

6. When using the Ext. Net Control, you must note that you must add the ResourceManager control before adding any control.

<Ext: ResourceManager id = "resourcemanager1" runat = "server">

 

After the configuration is complete, let's prepare for a wonderful Ext. Net journey!

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.