This question is locked. New answers and comments are not allowed.
Frederic Latour
Top achievements
Rank 1
Rank 1
Frederic Latour
asked on 31 Jul 2007, 03:03 PM
Hi,
The various deployment options of telerik controls (problem would occur with other 3rd party controls as well) with Moss may cause some problems at some time. Either for Web Part development or specific apps in layouts folder one is facing the following limitations:
1) if not deploying in GAC, several versions of the same control may not cohabit. The latest deployement will override the previous ones and will break possible web parts or apps using that specific version.
2) If deploying in GAC still you may encounter a problem in the following scenario. Let's say a Web Part using some radcontrols has been deployed. Another web part using some radcontrols - some of them being used as well by the first web part - is also deployed afterwards. In case, one of this web part is removed (solution is retracted), the radcontrols that were deployed alongside this web part will be removed from the GAC thus breaking the other web part which was relying on some radcontrols that have been removed.
Can you confirm my scenario?
In order to get rid of this dependency, I made some tests using ILMerge:
I built a web part and merged it with the radcombobox control assembly and then deployed this web part on Moss.
When using embeded sripts, it didn't work. For some reason, I am getting a script error on the page. There must be some good reason why but I didn't get further.
I then decided to use scripts from from radcontrols "dir". I had to rename the script version folder using the version of the resulting merged assembly. That seems quite logical as you must asked for the current assembly version. Though it seems to load the script correctly and be overall working, I have some strange results.
More specifically, regarding radcombobox, the drop down does not expand adjacent to the input field like if I had applied a 200 OffsetX.
I did not test other radcontrols using ILMerge as there seems to be some side effects.
Any idea of what could be the reason?
What do you think of the ilmerge scenario? It could solve some deployment problems when using development frameworks like Moss and could also make it possible to prevent possible reuse of your controls by internalizing them when merged.
Thanks in advance for any input.
Regards,
The various deployment options of telerik controls (problem would occur with other 3rd party controls as well) with Moss may cause some problems at some time. Either for Web Part development or specific apps in layouts folder one is facing the following limitations:
1) if not deploying in GAC, several versions of the same control may not cohabit. The latest deployement will override the previous ones and will break possible web parts or apps using that specific version.
2) If deploying in GAC still you may encounter a problem in the following scenario. Let's say a Web Part using some radcontrols has been deployed. Another web part using some radcontrols - some of them being used as well by the first web part - is also deployed afterwards. In case, one of this web part is removed (solution is retracted), the radcontrols that were deployed alongside this web part will be removed from the GAC thus breaking the other web part which was relying on some radcontrols that have been removed.
Can you confirm my scenario?
In order to get rid of this dependency, I made some tests using ILMerge:
I built a web part and merged it with the radcombobox control assembly and then deployed this web part on Moss.
When using embeded sripts, it didn't work. For some reason, I am getting a script error on the page. There must be some good reason why but I didn't get further.
I then decided to use scripts from from radcontrols "dir". I had to rename the script version folder using the version of the resulting merged assembly. That seems quite logical as you must asked for the current assembly version. Though it seems to load the script correctly and be overall working, I have some strange results.
More specifically, regarding radcombobox, the drop down does not expand adjacent to the input field like if I had applied a 200 OffsetX.
I did not test other radcontrols using ILMerge as there seems to be some side effects.
Any idea of what could be the reason?
What do you think of the ilmerge scenario? It could solve some deployment problems when using development frameworks like Moss and could also make it possible to prevent possible reuse of your controls by internalizing them when merged.
Thanks in advance for any input.
Regards,
1 Answer, 1 is accepted
0
Frederic Latour
Top achievements
Rank 1
Rank 1
answered on 31 Jul 2007, 03:13 PM
I realized I did not post in the right forum.
Please delete this thread as I copied it in the appropriate forum which is "Integrating RadControls...".
Sorry,
Please delete this thread as I copied it in the appropriate forum which is "Integrating RadControls...".
Sorry,