Centaurs Identity
Random thoughts in my brain
To WinForms 2.0, or to Avalon, that will be the question
The question then becomes, do I commit to Windows Forms, only to throw much of it out as I move to Avalon? 
 
The answer is Yes.  [A blog to the tune of James]
 
I believe, that move to CLR/Fx is no question.  The problem is to move to "2.0" after RTM or stay "1.1" even for the year 2005.
 
Vector based graphics will be huge for GUI developers.  But Longhorn/Avalon-powered XP will not be users' choice for several years, making one could focus on WinForms for now.  Whidbey WinForms is huge too, but I don't know if we should really deploy Whidbey based WinForms and related technologies such as ClickOnce.  If it will be a pain for customers to install .NET Fx, we may want to postpone until Avalon/XP will be available.  There will be enough days to work behind the scenes to prepare installation.

Trackbacks
http://www.luckypines.com/blog/trackback.ashx?uuid=b352fad0-a33a-4f6a-9dec-398c9ae869b2

Another CTP is coming...
I’m excited to say that today we signed off on the the last few issues and started the release process for the next Community Technology Preview.  You should be able to get the bits off of MSDN later this week.  [Rick LaPlante's WebLog]
 
So, it will be announced at TechEd Yokohama next week.
 
Because ".NET Fx 2.0" may not be a significant release in terms of CLR and BCLs, the Team System feature is the one which we should carefully look at.
 
Update(2004-09-01JST): It's up for MSDN Subscription.

Trackbacks
http://www.luckypines.com/blog/trackback.ashx?uuid=d73f595a-a631-43d1-aad2-b5fa7e88fe20

And now Longhorn...
Microsoft Announces 2006 Target Date for Broad Availability Of Windows "Longhorn" Client Operating System
 
Microsoft announced:
  • Longhorn Client will be out in 2006
  • WinFS will be beta when Longhorn Client is out
  • Avalon and Indigo will be on XP and 2K3 and will be out in 2006
 
Now, .NET Fx 2.0 (a.k.a. Whidbey) will ship in later 2005 ("later" is my wild guess).  A year later from the event, .NET Fx 3.0 (a.k.a. WinFX) will ship.  I don't know why I have to put my hands dirty with Whidbey.  Given the fact that 1.0 and 1.1 Fx need a few years to be the choice for development team, it seems fair to assume that Whidbey will need at least another year to spread.  And when people already knows that they will have THE innovation a year later, who will use Whidbey?  Two more years with Everett (1.1 Fx) sounds absolutely fine for me.

Trackbacks
http://www.luckypines.com/blog/trackback.ashx?uuid=afb42ed9-594c-40a8-a45c-7803d5d0e5b1

Whidbey is reverting back
First I found this days ago from ASP.NET team, and then this from System.Xml team.  Looks like Whidbey is reverting back to be Everett...?
 
The status of mobile ASP.NET controls does not bother me at least for now, but System.Xml is definitely one of my favorite(?) namespaces, and I should always consider its climate.
 
I for one don't love DOM programming model at all and I firmly believe that XML programmer does not have to learn DOM anymore.  Many programming environments offer various sort of features that keep programmers away from DOM model.  System.Xml seems no different here, but we will see.
 
For now, we have to wait for Beta 2 to see what "reverting the XPathDocument to what it was in v1.1" really means, as well as XmlDocument's perf improvements, and the results of editable XPathNavigator.

Trackbacks
http://www.luckypines.com/blog/trackback.ashx?uuid=ec3c69aa-a9be-4e4e-85d6-80aeca62ae5d

Whidbey XPath features need namespace awareness
XmlDataSource.XPath and XPathBinder should be very interesting features, but they don't accept namespace qualified documents.  What a pity.

Trackbacks
http://www.luckypines.com/blog/trackback.ashx?uuid=a175449a-72b3-422a-a620-74acac819884

Time flies...
They are deprecating the SoapFormatter.  I don't think I have to have it anymore, so my vote is "Go ahead and deprecate it".
 
Those were the days, when SoapFormatter showed us how we can interop using objects serialized in XML.  SoapFormatter was said to be one of the most conformant implementation of SOAP Section 5.  Those were the days that "real geeks use Remoting, ASMX is for kids".  Now in 2004, we are in the world where doc/lit is the only path to survive, we don't believe Remoting provides interop anymore.
 
Amazon recognized the move too, and the latest update has doc/lit endpoint instead of rpc/encoded.

Trackbacks
http://www.luckypines.com/blog/trackback.ashx?uuid=f7cc0c40-cf58-41cb-8fae-3be68b8bd5a8

Don't just swallow it just because known authority tell you to
Middle-tier hosting: Enterprise Services, IIS, DCOM, Web services and Remoting [Rocky Lhotka]
 
The description is great, but more important is that he is telling us not to swallow everything just because your favorite conference speaker tell you to.  In most cases, it is not even what speakers want you to do.  There is no silver bullet.  You always have to choose intelligently.  There are many good hints out there from some known authorities, but they are just hints, not mandatory demands.

Trackbacks
http://www.luckypines.com/blog/trackback.ashx?uuid=d78857d2-2887-491c-9400-d77324c6ff28

Why the timebomb for international versions?
InfoPath 2003 Toolkit for Visual Studio .NET is out.
 
Now, why the heck the International versions including Japanese are limited its availability until 2005-02-28, while English version seems to work forever? You guys got to explain it.

Trackbacks
http://www.luckypines.com/blog/trackback.ashx?uuid=c3a8965c-ec53-4a9c-83bf-4e979d6d68fd

Fireworks everywhere
View from my home balcony. 
 
This is fireworks show at Sumida River behind the Rainbow Bridge.
 
 
This is also a fireworks show the same day, but at Urayasu, Chiba-pref.
 
 
It was amazing how many fireworks you could see from home at once in the very same night.

Trackbacks
http://www.luckypines.com/blog/trackback.ashx?uuid=f0dcc584-663d-403e-a66d-ff5bbe508b36

Archives
BlogRoll

Content (C) 2003 Fumiaki Yoshimatsu RSS