It seems some kind of configuration is missing for the webservice in the COM-enabled DLL. Does anyone have any experience with this?Could not find default endpoint element that references contract '' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element.
Type library exporter warning processing ''.
Warning: Type library exporter encountered a type that derives from a generic class and is not marked as ClassInterface(ClassInterfaceType.None)]. Class interfaces cannot be exposed for such types. Consider marking the type with [ClassInterface(ClassInterfaceType.None)] and exposing an explicit interface as the default interface to COM using the ComDefaultInterface attribute.
Comments
I got a little closer to the solution. The problem is caused by the app.config file.
Since a COM enabled DLL is not executable, the CLR cannot find the app.config file...
Regards,
Kurt
I found the solution. \:D/
As mentionned earlier, the problem is caused by the configuration file (app.config).
Instead of using the default constructor for your web service client like below: you should use the following code:
Hopefully, this short topic ends the ](*,)
Regards,
Kurt
However, the solution you outline should work just as well, and not require as much mucking around on the client filesystem.
Tim Larson
I Know the post is pretty old but i have a little problem.
What do i do if i have more then one app.config file?
I cant use the EndpointAddress because i have a https link and not like expected a http.
So does anybody have an idea how i can solve that problem? i cant use the finsql.exe.config because i use more then one config file and EndpointAddress don't work because i have https.
hope somebody could help me.