I'm currently working on an ASP.NET MVC 4.5 application. I'm new to that project as well as WCF and look for a way to properly debug the project using regular breakpoints.
Given are 2 solutions:
ASP.NET Project in: Solution 'Projects'
WCF Project in: Solution 'ProjectService'
in my 1st solution Solution 'Projects' I'm calling the WCF Service the following way:
OperationResult<FindProjectsResult> projectsResult = _projectsWcfService.Call(p => p.FindProjects())
and reference the Wcf in the Web.config file:
<client>
<endpoint address="/ProjectSearch.svc" binding="NamedPipeBinding" name="ProjectServiceNetNamedPipe">
<identity>
<dns value="localhost" />
</identity>
</endpoint>
</client>
The implementation for my Wcf Service is in the 2nd solution Solution 'ProjectService' in my svc file ProjectSearch.svc.cs.
The method I'm calling from solution 1 looks like that:
public OperationResult<FindProjectsResponse> FindProjects()
{
return ProjectManagement.FindProjects();
}
It all works fine.
I need to know, how to debug the WCF Service.
Currently I'm attaching solution 1 to my w3wp.exe process. Though I cannot attach 2 solutions on 1 process.
I would be fine with any help on how to debug the WCF service.
Thanks a lot!!!
Right-click on the solution, you can configure your solution so that you can debug multiple projects via visual studio.
Related
I want to add header information to my Web Service, which I created with basic wizard in Visual Studio 2012.
I simply clicked "Add Service Reference", gave my link and VS created the code itself. Which class do I have to use to pass the header information of my request? Do I have to override the code that VS created automatically?
One more note: If you know another way to add a header to a web service, I would like to use it too. I don't have to use automaticaly created codes. (Although it's handy to use them.)
.Net Framework creates and patches the header on its own in the background, so what I should be doing is to add the username-password header values on web.config, instead of binding it to the post itself.
<client>
<endpoint address="http://ServiceAdd/FService" binding="basicHttpBinding"
bindingConfiguration="FServiceSoapBinding" contract="MyReference.MService_"
name="FServicePort" >
<headers>
<Account>
<username>user</username>
<password>password</password>
</Account>
</headers>
</endpoint>
</client>
my code includes a reference to a webservice, if I want it to run, I need the following section in my app.config:
<client>
<endpoint address="http://123.45.6.78:8080/ASPPO/StartASPPOCallBack"
binding="basicHttpBinding" bindingConfiguration="StartASPPOCallBackPortBinding"
contract="ASPPOCallBack.StartASPPOCallBack" name="StartASPPOCallBackPort" />
</client>
My problem is now, that my code gets called by a SSIS-package and this doesn't have any app.config. So I somehow need to include all the settings I need directy in the code, because I will get a System.Reflection.TargetInvocationException otherwise.
But I actually have no idea where to put it. Can you give me a hint?
If your code is invoked by SSIS (not via external app) you have to modyfy .config file of application which will execute your SSIS package: DTExec.exe, dtshost.exe, devenv.exe, DTExecUI.exe. Here you have more info of appropriate .config locactions: http://www.sqlis.com/post/Where-is-my-appconfig-for-SSIS.aspx
Alternatively you can configure your endpoint in code (not via .config file) similar to http://blogs.msdn.com/b/dbrowne/archive/2010/07/08/how-to-configure-an-ssis-package-to-access-a-web-service-using-wcf.aspx
We run a web application with many (50+) WCF service hosts (Written in C#, running on Win 2008R2/IIS 7.5) for integration with different external vendors. We would like to add another service to each of these hosts for administration. This service can be generic enough that we have a single service definition which we define in some library which we can reference from the integration projects. But is there a way of actually adding the endpoint only in configuration? That is, I would like to avoid adding a .svc file, and only add some rows in the web.config service-section.
I tried adding this to the web.config:
<service name="Contracts.AdminService">
<endpoint address="AdminService" contract="Contracts.IAdminService" binding="basicHttpBinding" />
</service>
This does not work however. If I add a simple .svc file like below it works
<%# ServiceHost Language="C#" Debug="true" Service="Contracts.AdminService" CodeBehind="Contracts.AdminService.cs" %>
However, I would really like to avoid this so that it is less likely that a mistake is made when setting up a new host (we already do a bunch of automatic stuff with the config file, so adding a new service would be trivial). Is this possible? Any drawbacks?
Found the answer myself after a while. The solution is WCF 4's file-less activation. This let me just add this to my web.config:
<serviceHostingEnvironment aspNetCompatibilityEnabled="true"
multipleSiteBindingsEnabled="true">
<serviceActivations>
<add relativeAddress="AdminService.svc" service="Contracts.AdminService"/>
</serviceActivations>
</serviceHostingEnvironment>
After this I can access the service by going to http://<hostname>/<path>/AdminService.svc.
WCF services are hosted in a ServiceHost.
ServiceHosts must be manually created when you are not hosting your WCFs in IIS/WAS, as both IIS/WAS interact with the ServiceHost on your behalf.
What you are basically doing inside the .svc file in IIS is instantianting a new ServiceHost.
Because ServiceHost can only host a single service type, if you plan on creating new types of services for adminsitration, you will need a service host for each of those new types.
So, the short answer to your questions is that you can't just add some information in your web.config for the new services you are going to create, you also need a mechanism to instantiate a ServiceHost.
When added a service reference in vs.net 2008, the url to the wcf service is hardcoded in the generated files.
How can I extract this out to my web.config so I can potentially change the url?
The service reference should automatically generate configuration data, including the endpoint, into your web.config. The URL will be inside the client configuration:
<endpoint address="http://localhost:8732/Service.svc/"
binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_IService"
contract="Service.IService" name="WSHttpBinding_IService" />
When creating a client instance, you also have the option to override the endpoint address in one of the overloaded constructors.
Nothing should be hard-coded in the generated files. Are you sure you're adding a "service reference" and not an old-style "web reference"?
Does anyone know of a good tool to generate the WSDL for a service contract written in C# (i.e. set of methods that are tagged as "[OperationContract]" using WCF)? All the tools I've found work the other way around: create code stubs from a WSDL. I don't want to have to hand-jam a WSDL file. I've found tools for php and J2EE, but not C#. Thanks!
svcutil or just host it quickly and hit the MEX point :)
Easiest thing to do is host the service with a base address setup, and then just hit it from a browser with "?wsdl" appended to the end.
Here's an example of a service configuration with a base address specified. Note this goes in the <configuration><services> element in your config:
<service name="MyServiceName" behaviorConfiguration="MyServiceBehavior">
<host>
<baseAddresses>
<add baseAddress="http://localhost:9000/MyService"/>
</baseAddresses>
</host>
<endpoint address="net.tcp://localhost:9001/MyService"
binding="netTcpBinding"
contract="IMyService"
bindingConfiguration="MyServiceBinding"/>
</service>
Once you get it hosted, just go to http://localhost:9000/MyService?wsdl to see the WSDL definition.
Two ways:
a) Download wsdl file and do below steps:
i) Open visual studio command prompt as an administrator.
ii) Type below command:
wsdl.exe [path To Your WSDL File]
b) With endpoint:
i) Open Visual studio command prompt as an administrator.
ii) type below command:
wsdl.exe http://localhost:9000/MyService