The important thing about .NET that one should not lose sight of is that when the code is finally compiled into machine code by the JIT the source code is MSIL and not the language you wrote your assemblies in.. Therefore C# is not necessarily the vehicle in which MS promotes Windows Forms. It's developer/organization policies/preferences that steer a project toward one lanugage or another.
The tech evolution for Windows client is Win32 - NextGenerationWindowsServices - which was branded as .NET - System.Windows.Forms, which will be followed by - WinFx as part of Longhorn - which will include a new UI presentation model , Avalon - parts of which are being ported backwardly to Windows XP, Windows 2003. MS does not do itself favors by the confusing branding they seem to output. The so-called Windows Client, or fat client, is now being referred to as a "Smart Client". http://msdn.microsoft.com/smartclient/ You stated you weren't sure when MS will be able to use .Net and C# for Windows Development, and the answer is "now and has been for a while". CC 1A 5B 94 D0 75 09 B4 USA USA USA USA USA http://www.vinnychi.com/vince Did you think that I was gonna give it up to you? > -----Original Message----- > From: Unmoderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Scott > Sent: Saturday, December 25, 2004 12:23 AM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: [ADVANCED-DOTNET] Persistence Options > > I haven't read WSE2.0 for .NET, but I could certainly > understand why it > would say that Web Services interfaces should be Platform independent. > This is a main goal of Web Services which leads to increased > interoperability between systems using different technologies. > > However, a particular implementation of a web services client > or server > must use some specific technology such as Java or .Net. So, > the question > is, how would you decide which technology to use? > > Correct me if I'm wrong, but it seems like .Net and C# is Microsoft's > strategy for Web Services and the future of development on > Windows. If I > wanted to write an application for Windows that will have a > Windows UI, at > some point in time, it would seem that C# would be the > obvious answer for > what technology I would choose. I don't have a good > understanding of the > current state of C# and .Net and its adoption in industry, so > I couldn't > begin to make an estimate of when that might be. But, it does seem > inevitable. If this wasn't Microsoft's plan, why would they > include the > ability to build Windows forms with C# and .Net? > > Do others disagree? Am I missing something? > > Scott > > > > > On Wed, 24 Nov 2004 23:51:23 -0600, James > <[EMAIL PROTECTED]> wrote: > > > > > > >________________________________ > > > >> Scott writes > >You say that most consumers don't have .Net installed. This > seems like a > >temporary problem, since Microsoft has put a large investment in .Net > > > >Scott, > >Microsoft recomends that you write WebServices interfaces to > be Platform > independant and to support IEEE standards. > >This in a nutshell means that .Net (or any Language)should > not required by > your web service client. > >Support for this and other things are documented in WSE2.0 for .NET. > > > >Good Luck with your studies! > > > >=================================== > >This list is hosted by DevelopMentorR http://www.develop.com > > > >View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== > This list is hosted by DevelopMentorR http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== This list is hosted by DevelopMentorŪ http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
