When you set a DataGrid’s datasoure to a LinqDataSource control you still need to handle the paging event in your code behind file.  It’s also worth noting that the DataGrid does not use the Linq skip and take paging functionality.  The DataGrid will simply request all results and page them in memory.

When you over load the OnSelecting event you do not need to specify a datacontext or TableName or other query specific properties.

When you specify a css class for your GridView’s PagerStlye (PagerStyle.CssClass=”pagerStyleClass”) the rendered table row class font-size.

You will need to select the child table of this tr element  in your css

.pagerStyleClass Table{font-size: 10px;}

I am starting to suspect VB.net 2008 is not saving all my changes.  This is not a good sign.  Maybe this will be fixed in SP1.  I hope a lot of my VB headaches will go a way with SP1

So there is this little petition online ADO .NET Entity Framework Vote of No Confidence.  Which seems to have evoked a response from the Entity Framework team.

But I don’t care to be talked down to by the  so called experts.  “Warning” poor old me not to use technology that does not fit their.  It seems obvious to them that all domain’s and software shops are the same, and I clearly  cannot evaluate a framework.( Maybe this is true, I am on windows after all.  But then what does that say about them?)

There are cases where the Entity Framework will prove most useful.  While POCO can be nice, it’s not always what I am looking for.  Some times I do actually need data storage. And some times persistence ignorance is not a benefit.

I would like to thank Kathleen and Julie for their contrarily posts to the petition.

Kathleen Dollard: Entity Framework Petition 

Julie Lerman: Oh that no-confidence vote on E.F.

What happens when it rains?

Amazon S3 and data corruption. Thread: S3 data corruption?

We've isolated this issue to a single load balancer that was brought into service at 10:55pm PDT on Friday, 6/20.  It was taken out of service at 11am PDT Sunday, 6/22.  While it was in service it handled a small fraction of Amazon S3's total requests in the US.  Intermittently, under load, it was corrupting single bytes in the byte stream.  When the requests reached Amazon S3, if the Content-MD5 header was specified, Amazon S3 returned an error indicating the object did not match the MD5 supplied.  When no MD5 is specified, we are unable to determine if transmission errors occurred, and Amazon S3 must assume that the object has been correctly transmitted. Based on our investigation with both internal and external customers, the small amount of traffic received by this particular load balancer, and the intermittent nature of the above issue on this one load balancer, this appears to have impacted a very small portion of PUTs during this time frame.
One of the things we'll do is improve our logging of requests with MD5s, so that we can look for anomalies in their 400 error rates.  Doing this will allow us to provide more proactive notification on potential transmission issues in the future, for customers who use MD5s and those who do not. In addition to taking the actions noted above, we encourage all of our customers to take advantage of mechanisms designed to protect their applications from incorrect data transmission.  For all PUT requests, Amazon S3 computes its own MD5, stores it with the object, and then returns the computed MD5 as part of the PUT response code in the ETag.  By validating the ETag returned in the response, customers can verify that Amazon S3 received the correct bytes even if the Content MD5 header wasn't specified in the PUT request.  Because network transmission errors can occur at any point between the customer and Amazon S3, we recommend that all customers use the Content-MD5 header and/or validate the ETag returned on a PUT request to ensure that the object was correctly transmitted.  This is a best practice that we'll emphasize more heavily in our documentation to help customers build applications that can handle this situation.
If you have specific questions or concerns about how your application might have been affected, please feel free to e-mail us at aws@amazon.com.

When I used the 3.0 Firefox installer I have a version that reports 2.0.0.14  that's messed up.

I have been working on moving a lot of inline styles to a separate CSS page today.  There are some asp:datagrid that I would like to control paging(number of pages, page mode…) and other settings in one configuration location rather then each page.  I just realized I was looking for MVC.

CBS has placed some of its classic TV shows such as Star Trek, Hawaii Five-O, MacGyver online for our viewing pleasure.

Microsoft gave us a new toy to play with to help us scale better.

“Velocity” is a distributed in-memory application cache platform for developing scalable, available, and high-performance applications. Using “Velocity,” applications can store any serializable CLR object without concern for where the object gets stored because data is cached across multiple computers. “Velocity” allows copies of data to be stored across the cache cluster, protecting data against failures. It can be configured to run as a service accessed over the network or can be run embedded with the distributed application. “Velocity” includes an ASP.NET session provider object enabling storage of ASP.NET session objects in the distributed cache without having to write to databases, which increases the performance and scalability of ASP.NET applications.

Down load the CTP

Project Velocity’s team blog

brief demo of WCF using Twitter’s REST API Programming Twitter with WCF 3.5

by Dariusz.