Re: WSE Settings 3.0 problems (Soap protocol factory)

Tech-Archive recommends: Fix windows errors by optimizing your registry

Alec,

I'm new to this too, and I still haven't been able to get MTOM to
work, but I have been able to get web services to work without MTOM.

I assume you downloaded the WSE 3.0 Enhancements from MS:

http://www.microsoft.com/downloads/details.aspx?familyid=018a09fd-3a74-43c5-8ec1-8d789091255d&displaylang=en

Did you try running the some of the sample projects that came with
that? If you did, were you able to run them successfully?



On Mar 8, 7:32 am, "Alec MacLean" <alec.macl...@xxxxxxxxxxxxxxxxxxx>
wrote:
Hi,

I'm very new to the WSE subject, but I seem to be having an issue which so
far as I can tell shouldn't be happening.

Dev PC and Visual Studio config:
- XP Pro on an AD network
- Office 2003 Pro
- VS 2005, with SP1
- WSE 3.0
- VSTO 2005, with SP1
- VSTO 2005 SE
- Dundas Charting (ASP.NET Pro)

(This is a recently re-built PC, so registry should be pretty clean.)

I'm following the steps outlined in the WSE Documentation for configuring a
web service.

I created a new project of type "ASP.NET Web Service Application".
For this project, I right-clicked it in Solution Explorer and selected "WSE
Settings 3.0..."
In the WSE dialogue, I checked the box to enable WSE on the project.

At this point, the checkbox for "Enable Microsoft Web Services Enhancements
Soap Protocol Factory" is greyed out.

Have I missed something? Is there some sort of configuration conflict in
the add-ons for VS? Or is the WSE settings just flaky?

I'm using VB.NET as the preferred language, but I have tried using the C#
version of a web service, with the same problem.

I have read the posting in this group by Tony Girgenti ("RE: Need help with
... SoapContext error" 15/02/2007 21:52), which seems to cover a similar
issue, except he seems to have successfuly been able to check the soap
protocol box when he created a new blank web service project. I can't seem
to even get this.

Any pointers would be greatly appreciated.

Alec


.

Relevant Pages

  • Re: How to call Web Service Securely
    ... Maybe I am complicating WSE too much - can you point me to a simple ... you could provide a logon screen in the client app and create a NetworkCredential ... tokens - but that is tied to .NET 2.0 ... make a web method via dialup to my IIS Web Service. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: VBA access to WSE web service?
    ... \par Yes, you're right, COM interop is one possible approach as long as the client machine also has .net framework and WSE installed... ... \par Microsoft Online Support ... \par Subject: Re: VBA access to WSE web service? ... \par>Regarding on the calling WSE protected XML Webservice through Office ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: WSE Settings 3.0 problems (Soap protocol factory)
    ... guessing it is a configuration issue of the solution I'm trying to create. ... when I try to create a totally new Web Service project using the ... I assume you downloaded the WSE 3.0 Enhancements from MS: ... Soap Protocol Factory" is greyed out. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • RE: Web Service Security
    ... You could encrypt or hash your ... As far as web service authentication/authorisation is concerned you would be ... WSE does a pretty good job of abstracting away most of the ... a windows domain account). ...
    (microsoft.public.dotnet.framework.webservices)
  • Asychronous web service call using WSE 3.0
    ... I need to make multiple simultaneous asynchronous calls to a web service ... proxy.FooCompleted += new FooCompletedEventHandler; ... That is when we call the web service without using WSE. ... // Distinguish among asynchronous operation by providing a unique ...
    (microsoft.public.dotnet.framework.webservices.enhancements)