Search

You searched for the word(s): userid:636618

Matching Posts

  • Re: Sample usage of ClientScriptManager.RegisterFo­rEventValidation

    Clay, Hmmmm, in this case, that might work. The DDL in question resides in a user control that I might be able to redesign so that it's not rendered with a server control, rather use a straight html control. However, I hope you'd agree with me that this is just a workaround for the real issue. I'd still like to understand the following: 1. Is is possible to disable postback event validation for a single control on a page? 2. Is it possible to register a custom delegate to perform the event validation
  • Is WSE 3.0 supported on a compact framework device?

    Does WSE 3.0 support the compact framework (version 2.0)? I have a PocketPC app in VS2005, targetting Windows Mobile 5. I enable WSE 3.0 for the PocketPC project and create a web reference to my WSE 3-enabled webservice. This part works OK. I get a compile error on the generated proxy class for the web reference: private System.Threading.SendOrPostCallback HelloWorldOperationCompleted; The SendOrPostCallback class does not exist in the System.Threading namespace of the CF version of the System.dll
    Posted to XML Web Services (Forum) by n33470 on 12/16/2005
  • Does CF support WSE?

    Is WSE 3.0 supported on the compact framework (version 2.0)? I have a PocketPC app in VS2005, targetting Windows Mobile 5. I enable WSE 3.0 for the PocketPC project and create a web reference to my WSE 3-enabled webservice. That part works OK. I get a compile error on the generated proxy class for the web reference: private System.Threading.SendOrPostCallback HelloWorldOperationCompleted; The SendOrPostCallback class does not exist in the System.Threading namespace of the CF version of the System
    Posted to Mobile and Handheld Devices (Forum) by n33470 on 12/16/2005
  • Re: Sample usage of ClientScriptManager.RegisterFo­rEventValidation

    Clay, OK, that's a good start, at least I understand more about how the RegisterForEventValidation works. The difference with my design is that the DDL is populated by the *user* through script. My aspx page has a DDL. That DDL may have extra values programmatically added to it from javascript so that on postback the selected item in the DDL was not in the *original* viewstate of the DDL. I realize that this is exactly what the event validation design was supposed to flag, in this case the event
  • Re: ASP.NET 2.0 web project changes filenames to lower case

    Thanks for the info! I'll keep watching for an announcement about the update. --steve
  • string Replace function different in VS2005

    Hi all, We have a function that makes use of the string replace function in a CR formula. In previous versions of .NET (both VS2003, and earlier) this worked OK. Now running in VS2005, the behavior of this function is different. Here is a sample of the code: StringVar sTemp := Replace ({Notices.ReminderNotice}, "@Name", {@DriverName}, 1, -1, 1 ); sTemp := Replace (sTemp, "@Type", {SourceTable.MaintItemName}, 1, -1, 1 ); sTemp := Replace (sTemp, "@Date", CStr ({SourceTable.MaintItemDate}), 1, -1,
    Posted to Crystal Reports (Forum) by n33470 on 12/13/2005
  • Sample usage of ClientScriptManager.RegisterFo­rEventValidation

    Hi all, I have a dropDownList on a web page that is populated by client-side script. I get an error on PostBack of the page. I've seen quite a few posts about this, so I understand the issue, and why it's occurring. I know that I need to remove the automatic event validation that ASP.NET is performing on the control. One of my options is to use the page directive enableEventValidation="false". I'd rather not do this for the entire page, I'd rather remove the event validation for only the dropdownlist
  • ASP.NET 2.0 web project changes filenames to lower case

    We have a web site that is being converted from the 1.1 format into 2.0. I've noticed that after the web project has been converted, the first time that the solution is opened in VS, all of the aspx and ascx filenames are changed to lowercase. The filenames are not being changed during the conversion process. After conversion completes, the filenames remain unchanged. However, the first time that the solution is opened in VS2005, the mixed-case filenames of the ASPX and ASCX files are all changed
Page 1 of 1 (8 items)