开发环境:VS2008、SQL Server2005、Coolite Toolkit

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
                           www.coolite.com
                         support@coolite.com

转载于:https://www.cnblogs.com/sen_shan/archive/2010/03/13/1684984.html

管理软件开发历程之一Coolite配置相关推荐

  1. 文献管理软件Zotero配置及使用

    文献管理软件-Zotero常用插件安装及配置使用 一.Zotero安装与同步盘配置 1.下载Zotero并安装 2.配置Zotero (1)配置同步盘(以onedrive为例)--如果不配置同步盘,这 ...

  2. 如何快速配置OA、CRM、ERP等管理软件

    当代企业的信息化建设不外乎两个方向,第一是电子商务网站,是企业开向互联网的一扇窗户:其次就是管理信息系统,它是企业内部信息的组织管理者.电子商务的发展速度和规模是惊人的,似乎一夜之间,各行各业的许多企 ...

  3. 新手如何安装及配置VMware Workstation虚拟机及Xshell远程管理软件

    新手如何安装及配置虚拟机及远程管理软件     VMware Workstation Pro & Xshell 下载并安装VMware Workstation Pro及Xshell. 访问mi ...

  4. 当前国内有哪些公司是做OKR管理软件做的比较好的?

    既然你诚心诚意地发问了,那我当然是要强烈推荐--日事清. 一.为什么要用专业的OKR管理工具? 传统的OKR执行以表格为主要辅助工具,其优点是成本低廉.制作方便.通常是将OKR拆分成公司.团队.个人三 ...

  5. 挑选管理软件应注意的几个问题

    随着信息技术的发展,在企业管理软件市场上,各种管理软件如雨后春笋般冒出来.现在的企业管理软件,已经涉及到了企业的各个部门,有财务管理软件.ERP.CRM等等管理软件,这些管理软件能大大提高企业的办公效 ...

  6. 组策略管理——软件限制策略(5)

    组策略管理--软件限制策略(5) 标签:安全 系统 管理 软件限制策略 组策略 原创作品,允许转载,转载时请务必以超链接形式标明文章 原始出处 .作者信息和本声明.否则将追究法律责任.http://m ...

  7. 管理软件预警通知(Notification)功能的实现案例分析

    预警通知的功能对于管理软件比较常见.比如,开发部填写购买10台电脑的采购申请单,需要通知经理和财务经理审批:又如供应商把10台电脑送到公司,货物经过仓库部门入库,仓库需要通知申请购买的部门来领取电脑. ...

  8. 如何在 Linux 上安装服务器管理软件 Cockpit

    如何在 Linux 上安装服务器管理软件 Cockpit Cockpit 是一个自由开源的服务器管理软件,它使得我们可以通过它好看的 web 前端界面轻松地管理我们的 GNU/Linux 服务器.Co ...

  9. Linux系统上怎么安装服务器管理软件Cockpit?

    Cockpit 是什么?Cockpit 是一个自由开源的服务器管理软件,使得我们可以通过它好看的 Web 前端界面轻松地管理我们的 GNU/Linux 服务器,非常轻量级,Web 界面也非常简单易用. ...

最新文章

  1. 竞拍AI教父Hinton
  2. 图例放在图的外面_Qt编写自定义控件41-自定义环形图
  3. [开源]quakeIII(雷神之锤3)源码
  4. Flask-SocketIO传输二进制单元测试的Bug和修改
  5. [黑客入门全程图解].吴自容,武新华.等编著.文字版,精确还原
  6. Python新书上市,强烈推荐!《Python网络数据爬取及分析从入门到精通(爬取篇)》导读
  7. 千锋前端-React全家桶_React项目实战全球新闻发布管理系统-db.json文件数据
  8. 二清资金监管户账务处理实例
  9. 【matlab】matlab相关系数计算公式(Pearson和Spearman,以及Kendall Rank)
  10. mysql存储指纹,mysql - ZKTeco 4500指纹验证 - 堆栈内存溢出
  11. Nature子刊:灵活的语音皮质编码可增强与任务相关的声学信息的神经处理
  12. python画车辆轨迹图_如何利用 Python 绘制酷炫的 车辆轨迹 — 速度时空图?三维数据用二维图像呈现...
  13. 本周白银市场再刮超级旋风
  14. 员工每月工资数据集可视化分析
  15. c/c++ sprintf sprintf_s
  16. EMD方法基本基本知识
  17. gunicorn的命令参数解释
  18. python输出图片到word_python将文本转换成图片输出的方法
  19. 中国计算机学会举办首届未来计算机教育峰会
  20. 爬取链家二手挂单房屋 - 匹配百度地图API坐标 - python出地图【2】(end) echarts调用百度地图画自己喜欢的底图,最终python出地图

热门文章

  1. django+mysql+插入数据库网页展示内容
  2. 2014年值得关注的10个开源项目 上
  3. LeNet-5——CNN经典网络模型详解(pytorch实现)
  4. Skywalking-02:如何写一个Skywalking trace插件
  5. toj 4596 一行盒子
  6. DFB [02] 基础和相关的非常用的几个链接
  7. zabbix mysql pgsql_Zabbix 5.0 监控 PostgreSQL 数据库
  8. 服务器证书在注册表上位置,服务器ssl证书注册表
  9. 图像处理中ct图的通道是多少_新一代安检CT机,智能安防领域又一明星产品
  10. mysql报904_数据库错误码[-904]