I used your code to create products dropdown from northwind database, it works fine for me
http://dotnetdevelopment.pastebin.com/BGFVEZhc Did you define the columns of *Options_DataTable* ? On Wed, Jun 16, 2010 at 4:32 PM, Troy International <[email protected]>wrote: > Hi , Thanks for your info.. > > I am working with .net 2.0 so how to resolve this issue.ie: > > you can check my issue here.. in detail. > > http://forums.asp.net/t/1524963.aspx > > Any idea.. > > > On Wed, Jun 16, 2010 at 1:26 PM, Raghupathi Kamuni > <[email protected]>wrote: > >> >> http://blogs.msdn.com/b/ddperf/archive/2008/04/28/visual-studio-2008-performance-still-room-for-improvement.aspx >> >> *Excerpts From the above link* >> ======================= >> >> *Question* >> Couple more that come to mind (although again, I can only verify it's in >> 2005 and has been around for several versions); >> >> 1. The dreaded "Function evaluation disabled because a previous function >> evaluation timed out. You must continue execution to reenable function >> evaluation" debugger error. I currently get this on a small WinForms app I >> run every time an exception gets hit, so I have to kill program execution, >> put a try/catch around it that dumps out hte stack trace, and then re-run >> because the debugger is effectively dead at this point. I've gotten this >> before on other projects; once the IDE starts doing this, it doesn't stop >> and in fact gets worse and worse, even after rebooting the machien. >> >> >> *Reply*: >> >> In VS2005 (and earlier) the main cause of functions timing out in the >> debugger was thread switching (which could be triggered by something as >> simple as accessing a WinForms property in the wrong context). Since all >> other threads were stopped, the system would hang until it timed out. In >> VS2008 we eliminated this issue by hooking thread switching calls (when in >> debugger expression evaluation) and failing them immediately. So the >> likelihood that you'll encounter that particular problem should be >> substantially reduced. >> >> Unfortunately most applications, including VS, deal poorly with slow / >> unreliable network connections. For now, the best you can do is either fix >> the lag or disconnect entirely from the network (both of which have their >> issues). Long term, we need to do a better job of designing applications to >> deal with the wide ranges of network performance. >> >> David Berg >> Developer Division Performance Engineering Team >> >> >> On Wed, Jun 16, 2010 at 12:06 PM, Venkatu <[email protected]> wrote: >> >>> have this code >>> >>> >>> DataRow[] dr; >>> dr = dt.Select("stepid = '1' AND placeid = " + >>> Convert.ToInt32(h1.Value)); >>> >>> >>> >>> so dt -- contains so many Rows from that i am going to filtering the >>> data and add that row to the another DT - Finally bind the Dt to the >>> Dropdownlist . >>> >>> Could anyone tell how to resolve this issue ? >>> >>> But it shows error : >>> >>> >>> ************** Exception Text ************** >>> System.Exception: Function evaluation disabled because a previous >>> function evaluation timed out. You must continue execution to reenable >>> function evaluation. >>> at >>> >>> Microsoft.VisualStudio.DebuggerVisualizers.DebugViewerShim.PrivateCallback.MaybeDeserializeAndThrowException(Byte[] >>> data) >>> at >>> >>> Microsoft.VisualStudio.DebuggerVisualizers.DebugViewerShim.ManagedShim.DelegatedHost.CreateViewer(IntPtr >>> hwnd, HostServicesHelper hsh, SafeProxyWrapper proxy) >> >> >> >
