Noted. But, just reading the specs would lead me to think that it is a
natural progression of C# to make it more compatable with WinFX in Longhorn.
Or at least, that is my take on all the different things I have read about
Longhorn's file system. I have read that WinFX should not be thought of
exactly as a file system. But a part of one. Anyway, I was just curious
how current C# programmers felt about( Xen or whatever it ends up being
called) it and if they (C# programmers) would react the same way VB6
programmers did about the changes to VB6 to VB.NET (which I like by the
way).
I like C# as it is right now. I just wonder how drastic the changes to get
to Longhorn and it's functionality will be with current code.
james
"Eric Gunnerson [MS]" <er****@online.microsoft.com> wrote in message
news:O6**************@TK2MSFTNGP09.phx.gbl...
Note that Xen is a project in MSR, and therefore it is - like most MSR
projects - of a speculative nature. A sort of "if we did this, what would
it look like?" exercise.
--
Eric Gunnerson
Visit the C# product team at http://www.csharp.net
Eric's blog is at http://weblogs.asp.net/ericgu/
This posting is provided "AS IS" with no warranties, and confers no
rights. "james" <jjames700ReMoVeMe at earthlink dot net> wrote in message
news:uY*************@tk2msftngp13.phx.gbl... Here is an interesting article from WinInfo that I thought folks here
might like to comment on.
james
Just What We Need--Another Programming Language
I hope you've have mastered C# because Microsoft is working to
replace it with yet another C-like programming language. Dubbed Xen
(previously X#), the new language melds C# with XML and Microsoft SQL
Server support. To be fair, if Microsoft develops the new language
correctly it will be a superset of C#, prompting me to wonder whether
the company should market Xen as a new C# version. Otherwise,
Microsoft risks alienating C# users as the company alienated Visual
Basic (VB) users when it moved from the simple VB 6.0 language to the
more complicated Visual Basic .NET.
