Firstly, im tracking S91705 and you updated it today 16 jan. After looking at this issue i cant update it in any way. and i need to as there is a serious flaw in your skin files.
As an example the aspxbutton.skin contains the following CssFilePath="~/App_Themes/Aqua/{0}/styles.css"
As soon as these themes are put in the global theme location they all fail.
The purpose of S91705 was for you to provide a machanism that would allow developers to deploy the themes once only and not have to repeat them in every application.
That is the purpose of global themes.
Your standard themes fail in this suitation.
Image location also fail, eg:
<LargeIncrementImage Url="~/App_Themes/Aqua/Editors/edtSpinEditLargeIncImage.png" UrlHottracked="~/App_Themes/Aqua/Editors/edtSpinEditLargeIncHottrackedImage.png" UrlPressed="~/App_Themes/Aqua/Editors/edtSpinEditLargeIncHottrackedImage.png" UrlDisabled="~/App_Themes/Aqua/Editors/edtSpinEditLargeIncDisabledImage.png" Width="7px" Height="9px" />
the solution for images is as follows:
<ErrorImage Height="14px" Url="Editors/Error.gif" Width="14px" />
The solution for skin files seems to be to leave the css file path out entirely. for example the following works for me:
<%@ Register TagPrefix="dxe" Namespace="DevExpress.Web.ASPxEditors" Assembly="DevExpress.Web.ASPxEditors.v8.3" %>
<dxe:ASPxButton runat="server"
CssPostfix="BlackGlass">
</dxe:ASPxButton>
another important issue with S91705 is that when you release you product can it contain one zip file that contains all the themes. otherwise they seem to be repeated all over the place. and sometimes seem different.
I havent looked at the win form versions of the themes. they can also reside in a global location so should not be application realative in any way.
Thanks
We have closed this ticket because another page addresses its subject:
Global themes not compiling - Compiler Error Message: CS0012: The type 'DevExpress.XtraScheduler.Native.IDateNavigatorControllerOwner' is defined in an assembly that is not referenced.
Hello Michael,
Thank you for your comments. Suggestion <sclink id="S91705">S91705 hasn't been yet implemented. It may be implemented in the next major version. Please stay tuned. You'll be notified via email when the suggestion's status becomes "Implemented".
Thanks,
Nick
--------------------
Check if Search Engine is able to answer questions faster than I do!
Im, sorry this is a bug.
As soon as the themes are put in a global location they fail.
Its a serious bug.
Michael,
Please provide me with step-by-step instructions on how to reproduce the issue. I'll try to replicate it on my system by following your instructions.
Thanks,
Nick
--------------------
Check if Search Engine is able to answer questions faster than I do!
Nick, thnaks.
How to usae global theming is documented in MSDN. However to help resolve this issue:
Michael,
Sorry for the delay. We are investigating the problem and looking for a solution. I'll write back to you as soon as a solution is found.
Thanks,
Nick
I sent you the solution. It seems to work for me.
Remember that themes are process on the server and dont need app relative paths, ie ~. Just file system relative paths.
We've improved the functionality of the ASPxThemeDeployer tool. Now our themes can be deployed to a global theme folder as well.
Thanks for the update.
However im getting the following error after installing the new theme skin files
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0012: The type 'DevExpress.XtraScheduler.Native.IDateNavigatorControllerOwner' is defined in an assembly that is not referenced. You must add a reference to assembly 'DevExpress.XtraScheduler.v8.3.Core, Version=8.3.4.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a'.
Source Error:
Line 341: this.@__controlSkins[@__BuildControl__control11_skinKey] = new System.Web.UI.ControlSkin(typeof(DevExpress.Web.ASPxDataView.ASPxDataView), new System.Web.UI.ControlSkinDelegate(this.@__BuildControl__control11));
Line 342: this.@__controlSkins[@__BuildControl__control23_skinKey] = new System.Web.UI.ControlSkin(typeof(DevExpress.Web.ASPxEditors.ASPxDateEdit), new System.Web.UI.ControlSkinDelegate(this.@__BuildControl__control23));
Line 343: this.@__controlSkins[@__BuildControl__control25_skinKey] = new System.Web.UI.ControlSkin(typeof(DevExpress.Web.ASPxScheduler.ASPxDateNavigator), new System.Web.UI.ControlSkinDelegate(this.@__BuildControl__control25));
Line 344: this.@__controlSkins[@__BuildControl__control26_skinKey] = new System.Web.UI.ControlSkin(typeof(DevExpress.Web.ASPxEditors.ASPxFilterControl), new System.Web.UI.ControlSkinDelegate(this.@__BuildControl__control26));
Line 345: this.@__controlSkins[@__BuildControl__control29_skinKey] = new System.Web.UI.ControlSkin(typeof(DevExpress.Web.ASPxGridView.ASPxGridView), new System.Web.UI.ControlSkinDelegate(this.@__BuildControl__control29));
Source File: c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\crm\4d81fe47\9ac8edd6\App_GlobalTheme_Office2003 Blue.2saptb9x.0.cs Line: 343
Hi Michael,
Please make certain that you have added a reference to the DevExpress.XtraScheduler.v8.3.Core assembly in your web.config file and also in the application's References list (if you are using a web application). This should help you address this issue. If not, please let us know how you deployed a themes: globally or locally. Also, please send us a problematic page for the investigation.
Thanks,
Plato
Plato, im sorry but please read the history of this issue and it will answer all your questions
Hi Michael,
I think we've determined the cause of the problem and fixed this problem in the Global themes not compiling - Compiler Error Message: CS0012: The type 'DevExpress.XtraScheduler.Native.IDateNavigatorControllerOwner' is defined in an assembly that is not referenced. thread, so you can get the public fix for this issue there.
With best regards,
Dmitry
This issue was logged by a previous employee but I inherited his log in, so I am closing this issue.