Coolite配置 管理软件开发历程之

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

(0)

相关推荐

  • Coolite配置 管理软件开发历程之

    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" requirePerm

  • Android开发教程之Fragment定义、创建与使用方法详解【包含Activity通讯,事务执行等】

    本文实例讲述了Android开发教程之Fragment定义.创建与使用方法.分享给大家供大家参考,具体如下: 概述 Fragment是activity的界面中的一部分或一种行为.你可以把多个Fragment们组合到一个activity中来创建一个多面界面并且你可以在多个activity中重用一个Fragment.你可以把Fragment认为模块化的一段activity,它具有自己的生命周期,接收它自己的事件,并可以在activity运行时被添加或删除. Fragment不能独立存在,它必须嵌入到

  • CentOS 7下配置Ruby语言开发环境的方法教程

    本文跟大家分享的是在CentOS 7下配置Ruby语言开发环境的方法教程,分享出来供大家参考学习,下面来看看详细的介绍: 安装Ruby 2.2 CentOS7存储库中的Ruby版本为2.0,但如果需要,可以使用RPM软件包安装2.2 1.添加CentOS SCLo软件集合存储库 [root@linuxprobe ~]# yum -y install centos-release-scl-rh centos-release-scl # set [priority=10] [root@linuxpr

  • Windows下Eclipse+PyDev配置Python+PyQt4开发环境

    本文为大家分享了Windows下配置Python PyQt4开发环境的详细步骤,供大家参考,具体内容如下 1. 下载相关软件 Eclipse下载地址:http://www.eclipse.org/downloads/ JRE下载地址:http://www.java.com/zh_CN/download/manual.jsp PyDev下载地址: http://sourceforge.net/projects/pydev/ Python下载地址:http://www.python.org/geti

  • PHP7扩展开发教程之Hello World实现方法示例

    本文实例讲述了PHP7扩展开发教程之Hello World实现方法.分享给大家供大家参考,具体如下: 一.下载PHP源代码 要开发PHP扩展,需要先下载PHP的源代码,一方面是因为我们的扩展一般会用到PHP自身定义的函数和宏,另一方面我们可以利用官方提供的工具减少工作量. 我下载了PHP-7.0.2,地址是:http://cn2.php.net/get/php-7.0.2.tar.gz. 解压源码压缩包, tar xzf php-7.0.2.tar.gz,我们现在只需要关注Zend和ext这两个

  • webpack 2.x配置reactjs基本开发环境详解

    本文介绍了webpack 2.x配置reactjs基本开发环境详解,分享给大家,具体如下: 当前webpack版本:2.2:react: 15.4.2 webpack从1.x升级到2.x替换了几个接口,包括module.loaders这样的重要接口已被弃用(详细变更).官网目前已不推荐使用1.x版本,早上折腾一番,根据2.2版本配置了react基本的开发环境,满足不太复杂的web应用开发,后期会逐步优化配置文件. 如果您之前使用过webpack,需要改动的地方并不大.下文假定您没有接触过类似的打

  • PUBWIN网吧管理软件的破解与防范

    PUBWIN这个管理软件在网吧使用非常普及,它的使用.管理上非常方便,在国内网吧管理软件是首屈一指的. 今天我就讨论一下:PUBWIN的安全性.(测试的的环境是安全性比较低的系统) 一.破解篇: 1.客户端的破解: 目前比较流行的PUBWIN的客户端的破解方式有3种 (1) 通过智能ABC输入法漏洞和软件冲突等错误破解 我们从001.jpg这张图片可以看到PUBWIN的客户端只要有2个进程RECLOCK.EXE和PUBWIN.EXE.. rerock.exe主要的作用就是每隔1-2分钟自动检测P

  • 在Ubuntu中安装VSCode并配置C/C++开发环境的方法步骤

    第一步,打开Ubuntu Software下载VSCode.(so easy) 官网地址:https://code.visualstudio.com/docs/?dv=linux64_deb 然后使用 sudo dpkg -i  xxx.deb解压即可 第二步,如果你的电脑中没有gcc,g++,gdb的话,可以通过以下代码获得. sudo apt-get update //访问源列表,并读取软件列表 sudo apt-get install gcc sudo apt-get install g+

  • VS Code配置Go语言开发环境的详细教程

    VS Code是微软开源的一款编辑器,插件系统十分的丰富.本文就介绍了如何使用VS Code搭建Go语言开发环境. VS Code配置Go语言开发环境 说在前面的话,Go语言是采用UTF8编码的,理论上使用任何文本编辑器都能做Go语言开发.大家可以根据自己的喜好自行选择.编辑器/IDE没有最好只有最适合. 下载与安装 VS Code官方下载地址:https://code.visualstudio.com/Download 三大主流平台都支持,请根据自己的电脑平台选择对应的安装包. 双击下载好的安

  • 如何在Ubuntu 18.04(实体机)上配置OpenWRT的开发环境

    一.安装虚拟机(实体机) 安装虚拟机或者实体机都可以,刚上手建议安装虚拟机,选择16.04版本或者18.04版本都OK,其openwrt开发环境的搭建过程大同小异,看自身情况选择即可.安装教程请参考其他资料,此处不再记录.因之前接触过一些Linux程序,故博主本人采用的是Ubuntu 18.04实体机. 二.换源 为避免后续遇到一些包的下载路径受网络环境限制的困难,故我们首先进行换源操作: ①打开"软件和更新": ②将原来的"中国的服务器"更改为"mirr

随机推荐