steve curtis
Top achievements
Rank 1
Rank 1
steve curtis
asked on 14 Aug 2009, 06:08 PM
Hi,
I've followed the instructions on http://demos.telerik.com/aspnet-ajax/editor/examples/externaldialogspath/defaultcs.aspx and on http://www.telerik.com/community/forums/aspnet-ajax/editor/adding-functionality-to-a-customized-built-in-dialog.aspx in order to customise the hyperlink manager in the radeditor. This all works well except after the site has been compiled. After compilation and release the file LinkManager.ascx does not exist in the location specified in the property ExternalDialogsPath because it has been compiled into the bin folder. The compiled file name has also been changed so is not LinkManager.ascx, it is something like linkmanager.ascx.ab9a7aa3.compiled.
Is there a way around this that anyone knows?
Many thanks in advance,
Steve.
I've followed the instructions on http://demos.telerik.com/aspnet-ajax/editor/examples/externaldialogspath/defaultcs.aspx and on http://www.telerik.com/community/forums/aspnet-ajax/editor/adding-functionality-to-a-customized-built-in-dialog.aspx in order to customise the hyperlink manager in the radeditor. This all works well except after the site has been compiled. After compilation and release the file LinkManager.ascx does not exist in the location specified in the property ExternalDialogsPath because it has been compiled into the bin folder. The compiled file name has also been changed so is not LinkManager.ascx, it is something like linkmanager.ascx.ab9a7aa3.compiled.
Is there a way around this that anyone knows?
Many thanks in advance,
Steve.
2 Answers, 1 is accepted
0
Hello Steve,
The ExternalDialogsPath property relies on the physical dialog file existence. When you open the Link Manager dialog, the editor will look for a file called LinkManager.ascx specifically in the external dialogs folder. If the file is not found the editor will load the dialog from the embedded resource in the Telerik.Web.UI assembly.
If you want to use custom editor dialogs with a pre-compiled site, you can try setting the "allow this precompiled site to be updatable" checkbox when publishing. This way the content of .aspx and .ascx files will be preserved on the live server and the editor will be able to find the LinkManager.ascx. If you are not comfortable with this solution, then you will need to manually deploy the LinkManager.ascx file and exclude it from your web application so it is not precompiled when publishing.
Sincerely yours,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
The ExternalDialogsPath property relies on the physical dialog file existence. When you open the Link Manager dialog, the editor will look for a file called LinkManager.ascx specifically in the external dialogs folder. If the file is not found the editor will load the dialog from the embedded resource in the Telerik.Web.UI assembly.
If you want to use custom editor dialogs with a pre-compiled site, you can try setting the "allow this precompiled site to be updatable" checkbox when publishing. This way the content of .aspx and .ascx files will be preserved on the live server and the editor will be able to find the LinkManager.ascx. If you are not comfortable with this solution, then you will need to manually deploy the LinkManager.ascx file and exclude it from your web application so it is not precompiled when publishing.
Sincerely yours,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
steve curtis
Top achievements
Rank 1
Rank 1
answered on 17 Aug 2009, 05:03 PM
Hi Lini,
Thanks for your reply, that worked really well. The trick was removing the ascx file before the site was compiled and then putting it back in as a post build step.
Steve.