1.从官方网站下载Coolite Toolkit:

http://www.coolite.com/download/

2.修改Web.config文件

<?xml version="1.0"?>
<configuration>
 <configSections>
    <section name="coolite" type="Coolite.Ext.Web.GlobalConfig" requirePermission="false"/>
  <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/>-->

  <!--<connectionStrings/>-->
  <connectionStrings>
    <clear/>
    <add name="DB_Connect" connectionString="Password=;Persist Security Info=True;User ID=sa;Initial Catalog=HRDB;Data Source=."/>
  </connectionStrings>
  <coolite theme="Default"/>
 <system.web>
  <!--
            设置 compilation debug="true" 可将调试符号插入
            已编译的页面中。但由于这会
            影响性能,因此只在开发过程中将此值
            设置为 true。
        -->
  <compilation debug="true">
   <assemblies>
    <add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
    <add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
    <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=B77A5C561934E089"/>
   </assemblies>
  </compilation>
  <!--
            通过 <authentication> 节可以配置 ASP.NET 用来
            识别进入用户的
            安全身份验证模式。
        -->
  <authentication mode="Windows"/>
  <!--
            如果在执行请求的过程中出现未处理的错误,
            则通过 <customErrors> 节可以配置相应的处理步骤。具体说来,
            开发人员通过该节可以配置
            要显示的 html 错误页
            以代替错误堆栈跟踪。

        <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 path="*/coolite.axd" verb="*" type="Coolite.Ext.Web.ResourceManager" validate="false"/>
   <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="AjaxRequestModule" type="Coolite.Ext.Web.AjaxRequestModule, Coolite.Ext.Web"/>
   <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
  </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=b77a5c561934e089">
    <providerOption name="CompilerVersion" value="v3.5"/>
    <providerOption name="WarnAsError" value="false"/>
   </compiler>
  </compilers>
 </system.codedom>
 <!--
        在 Internet 信息服务 7.0 下运行 ASP.NET AJAX 需要 system.webServer
        节。对早期版本的 IIS 来说则不需要此节。
    -->
 <system.webServer>
  <validation validateIntegratedModeConfiguration="false"/>
  <modules>
   <remove name="ScriptModule"/>
   <add name="AjaxRequestModule" preCondition="managedHandler" type="Coolite.Ext.Web.AjaxRequestModule, Coolite.Ext.Web"/>
   <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="AjaxRequestHandler" verb="*" path="*/coolite.axd" preCondition="integratedMode" type="Coolite.Ext.Web.ResourceManager"/>
   <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>

3.项目中引用

  在项目点击引用,通过浏览增加Coolite.Ext.Web.dll、Coolite.Utilities.dll引用

4.工具箱增加

  在工具箱增加Coolite ToolKIT。增加文件:Coolite.Ext.Web.dll

 

以下是官方配置:

Product      : Coolite Toolkit Community Edition
Version      : 0.8.2
Last Updated : 2009-12-21


--------------------------------------------------------------------------
                             CONTENTS
--------------------------------------------------------------------------

I.    ADD TO VISUAL STUDIO TOOLBOX INSTRUCTIONS
II.   SAMPLE WEB.CONFIG
III.  CREDITS

 
--------------------------------------------------------------------------
            I. ADD TO VISUAL STUDIO TOOLBOX INSTRUCTIONS
--------------------------------------------------------------------------

If you ran the automatic installer (.msi), the Coolite Toolkit 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 "Coolite Toolkit" Tab, by...
    a. Right-Click in the ToolBox area.
    b. Select "Add Tab".
    c. Enter "Coolite Toolkit".

 6.  Inside the "Coolite Toolkit" tab, Right-Click and select
     "Choose Items...".

 7.  Under the ".NET Framework Components" Tab select the "Browse"
     button.

 8.  Navigate to and select the Coolite.Ext.Web.dll file, choose open.

          NOTE: If the automatic installer has been run previously, the
                Coolite.Ext.Web.dll can typically be found in the
                following location:

                C:\Program Files\Coolite\Coolite Toolkit Community v0.8.2\

 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 "Coolite.Ext.Web"

 10. Click "OK". The icons should be added to your ToolBox. You should
     now be able to drag/drop a Coolite component onto your WebForm.

 11. Enjoy.


--------------------------------------------------------------------------
                        III. SAMPLE WEB.CONFIG
--------------------------------------------------------------------------

