Re: Where to get WCF for Visual Studio 2005


"....DotNet4Ever...." <hate.spam@xxxxxxxxxxx> wrote in message news:Ol$ko5X5IHA.1176@xxxxxxxxxxxxxxxxxxxxxxx

"Mr. Arnold" <MR. Arnold@xxxxxxxxxx> wrote in message
You should somehow get in touch with MS and ask what's wrong with the links.


Hum... very unlikely that they will respond... I guess I will opt for not using WCF in this project.


Well, I use VS 2008. I am in the process of reading a WCF book. Yes I could use the WCF template. But I have learned how to build a WCF solution from scratch with the opening part of putting the solution together manually is do different that what the temple has to start a project with, which the book is geared towards VS 2005. The book is C#, if that makes a difference and is ISBN 978-0-470-08984-2. I would say that you really need to do it and also understand about putting all of it together manually, very interesting.

.

Relevant Pages

  • Re: Remoting or Web Service?
    ... -Web Based Administration Utility - Hosting Company ... -VPN Connection from the Corporate Office to the Hosting Company ... The topic was WCF, which MS is pushing. ... MS is going to leverage out .Net Remoting and regular Windows Web service out of its solution in favor of WCF Web service over HTTP, WCF TCP/IP, WCF Named Pipe, and WCF MSMQ, along with ASP.NET Data Service that is another type of a WCF solution. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Sharing data with host app
    ... I want to create my WCF service to basically be the ... tool to add new workitems to EventQueue. ... That would mean that you would need a WCF client in a solution that passed the object via the interface to the WCF solution for processing and that object might have to be serialized to pass it to WCF service. ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Xml Serialization - Defaulting to XmlIgnore?
    ... alternative may be to use the .Net 3.0 "WCF" serialization ... than "opt out", plus can work on fields or properties equally. ... I guess this keeps things simple with nullables etc. ...
    (microsoft.public.dotnet.languages.csharp)
Loading