Support for the xslt document () function and embedded script blocks are disabled by default These features can be enabled by creating an xsltsettings object and passing it to the load method Well, everything is working perfect for a transformation loaded from the file. I am attempting to create web.config files for testing, qa and production environments When the web.config file is unencrypted, all transformations work as expected, replacing connection strings and app settings where appropriate After encryption of the connection strings and app settings sections, transformation no longer occurs during publication.
How can i have the different operationcontract s get separated in the wsdl? I'm assuming i will have to modify the reference.cs file or maybe even the wsdl, but here's some of the code i've done for the binding.is this on the right track? How can i set up my client's binding to get a token from the sts and send that token and a client certificate in the request to the service I've tried setting the client certificate for my client in code but wcf seems to ignore it when invoking the service Here is my client's app.config: My requirement is connect c# to sap through sap web service which created via soamanager.
OPEN