<?xml version="1.0"?>
<configuration>
 <configSections>
  <section name="coolite" type="Coolite.Ext.Web.GlobalConfig" requirePermission="false" />
 </configSections>

 <!-- 
    COOLITE GLOBAL CONFIGURATION PROPERTIES

    ajaxEventUrl : string
  The url to request for all AjaxEvents.
        Default is "".

 ajaxMethodNamespace : string
  Specifies a custom namespace prefix to use for the AjaxMethods. Example "CompanyX".
  Default is "Coolite.AjaxMethods".

 ajaxMethodProxy : ClientProxy
  Specifies whether server-side Methods marked with the [AjaxMethod] attribute will output configuration script to the client.
  If false, the AjaxMethods 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 AjaxEvent.
  The Default value is to Exclude the ViewState from the Response.
  Default is 'Default'. Options include [Default|Exclude|Include]

 cleanResourceUrl : boolean
  The Coolite controls can clean up the autogenerate WebResource Url so they look presentable.       
  Default is 'true'. Options include [true|false]

 clientInitAjaxMethods : boolean
  Specifies whether server-side Methods marked with the [AjaxMethod] attribute will output configuration script to the client.
  If false, the AjaxMethods 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 coolite 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 coolite 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 ~/Coolite/ 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]
 -->

 <coolite 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="*/coolite.axd" verb="*" type="Coolite.Ext.Web.ResourceManager" validate="false" />
  </httpHandlers>
  <httpModules>
   <add name="AjaxRequestModule" type="Coolite.Ext.Web.AjaxRequestModule, Coolite.Ext.Web" />
  </httpModules>
 </system.web>

 <!--
  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>
   <add name="AjaxRequestModule" preCondition="managedHandler" type="Coolite.Ext.Web.AjaxRequestModule, Coolite.Ext.Web" />
  </modules>
  <handlers>
   <add name="AjaxRequestHandler" verb="*" path="*/coolite.axd" preCondition="integratedMode" type="Coolite.Ext.Web.ResourceManager"/>
  </handlers>
 </system.webServer>
</configuration>


--------------------------------------------------------------------------
                             IV. CREDITS
--------------------------------------------------------------------------

1.  FamFamFam Icons provided by Mark James
    http://www.famfamfam.com/lab/icons/silk/

    See \Build\Resources\Coolite\Licenses\FamFamFam.txt for more information.

2.  Json.NET provided by James Newton-King
    http://www.codeplex.com/json/

    See \Build\Resources\Coolite\Licenses\Newtonsoft.Json.txt

3.  Ext JS - JavaScript Library provided by ExtJS LLC
    http://www.extjs.com/   

    See \Build\Resources\Coolite\Licenses\ExtJS.txt


--------------------------------------------------------------------------

--------------------------------------------------------------------------

        Copyright 2006-2009 Coolite Inc., All rights reserved.

                             Coolite Inc.
                        208, 10113 104 Street
                   Edmonton, Alberta, Canada T5J 1A1
                           +1(888)775-5888

风云阁资源网 Design By www.bgabc.com
广告合作:本站广告合作请联系QQ:858582 申请时备注:广告合作(否则不回)
免责声明:本站资源来自互联网收集,仅供用于学习和交流,请遵循相关法律法规,本站一切资源不代表本站立场,如有侵权、后门、不妥请联系本站删除!
风云阁资源网 Design By www.bgabc.com

《魔兽世界》大逃杀!60人新游玩模式《强袭风暴》3月21日上线

暴雪近日发布了《魔兽世界》10.2.6 更新内容,新游玩模式《强袭风暴》即将于3月21 日在亚服上线,届时玩家将前往阿拉希高地展开一场 60 人大逃杀对战。

艾泽拉斯的冒险者已经征服了艾泽拉斯的大地及遥远的彼岸。他们在对抗世界上最致命的敌人时展现出过人的手腕,并且成功阻止终结宇宙等级的威胁。当他们在为即将于《魔兽世界》资料片《地心之战》中来袭的萨拉塔斯势力做战斗准备时,他们还需要在熟悉的阿拉希高地面对一个全新的敌人──那就是彼此。在《巨龙崛起》10.2.6 更新的《强袭风暴》中,玩家将会进入一个全新的海盗主题大逃杀式限时活动,其中包含极高的风险和史诗级的奖励。

《强袭风暴》不是普通的战场,作为一个独立于主游戏之外的活动,玩家可以用大逃杀的风格来体验《魔兽世界》,不分职业、不分装备(除了你在赛局中捡到的),光是技巧和战略的强弱之分就能决定出谁才是能坚持到最后的赢家。本次活动将会开放单人和双人模式,玩家在加入海盗主题的预赛大厅区域前,可以从强袭风暴角色画面新增好友。游玩游戏将可以累计名望轨迹,《巨龙崛起》和《魔兽世界:巫妖王之怒 经典版》的玩家都可以获得奖励。