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 DevelopMentorŪ 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
