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...@NO-SPAM-copeohs.com>
wrote:

Hello again.

After a little further experimention last weekend - I was following the
Hands On Lab for Security - I happened to find that the issue of whether the
SOAP Protocol Factory checkbox is enabled or not is determined by the type
of web project you choose when you create the project.

When starting a new Web Service project, if you use the "New Web Site"
toolbar button instead of the "New Project" toolbar button, you get to
choose from a different set of project types for web-based projects.

The reason for this is that after installing the WAP add-in or VS2005-SP1
(WAP is now included as standard as part of VS2005-SP1), the New Project
dialog version of creating a web service will create an "ASP.NET Web Service
Application", (note the additional word "Application" here is an important
distinguishment) which will consequently create the project using the WAP
settings - that is, allowing precompilation of the DLL like VS2003 does
rather than compile on first access to the site.

For some reason the WAP settings disable the ability of the WSE 3 Settings
dialogue to control the web.config file sufficiently for adding the SOAP
Protocol Factory, although you can still enable the project for using WSE-3.
I don't know if this is by design or accident - perhaps someone with greater
knowledge on the subject could let us know about this aspect?

If instead you choose the "New Web Site" option from the toolbar, you can
choose the "ASP.NET Web Service" option (note, no "Application" in the
description this time).  This project template then allows the WSE Settings
dialogue to work as expected.

Due to other project commitments, I have not yet managed to get time to
determine if by simply manually editing the web.config file to add the
protocol factory settings this will enable them correctly for use under a WS
Application version project, or whether it has some detrimental effect hence
why the checkbox gets disabled.

I hope this helps anyone else scratching their heads trying to get this
(potentially great) free toolkit working!

Regards,

Alec