Single DLL for all controls

35 posts, 0 answers
  1. Rumen
    Admin
    Rumen avatar
    1536 posts

    Posted 12 Jan 2007 Link to this post

    Hi Ryan,

    That's a great idea and can combine the best of both worlds - separate assemblies for different controls (to optimize size of deployment and minimize dependencies for developers that do not need them) - and one large ILMerged assembly for developers using a lot of telerik controls in a single project - this will produce one large assembly - much easier for deployment.

    We are currently testing ILMerge and have a promising start, hopefully we will have progress in this area soon.

    Sincerely yours,
    Rumen Stankov (MCSD.NET)
    the telerik team
  2. Brian Olive
    Brian Olive avatar
    1 posts
    Member since:
    Jan 2006

    Posted 16 May 2007 Link to this post

    Do anyone have any experience with the ILMerge utility?  Basically, I have a few modules that I would like to sell which are using a couple of Telerik controls.  I didn’t want to install each of the Telerik controls with the modules, but wanted to use ILMerge to put them into one dll (easier deployment and faster loading).

    However, the problem is that if someone else place a Telerik .dll in the /bin folder along with my merged .dll the system errors with a ambiguous reference because at run-time both components are being loaded.

    Does anyone have any experience with this?  I have searched all over the internet and found much on ILMerge (basically merging your own .dlls, but not so much with commercial deployment and 3rd party components).

    Thanks for any direction that you may be able to provide.

  3. Vassil Petev
    Admin
    Vassil Petev avatar
    1765 posts

    Posted 17 May 2007 Link to this post

    Thank you, Brian, for your question.

    Indeed, having two assemblies with the same namespace and type name in the same project means that you will get an exception. This a restriction of the framework and unfortunately we do not have much control over it. The only solution is to leave the controls as they are, without using Elmer. This way if another product uses them, there will be only 1 copy in the bin folder. However, both products must reference the same version of the controls. If one is build with menu 3.0 and the other is with 3.2 then one of the products will have to be updated.

    In case you have further questions, please, use the this Forum post.


    Greetings,
    Rob

    Instantly find answers to your questions at the new Telerik Support Center
  4. masking
    masking avatar
    1 posts
    Member since:
    Aug 2007

    Posted 07 Aug 2007 Link to this post

    I want WebControls.dll I can't find it.
    please help me to find it.
  5. Vassil Petev
    Admin
    Vassil Petev avatar
    1765 posts

    Posted 07 Aug 2007 Link to this post

    Hello Amin,

    The single DLL for all controls is featured in our Prometheus suite. You can learn more about the new suite here: http://www.telerik.com/products/aspnet-prometheus/overview.aspx. The download is available in your client.net account.

     
    All the best,
    Rob
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
Back to Top