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

程序员文章站 2024-03-07 22:16:27

1.从官方网站下载coolite toolkit： 2.修改web.config文件

1.从官方网站下载coolite toolkit：

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>
    <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">
   <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 mode="windows"/>
  <!--
            如果在执行请求的过程中出现未处理的错误，
            则通过 <customerrors> 节可以配置相应的处理步骤。具体说来，
            开发人员通过该节可以配置
            要显示的 html 错误页
            以代替错误堆栈跟踪。

</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>

<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]
-->

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


<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


    see \build\resources\coolite\licenses\famfamfam.txt for more information.

2. json.net provided by james newton-king


    see \build\resources\coolite\licenses\newtonsoft.json.txt

3. ext js - javascript library provided by extjs llc


    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

上一篇：浅析Java中的GC垃圾回收器的意义及与GC的交互

下一篇：详解Java中list,set,map的遍历与增强for循环

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