Alex Norcliffe
Top achievements
Rank 1
Rank 1
Alex Norcliffe
asked on 13 Jul 2006, 12:47 PM
Hi everyone
I write a CMS which references lots of Telerik controls and I have run into a problem.
The CMS allows you to upload third-party .NET user controls and run them within the site design so that you can have dynamic pages managed within the database - you just have to upload the DLL to the bin folder to add to the ones already there for the CMS.
The problem I have is that sometimes those 'plugin projects' DLLs might reference a Telerik DLL, a different version to the one used by the CMS.
This then means that if I recompile the CMS to include the latest MINOR version increases on the Telerik stuff (even hotfixes), the application fails because the plugin DLL was not built for the very very latest Telerik DLL - even though I know it will run beause the API hasn't changed.
So my question is, does anyone know how I can compile the plugin projects to very loosely reference the DLL by just its path, rather than the entire strong name of the Telerik assembly? So that it doesn't throw an exception if the version number changes? If I were to be changing a MAJOR version of the Telerik DLL I would be happy to recompile all the plugin projects, but not for every Hotfix....
Either that, or if someone knows of a way to have two versions of the same assembly within one application that would be even better. I thought this was possible with side-by-side execution but I have a feeling you can't do it within the same ASP.NET application.
Any and all help GREATLY appreciated!
Many thanks
Alex
I write a CMS which references lots of Telerik controls and I have run into a problem.
The CMS allows you to upload third-party .NET user controls and run them within the site design so that you can have dynamic pages managed within the database - you just have to upload the DLL to the bin folder to add to the ones already there for the CMS.
The problem I have is that sometimes those 'plugin projects' DLLs might reference a Telerik DLL, a different version to the one used by the CMS.
This then means that if I recompile the CMS to include the latest MINOR version increases on the Telerik stuff (even hotfixes), the application fails because the plugin DLL was not built for the very very latest Telerik DLL - even though I know it will run beause the API hasn't changed.
So my question is, does anyone know how I can compile the plugin projects to very loosely reference the DLL by just its path, rather than the entire strong name of the Telerik assembly? So that it doesn't throw an exception if the version number changes? If I were to be changing a MAJOR version of the Telerik DLL I would be happy to recompile all the plugin projects, but not for every Hotfix....
Either that, or if someone knows of a way to have two versions of the same assembly within one application that would be even better. I thought this was possible with side-by-side execution but I have a feeling you can't do it within the same ASP.NET application.
Any and all help GREATLY appreciated!
Many thanks
Alex
1 Answer, 1 is accepted
0
Hello Alex,
We believe that this link will be helpful in your case.
Let us know how it goes.
Best wishes,
the telerik team