Product : Ext.NET Professional Edition
Version : 1.0.0
Last Updated : 2010-01-22
--------------------------------------------------------------------------
CONTENTS
--------------------------------------------------------------------------
I. ADD TO VISUAL STUDIO TOOLBOX INSTRUCTIONS
II. Version 1.0.0 BREAKING CHANGES
III. SAMPLE WEB.CONFIG
IV. CREDITS
--------------------------------------------------------------------------
I. ADD TO VISUAL STUDIO TOOLBOX INSTRUCTIONS
--------------------------------------------------------------------------
If you ran the automatic installer (.msi), the Ext.NET component
icons should be automatically installed to your Visual Studio 2005/2008
Toolbox.
The .msi installer does not automatically install the Toolbox icons to the
Visual Web Developer 2005/2008 Toolbox. They must be added manually.
The following steps are required to manually install the controls into
your Visual Studio or Visual Web Developer Express Toolbox.
1. Open Visual Studio or Visual Web Developer Express.
2. Open an existing web site or create a new web site project.
3. Open or create a new .aspx page.
4. Open the ToolBox panel, typically located on the left side in a
fly-out panel (Ctrl + Alt + x).
5. Create a new "Ext.NET" Tab, by...
a. Right-Click in the ToolBox area.
b. Select "Add Tab".
c. Enter "Ext.NET".
6. Inside the "Ext.NET" tab, Right-Click and select
"Choose Items...".
7. Under the ".NET Framework Components" Tab select the "Browse"
button.
8. Navigate to and select the Ext.Net.dll file, choose open.
NOTE: If the automatic installer has been run previously, the
Ext.Net.dll can typically be found in the
following location:
C:\Program Files\Ext.NET\Ext.NET Professional v1.0.0\
9. The component items should now be added to the list and
pre-checked. You can confirm by sorting the list by "Namespace"
and scrolling to "Ext.Net"
10. Click "OK". The icons should be added to your ToolBox. You should
now be able to drag/drop a Ext.NET component onto your WebForm.
11. Enjoy.
--------------------------------------------------------------------------
II. Version 1.0.0 BREAKING CHANGES
--------------------------------------------------------------------------
Version 0.8.0 BREAKING CHANGES
See CHANGELOG.txt
--------------------------------------------------------------------------
III. SAMPLE WEB.CONFIG
--------------------------------------------------------------------------
<?xml version="1.0"?>
<configuration>
<configSections>
<section name="extnet" type="Ext.Net.GlobalConfig" requirePermission="false" />
</configSections>
<!--
EXT.NET GLOBAL CONFIGURATION PROPERTIES
directEventUrl : string
The url to request for all DirectEvents.
Default is "".
directMethodNamespace : string
Specifies a custom namespace prefix to use for the DirectMethods. Example "CompanyX".
Example with default value:
Ext.net.DirectMethods.doSomething();
Example with a custom value:
CompanyX.doSomething();
directMethodProxy : ClientProxy
Specifies whether server-side Methods marked with the [DirectMethod] attribute will output configuration script to the client.
If false, the DirectMethods can still be called, but the Method proxies are not automatically generated.
Specifies ajax method proxies creation. The Default value is to Create the proxy for each ajax method.
Default is 'Default'. Options include [Default|Include|Ignore]
ajaxViewStateMode : ViewStateMode
Specifies whether the ViewState should be returned and updated on the client during an DirectEvent.
The Default value is to Exclude the ViewState from the Response.
Default is 'Default'. Options include [Default|Exclude|Include]
cleanResourceUrl : boolean
The Ext.NET controls can clean up the autogenerate WebResource Url so they look presentable.
Default is 'true'. Options include [true|false]
clientInitDirectMethods : boolean
Specifies whether server-side Methods marked with the [DirectMethod] attribute will output configuration script to the client.
If false, the DirectMethods can still be called, but the Method proxies are not automatically generated.
Default is 'false'. Options include [true|false]
idMode : IDMode
Specifies how the Client ID for the control should be sent to the client. Similar in functionality to ASP.NET 4.0 ClientIDMode property.
The Default value is Legacy.
Default is 'Legacy'. Options include [Legacy|Inherit|Static|Ignore|Explicit]
initScriptMode : InitScriptMode
Specifies how the initialization JavaScript code will be rendered in the client.
Inline will place the Ext.onReady block within the Page <head>.
Linked will create a link to the init block and download in a separate request.
The Default value is Inline.
Default is 'Inline'. Options include [Inline|Linked]
locale : string
Specifies language of the ExtJS resources to use.
Default is to return the System.Threading.Thread.CurrentThread.CurrentUICulture if available.
gzip : boolean
Whether to automatically render scripts with gzip compression.
Only works when renderScripts="Embedded" and/or renderStyles="Embedded".
Default is true. Options include [true|false]
scriptAdapter : ScriptAdapter
Gets or Sets the current script Adapter.
Default is "Ext". Options include [Ext|jQuery|Prototype|YUI]
removeViewState : boolean
True to completely remove the __VIEWSTATE field from the client.
If true, the VIEWSTATE is not sent to, nor returned from the client.
Default is "false". Options include [true|false]
renderScripts : ResourceLocationType
Whether to have the Ext.NET controls output the required JavaScript includes or not.
Gives developer option of manually including required <script> files.
Default is Embedded. Options include [Embedded|File|None]
renderStyles : ResourceLocationType
Whether to have the Ext.NET controls output the required StyleSheet includes or not.
Gives developer option of manually including required <link> or <style> files.
Default is Embedded. Options include [Embedded|File|None]
resourcePath : string
Gets the prefix of the Url path to the base ~/extnet/ folder containing the resources files for this project.
The path can be Absolute or Relative.
scriptMode : ScriptMode
Whether to include the Release (condensed) or Debug (with inline documentation) Ext JavaScript files.
Default is "Release". Options include [Release|Debug]
sourceFormatting : boolean
Specifies whether the scripts rendered to the page should be formatted. 'True' = formatting, 'False' = minified/compressed.
Default is 'false'. Options include [true|false]
stateProvider : StateProvider
Gets or Sets the current script Adapter.
Default is 'PostBack'. Options include [PostBack|Cookie|None]
theme : Theme
Which embedded theme to use.
Default is "Default". Options include [Default|Gray|Slate]
quickTips : boolean
Specifies whether to render the QuickTips. Provides attractive and customizable tooltips for any element.
Default is 'true'. Options include [true|false]
-->
<extnet theme="Default" />
<!--
The following system.web section is only requited for running ASP.NET AJAX under Internet
Information Services 6.0 (or earlier). This section is not necessary for IIS 7.0 or later.
-->
<system.web>
<httpHandlers>
<add path="*/ext.axd" verb="*" type="Ext.Net.ResourceHa
Ext.NET.zip （6个子文件） 
Ext.NET 
Ext.Net.dll 14.92MB
README.txt 10KB WhatsNew_1.0.txt 32KB Newtonsoft.Json.dll 288KB CHANGELOG.txt 9KB Ext.Net.Utilities.dll 33KB资源评论
2就是不3不42014-03-19再次提醒，是dll文件，对和我一样初学者好像没什么用
softzhangpeiying2012-09-19不错，现在也不能期望太多，能有点用就很不错了。
jinemirates2012-03-22还以为是什么程序，下下来打开一开，原来是dll文件，唉，再此为广大的下载同胞们提个醒，是dll文件哦
