Here. "[O]ne thing doesn't make users happy—not having full control of any processing that their applications are performing. Even though the UI is responsive while pi is being calculated, the user would still like the option to cancel the calculation if they've decided they need 1,000,001 digits and they mistakenly asked for only 1,000,000."
In this article, I add canceling to my asynchronous pi calculating WinForms app.
Here. Bamboo.Prevalence is a "prevalence engine" for .NET. If you don't know what that means (I didn't), you can check out [1], which gives a good intro and then provides a FAQ for the skeptical. In a nutshell:
"For many systems it is already feasible to keep all business objects in RAM. ... To avoid losing data, every night your system server saves a snapshot of all business objects to a file using plain object serialization."
I admit to still being skeptical after reading the FAQ, but it's mostly a "this feels wrong, I'll think of a reason later" kind of a skepticism. : )
[1] http://www.prevayler.org/wiki.jsp?topic=ObjectPrevalenceSkepticalFAQ
Here. I know I don't organize things well for finding what's new in my list of VS.NET Fun Facts, but if you haven't checked back in a while, I add new tips and tricks all the time.
Today I added Nick Hodapp's tip on reducing the amount of time VC7 spends checking included header files for changes and another on Shawn Van Ness's "grokking" of the VS.NET clipboard ring.
If you have a fun fact, send it along!
Here. "We like .NET Remoting and its extensibility model. We want to show the world that you can do some pretty useful (and some weird) things with this model. We also like the ideas behind SOAP and web services but somehow believe that .NET Remoting is a superset of them and offers features which are needed by today's developers."
This open source site for .NET remoting extensions continues to grow with a new bi-directional TCP channel to work in firewall environments.
Here. "Have you ever wondered what was *really* stored in the view state of your .aspx pages? Well, now you can find out with the free view state decoder utility [1]. Just type in the URL of the page whose view state you would like to decode, and view the contents of the view state through a tree-view, as raw text, or as parsed XML. You can also copy and paste the view state string by hand to decode it. For a screenshot of this utility in action, check out: http://staff.develop.com/onion/images/decoderscreenshot.gif"
I've used this and loved it. It works a treat!
Here. Thanks for the submissions, folks! People reported exhaustion after spending 24 hours rushing to finish their entries, but uniformly thanked me for having them do it (and thus the power of .NET is revealed : ).
The judges are judging and I will the results as soon as I have them.
