Using a ASPxDateEdit control on a ASP.NET page the server error "File does not exist" occurs when loading the page.
The page will be loaded everytime fine but is also calling the Application_Error methode in global.asax.
On the development system everything is working fine. But on the testsystem the application will end after pressing another key (e.g. back button) on this page.
Source code of aspx:
<dxwdc:ASPxDateEdit ID="ASPxDateFrom" runat="server" TabIndex="0">
<EditorProperties DataFormatString="dd.MM.yyyy" EditFormatString="dd.MM.yyyy">
<LookAndFeel Kind="Office2003" Native="True">
</LookAndFeel>
</EditorProperties>
Server Error:
Server.GetLastError()
{"File does not exist."}
[System.Web.HttpException]: {"File does not exist."}
Data: {System.Collections.ListDictionaryInternal}
HelpLink: null
InnerException: null
Message: "File does not exist."
Source: "System.Web"
StackTrace: " at System.Web.StaticFileHandler.ProcessRequestInternal(HttpContext context)\r\n at System.Web.DefaultHttpHandler.BeginProcessRequest(HttpContext context, AsyncCallback callback, Object state)\r\n at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()\r\n at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)"
TargetSite: {Void ProcessRequestInternal(System.Web.HttpContext)}
</dxwdc:ASPxDateEdit>
Ticket
DQ40084
Visible to All Users
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Different problems (e.g. the response time of a page may increase dramatically) may also occur due to the XHTML document type - the default document type for VS 2005. Since you are working with this IDE, please note that the current version of our ASPx controls does not support XHTML. For more information on this subject, please refer to report DQ6210. I recommend that you also (1) look for other reports in the Support Center devoted to XHTML and (2) change XHTML to HTML on all pages containing our controls even though they operate properly.
Thanks,
Serge
P.S. By the way, you are using an older version of the ASPxGrid and Editors Library. Please visit our version info page at http://www.devexpress.com/Support/Versions.xml to learn about the most recent versions of our products and obtain instructions on how to update them.
Thank you for the information. So I removed all the DOCTYPE and xhtml information from my aspx pages. After that the error did not occur anymore. But unfortunately the ASPxGrid do not have bar buttons any longer. And also the layout of the page was really ugly (css problems?).
Do you think I have to upgrad to the newest version (end of the project is near) - will this really help?
This is very odd that changing the document type has affected the Grid in such a manner. In fact, the ASPxGrid does not rely on XHTML at all when rendering its elements. I recommend that you carefully verify the settings of your Grid related to the Navigator Bar to be sure that its buttons are not hidden explicitly. For example, this can be done via the Grid's Designer. If you wish, you are also welcome to send the problematic page to us. We will then try to test it with the most recent libraries. In the meantime, my personal opinion is that updating to a newer build near the end of the project is not a good idea.
As for using the CSS-defined styles with our Grid: I recommend that you examine the ASPxGrid's "LookAndFeel\StyleSheets" demo page to learn how to use such styles. The main rule mentioned in the demo description is that the style settings in a CSS will be fully applied to a control only when its LookAndFeel.Kind property is set to the Custom value. Otherwise, some of the settings may be overridden by the default values provided by different look-and-feel kinds.
Thanks,
Serge