[CLOSED] Coolite Deployment

  1. #1

    [CLOSED] Coolite Deployment

    I recently downloaded Coolite toolkit. Tha major component is the .dll file. However, the download also contains a folder with the name:
    Coolite - Drag into your Project [not required]

    That folder containd coolite and extjs scripts together with some icons. Is this folder really NOT required for deployment (as its name says)??
    If not, then where would coolite fetch all its js from, which should be required for the AJAX functionality??
  2. #2

    RE: [CLOSED] Coolite Deployment

    Hi r_honey,

    By default the Controls will dynamically pull the required resource files (.js, .css, images) from the .dll. The files are actually stored inside the .dll as "Embedded Resources".

    The "Coolite - Drag into your Project" folder can be added to your project if you wish to use files from the local files system instead of embedded resources. 

    You can switch between file system and embedded by setting the RenderScript="File" and RenderStyles="File" on the <ext:ScriptManager>.

    You do not need to change those properties, but the option is there. Again, by default the Controls will retrieve the resource files dynamically in real time from .dll and the only thing you need to ensure is uploaded to your web server are the .dll contents of your Projects /bin/ folder. 

    Hope this helps. Please let me know if you require any further clarification and I'll be more than happy to help out. 

    Geoffrey McGill
    Founder & CEO
  3. #3

    RE: [CLOSED] Coolite Deployment

    I have not added any handler in web.config for Coolite as I am NOT using the AjaxMethods facility.
    So, does the Coolite.dll would be still able to extract the resources from the binary without the handler??

    Also, which one is the more efficient method?? Uploading the files to the server should not be a problem in case that provides any sort of performance advantage.

    Lastly (rather it should have been firstly), you people have produced really good reusable toolkit. I have checked out ExtJs also. Although the major functionality has been derived from there, still the productivity of ASP.NET web controls coupled with some cool innvovations (Ajax methods &amp; all) really make this a wonderful resource to use.
  4. #4

    RE: [CLOSED] Coolite Deployment

    Hi r_honey,

    Thanks for the feedback!!

    If you use the Controls in Visual Studio or Visual Web Developer Express, the control should automatically register a new httpHandler to your web.config.

    If you open your Projects web.config, you should find the following "coolite.axd" node.


      <add path="*/coolite.axd" verb="*" type="Coolite.Ext.Web.ResourceManager" validate="false" />
    The above handler registration is not required, but if included, the controls will automatically clean the resource url (make it look pretty) and Gzip compress the response.

    View the html source rendered to the browser with/without the above coolite.axd handler. Pay particular attention to the url's, but the difference should be obvious.

    By default the coolite.axd handler also compresses the resource files using gzip. This compression reduces the "over-the-wire" size of the files by approx 70%, which produces a significant performance improvement.

    which one is the more efficient method?? Uploading the files to the
    server should not be a problem in case that provides any sort of
    performance advantage.
    Setting RenderScripts="File" and RenderStyles="File" on the ScriptManager *must* create a performance advantage because the requests would no longer be being handled/parsed our of the Assembly/.dll by the asp.net runtime. BUT...

    1. From my experience the performance difference is negligible. You may find otherwise.
    2. The resource files are no longer automatically compressed by the Toolkit using Gzip. That will result in a significant performance decrease. This is easy to work-around by manually handling the gzipping of files, but obviously then you have to manually handle this outside of the scope of the Toolkit controls.

    It just comes down to control and convenience. You decide how much you want the Toolkit/ScriptManager to handle for you automagically. Or, you start "turning off" features and deal with the plumbing manually. The more experience you build with the Coolite Toolkit/ExtJS, the more you may decide to handle manually... and that's the beauty of the framework(s)... we give *you* that option.

    Hope this helps.

    Geoffrey McGill
    Founder & CEO
  5. #5

    RE: [CLOSED] Coolite Deployment

    Thanx, that cleaned up almost everything. The issue is resolved (I could not find a 'Mark as Answer' button though).

Similar Threads

  1. [CLOSED] IIS7 deployment
    By farisqadadeh in forum 1.x Premium Help
    Replies: 4
    Last Post: May 31, 2013, 12:55 PM
  2. Deployment issue
    By Sergio Majocchi in forum 1.x Help
    Replies: 2
    Last Post: Feb 08, 2012, 4:50 AM
  3. [CLOSED] EXT is not defined on IIS deployment
    By CMA in forum 1.x Premium Help
    Replies: 4
    Last Post: Jan 14, 2011, 10:30 AM
  4. Coolite MVC Deployment
    By Mike in forum 1.x Help
    Replies: 4
    Last Post: Oct 20, 2009, 10:17 PM
  5. Deployment problem
    By romeox in forum 1.x Help
    Replies: 0
    Last Post: Jan 20, 2009, 4:17 AM

Posting Permissions