June 2005 - Posts
Note: this entry has moved.
We've a
community site for GAT, where you can
get the hands on lab that we did for TechEd 2005. Go get it if you want to have a very comprehensive idea of what's possible with
GAT....
Note: this entry has moved.
Jim Newkirk has just released a very useful package. And it's based on
GAT! :)).
Note: this entry has moved.
As
Eugenio and
Edjez mentioned, the second
community drop of CAB is around the corner. What you'll find in CAB is basically what's missing the raw widget framework of .NET (a.k.a. WinForms): support for reusability, life cycle management and shared state and events at the use case level, pluggable modules, injection of dependencies between components, and a very powerful loosely coupled event system/broker (among other things). Here's the team, in all its glory, after finally getting an official war room:
The war room has been substantially improved with a reorganization we did yesterday. I'll post more pictures later, but much more happy with the new layout :)
Note: this entry has moved.
Is it the format? The idea of collaborative editing? Other features?
From the Wikipedia, the definition is:
A wiki is a collaborative collection of interlinked web pages, all of which can be visited and edited by anyone at any time (collaborative software). Ward Cunningham invented the concept and software. You could even edit this page by clicking the "edit" link on the third tab above, or edit only a section by clicking on "[edit]" to its right! If you don't have anything to add or correct on this page and you just want to see how it works, try out the Wikipedia:Sandbox. See also Wikipedia:Editing FAQ and WikiWiki.
So you can see that there's no reference whatesoever to the format.
I know I hate the format (to make a nicely formatted table header with a bold title with a link, just type ||~*[--/?mylink?;-=+]}||... yeah, right.... even worse is that no two engines implement the same formatting rules)
I know we'll something about it.
Note: this entry has moved.
SqlCommand can infer parameter types from their values. It has always been that way. Therefore, you don't need to care about the mapping between CLR types and SQL types. In Whidbey (.NET v2.0), nullable types (Nullable<T> generic class) were introduced to better support database scenarios, where a field that would map to a CLR value type can actually be null. I would have expected the same type inference on parameters to be performed for these types too, basically resolving to the underlying type (i.e. Int32 in a Nullable<int>) and having the parameter set to null if it didn't contain a value.
Turns out that if you try to use parameter inference with Nullable<T>, you will get an exception saying that the managed provider does not know how to map the Nullable<T> to a native type. As usual,
I reported the bug, which they resolved
*By Design* (hopefully they will change the resolution to
Posponed, which is what I would expect given their own answer to the issue). Hence, it's not supported and will not be in Whidbey. Too bad as auto-generated data access layers now will have to account for this. And it's bad because although the introduccion of the Nullable<T> made it easier to generate the reading piece, it now complicates the querying and updating :(.
Note: this entry has moved.
I hate to do this again. For most well-developed, web-friendly sites (yeah, there are sites that are not friendly at all with the
web architecture), search engines will be a great aid in spreading the word. For example, if you
search Google for "TechEd GAT Hands On Lab", right on the first result page you will get what you look for, even if the website was launched just a
*week* ago. Now,
do the same for SgmlReader, a user sample in
GotDotNet which tons of weblogs and articles link to, and the only one with such a name: you will get it in the
**seventh** page, even if it has been around for years. Enough said...
Note: this entry has moved.
Yesterday I posted about
how Microsoft is listening to customers, and specially the excelent experience I had using
Product Feedback. Now it turns out that
one of my favorite bugs, one that I reported and
kept pushing for almost a year now, is in
Somasegar's
top 10 customer issues, third in the list :). I'm specially flattered about the description:
Description: Twice we resolved this issue as "Won't Fix" but because "kzu" kept pushing, reopening the bug and insisting we reconsider, we did and fixed it for Beta 2. I want to thank kzu for driving this issue for the community.
Fortunately I reopened the bug after he ran the query :o).... I only wish I had more support from ASP.NET MVPs (specially those with strong reputation among the product team...)
Note: this entry has moved.
I've broken the mark of 100 bugs entered thorugh
Product Feedback!!! I can only thank Microsoft for the diligence in reviewing, and even fixing most of them, even those that I qualified as less important. But when you report a bug, you have to be responsible for it, track it, provide more feedback when needed, regress them when they are fixed, etc. That's the only way you really contribute to the product. Most of my bugs were were acknowledged as such, and only a handful were either by design or not repro. I'm happy that most of them were resolved in one way or the other :).
Contributing this way makes you definitely feel part of the process of helping the platform continue to rock!
More Posts