Justin

@cacosta2018 maybe you should remove ServiceContract Attribute from interfaces, add it on implement class. Or merge two interfaces to one.

zip the files in https://github.com/swagger-api/swagger-ui/tree/master/dist and replace the file https://github.com/abelsilva/swaggerwcf/tree/master/src/SwaggerWcf/www/swagger-ui.zip

 @wuweizi55 as you can see, swagger-ui 3.x support openapi 2.0 & 3.0 so i think your swagger.json is incorrect pls create your own test project, not the SwaggerWcf.Test.Service

Add the following to your config file and change the values accordingly ` `

it is **not** wcf config, it is swaggerwcf config. https://github.com/abelsilva/swaggerwcf/blob/master/README.md **Step 4: Configure WCF services general information** for the service info property, there are three sources (appear in order): 1....

yes, you are right. if you don't use method 1, either method 2, there will be a exception in method 2. if you use method 1, method 2 will not...

there is a workaround, for SecurityDefinitions, follow the Step 4: Configure WCF services general information in readme for security sections, add SwaggerWcfSecurityAttribute to the operations

sorry, my mistake. i mean add .snk to the assembly. [How to: Sign an Assembly with a Strong Name](https://docs.microsoft.com/en-us/dotnet/framework/app-domains/how-to-sign-an-assembly-with-a-strong-name)

by the way, do you know any repository which can parse swagger.json and generate wcf code

my assembly has .snk file, so i can only reference the assembly that has .snk