<td nowrap="nowrap">
 content
</td>

This makes the code xhtml compliant and prevents warnings in the source view of designer in Visual Studio. Normally you could just specify a nowrap attribute by itself in plain html.

Or the CSS equivalent of setting nowrap:

<td style="white-space:nowrap;">
 content
</td>

Again, using the first option will prevent warnings in source view.

//Formatting Currency
<asp:GridView id="grid" Runat="Server" >
<Columns>
        <asp:BoundField HeaderText="Amount" DataField="amt"
         FormatString="{0:c}"/>
</Columns>
</asp:GridView>

To format a Date column, you must also set the HTMLEncode property to “False”.

//Formatting a date column
<asp:BoundField HeaderText="Amount" DataField="date1"
 FormatString="{0:d}" HTMLEncode="False" />

To format a Currency with no cents:

//No cents in the currency
<asp:BoundField HeaderText="Amount" DataField="amt"
 FormatString="{0:$#,0}" />

1. When I googled this issue, I found this link. It reveals a setting you can make in your web.config to force all calls to local web services to bypass your proxy (if you have one). While I did have an internet proxy server, my local calls were not using it. You can validate this by first checking that your web service instance is using a proxy and your .asmx address is set to bypass the proxy (using WebProxy.IsBypassed).

2. What ended up being my problem is that I had Windows Authentication set on my web service virtual directory. This isn’t the default but it got set at some point. The problem was that the first call to the web service got an access denied error (401) and the second call would go through fine (I assume by trying default credentials). So the delay was in the 401 error. One error isn’t really noticeable, but string together 5 or 10 calls on one page and the delay is unbearable. For reference, the log files revealed the 401 errors and the multiple calls.

If you want to go a step further (and you are bored), you can troubleshoot the 401 errors in your iis log files.

Hope this helps.

Metabuilders had a free ASP.Net web control (with source) called DualList (or DynamicListBox) that worked really well in ASP.Net 1.1. I wanted to use it in 2.0 but there are some minor fixes needed in the code. Here is summary of the fixes I found here and here.

Combining this control with Telerik‘s AjaxManager is slick.

Steps to Convert DualList to ASP.Net 2.0

1. First download the source from the metabuilders web site. Open the solution in VS 2005 and it will start the conversion wizard. When it asks about not finding the source code bindings, choose to remove them.
2. Once the conversion is finished, the project will not compile. Open the AssemblyInfo.cs file and REMOVE:

   [assembly: AssemblyDelaySign(false)]
   [assembly: AssemblyKeyFile("")]
   [assembly: AssemblyKeyName("metabuilders.com")]

3. Now open DynamicListBoxResourceHandler.cs, REPLACE:

   if ( context.Cache[cacheKey] == null ) {
   context.Cache.Insert(cacheKey, DetermineIsRegistered());
   }
   return (Boolean)context.Cache[cacheKey];

   WITH:

   bool bRet=false;
   //fixed cache delay, do not rely on cache available immediately after insert
   if (context.Cache[cacheKey] == null)
   {
   bRet = DetermineIsRegistered();
   context.Cache.Insert(cacheKey, bRet);
   }

   else

   bRet = (Boolean)context.Cache[cacheKey];

   return bRet;

4. In DynamicListBoxResourceHandler.cs again, REPLACE:

   Object handlerMap = System.Web.HttpContext.GetAppConfig(“system.web/httpHandlers”);

   WITH:

   Object handlerMap = System.Web.HttpContext.GetAppConfig(“httpHandlers”);

5. Finally, in DynamicListBox.js, REPLACE:

   list.Tracker = DynamicListBox_FindControl( list.name + “:itemTracker” );

   WITH:

   list.Tracker = DynamicListBox_FindControl( list.name + “$itemTracker” );

You should be all set then.