Frequently Asked Questions

The following lists questions and answers about using WSE.

Setup Questions

Question When I click Repair in Add or Remove Programs, the Setup program does not remove or update the Microsoft.Web.Services3.dll file if an old version exists.
Answer Repair does not remove or update existing files; it only replaces missing files. Instead, use Add or Remove Programs to remove the program, and then add it to get a new version of the .dll file.

Question If the Microsoft.Web.Services3.dll assembly is in use by another process, such as ASP.NET, the .dll file is not removed when I click Remove in Add or Remove Programs.
Answer Ensure that no other process has locked the.dll file before clicking Remove.

Question Why are target host names always lowercase? For example, using the following URI:Proxy.Url = https://LOCALHOST/genericTestService/genericTestService.asmx Results in the following outgoing message: <to>https://localhost/genericTestService/genericTestService.asmx</to>
Answer WSE changes URL host names to lowercase by design. The host names in URI are not case-sensitive. The semantics of WSE and of HTTP are not affected in any way by this change.

Question Does WS-Security make my Web service secure?
Answer WS-Security is not a complete security solution in and of itself. It is a protocol for exchanging security information between message senders and receivers. Developers need to design an appropriate security solution and deal with potential threats, such as replay attacks.

Question How should a mustUnderstand custom header be processed?
Answer Users who want to process a mustUnderstand header should use a custom input filter, not content-based routing. The mustUnderstand fault checking is done before the ProcessRequestMessage method is called, so attempting to use content-based routing will always result in a mustUnderstand fault at the client.

Question Can I use the Certificate Creation tool (Makecert.exe) included in the .NET Framework SDK to create a test certificate that supports digital signing?
Answer Yes. An example command line is as follows:

makecert -ss My -sr LocalMachine -sk Signature -n "CN=somename"