SRWargo

First off, let me say, WCF is a dream come true. Its everything I've been wanting to develop distributed apps. Now that wcf is live:

http://wcf.netfx3.com/blogs/news_and_announcements/archive/2006/11/08/We_2700_re-done.-WCF-is-live.-.aspx#comments

I'm wondering how I should develop applications to take advantage of this new framework

In general, I do not think its a good idea to run code developed using beta/ctp's in a production environment (licensing/support etc.). There are a few exceptions to this, but in general, I like to sleep at night, knowing that I'm running code developed using supported tools in the event that something does go awry. And to be honest, I cannot make the pitch to my boss saying we should run beta/ctp software in our multi-million dollar production environment (for so long as I want to stay employed).

That being said, I'm wondering is how others are using WCF in a production sense and what their thoughts are on all of this

It seems like the release date for orcas is so far off, that I'm not too sure how to put it into words, but not having tools to develop WCF apps today really stinks.

Thanks!



Re: Windows Communication Foundation (Indigo) Tools for WCF

Kavita Kamani - MSFT

Are you talking about the Fidalgo set of tools for developing in VisualStudio

You can always use VS 2005 to develop WCF applications and other tools like svcutil, svcconfigeditor, svctraceviewer etc all shipped final versions with our RTM release. Of course without Fidalgo, you wont get project templates and other goodness.

In a production environment, you do not deploy any of the Fidalgo stuff anyway. You will use Fidalgo in your development environment and really what you get is more productivity. Unfortunately, we were not able to get Fidalgo released at the same time as WCF Runtime RTM.






Re: Windows Communication Foundation (Indigo) Tools for WCF

SRWargo

Yes.. That is what I am refereing to. Some of my confusion stems from stale information like:

http://msdn2.microsoft.com/en-us/windowsvista/aa905015.aspx

How does Windows Communication Foundation relate to Visual Studio 2005

Visual Studio 2005 is the next release of the .NET Framework and Visual Studio development tools. Windows Communication Foundation is a set of additional managed class libraries that provide a unified framework for building advanced Web services. Windows Communication Foundation extends the .NET Framework and is fully compatible with Visual Studio 2005, meaning that developers using Visual Studio 2005 will be able to program against the Windows Communication Foundation class libraries using the language of their choice, their existing skills, and a familiar environment.

Note the Visual Studio 2005 is the next release statement (stale).

I realize that .net 3.0 development can be done in vs 2k5, w/out all the bells/whistles of the fidalgo stuff but....

I guess my question is: Is there more up-to-date information regarding what is what is not supported I just need some warm and fuzzies here. WCF is some pretty awesome stuff.

Thanks!





Re: Windows Communication Foundation (Indigo) Tools for WCF

Kavita Kamani - MSFT

If you have used ASMX/Asp.Net web services, you might remember they had an "Add Web Reference" and project templates (New Project -> Asp.Net Web Service) where these project templates automatically add some files, references to the appropriate libraries and using statements. That is the piece which is not integrated in VS for WCF in our V1 release. This is what is enabled in Fidalgo. In Orcas, Fidalgo would be rolled into VS, so you would be able to do these things easier.

Without Fidalgo, you have to create a Windows Library or a Console Application type of project in VS, manually add references to System.ServiceModel.dll and System.Runtime.Serialization.dll; add the using statements; build the host for hosting the ServiceHost, etc. You have to run svcutil on the command line to get the wsdl/proxy etc and then add it to the client project. It is just a productivity thing. WCF projects are not a first class concept in VS in the V1 release, and you have to basically add these things yourself. With Orcas and Fidalgo, that changes.

You should be able to build your WCF solutions without losing any features of WCF using VS 2005.

Hope that helps.