Last post Nov 15, 2012 09:24 PM by Haixia Xie - MSFT
Nov 13, 2012 12:09 PM|sbrauen|LINK
I'm lost and need some help. I have a WCF service that I'm running and have defined the config file how I would like it be. However, when I try to run the service via WcfTestClient I see a config file that doesn't even closely resemble mine.
I've unchecked the option to always regenerate the config, but I still keep seeing the wrong config information.
What do I need to do to fix this so the correct information is loaded into the test client?
Nov 15, 2012 02:10 AM|Haixia Xie - MSFT|LINK
Do you mean the config file shown in WCF Test Client? It is a config file of the test client, not your service's config file.
Nov 15, 2012 08:34 AM|sbrauen|LINK
I understand it's a config of the test client, I'm just wondering if it's possible to have it force load a pre-defined config file rather than modifying and saving the client's config file.
This is actually the first part of a two part question I have regarding WCF and client config.
In the actual application that is consuming the WCF service I'm defining the binding config via code and am wondering if there is anyway to validate that the config values being used in code match what I want and are not actually something that WCF has randomly
decided to use.
Nov 15, 2012 09:24 PM|Haixia Xie - MSFT|LINK
I'm just wondering if it's possible to have it force load a pre-defined config file rather than modifying and saving the client's config file.
You can edit the client config content with SvcConfigEditor, but you cannot load another one like you said a pre-defined one. It provides a seamless service testing but not create a real client. It generate a default config for you but you can change it
and persist the modified config by uncheck the Regerate option.
And you can find more information of wcf test client and the features supported by it in MSDN document.
#WCF Test Client (WcfTestClient.exe)