469,325 Members | 1,524 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,325 developers. It's quick & easy.

Debugging WCF apps

(this was also posted on the MSDN WCF forum but the answers over there are
not so good)
I have a WCF Library hosted by IIS 6 and it all works fine. However I need
to step through the code in the service. But when I hit F5 in VS2008 I get
the following error message. . .

A binding instance has already been associated to listen URI
'http://localhost:8877/VtaxDataService'. If two endpoints want to share the
same ListenUri, they must also share the same binding object instance.

nothing else on my machine is listening on that URI. I thought the message
might be referring to the website hosting my service but I stopped the web
site in IIS and I still get the message. I also stopped IIS and still get
the message My app.config is pasted below.

Why am I getting this message? What is the problem and how can I step
through this code?
Thanks
Gary

<system.serviceModel>
<diagnostics>
<messageLogging logMalformedMessages="true"
logMessagesAtServiceLevel="true"
logMessagesAtTransportLevel="true">
<filters>

</filters>
</messageLogging>
</diagnostics>
<services>
<service behaviorConfiguration="VtaxDataService.Service1Beh avior"
name="VtaxDataService.VtaxDataService">
<endpoint address="" binding="wsHttpBinding"
contract="VtaxDataService.IVtaxDataService" />
<endpoint address="mex" binding="mexHttpBinding"
contract="IMetadataExchange" />
<endpoint binding="basicHttpBinding"
contract="VtaxDataService.IVtaxDataService" />
<host>
<baseAddresses>
<add baseAddress="http://localhost:8877/VtaxDataService" />
</baseAddresses>
</host>
</service>
</services>
<behaviors>
<serviceBehaviors>
<behavior name="VtaxDataService.Service1Behavior">
<!-- To avoid disclosing metadata information,
set the value below to false and remove the metadata endpoint
above before deployment -->
<serviceMetadata httpGetEnabled="True"/>
<!-- To receive exception details in faults for debugging
purposes,
set the value below to true. Set to false before deployment
to avoid disclosing exception information -->
<serviceDebug includeExceptionDetailInFaults="False" />
</behavior>
</serviceBehaviors>
</behaviors>
</system.serviceModel>
Nov 6 '08 #1
7 3797
Hi Gary,

Regarding on the "A binding instance has already been associated to listen
URI " problem you encountered, here are some of my understanding and
suggestion.

1. For the error message above, it indicate that you're trying to startup
an service host/endponit at a URL which is already occuplied. Based on my
understanding, one possible issue is that you create the WCF class library
via "WCF Service LIbrary" project type. And for this kind of project, it
will use the new "WCFTestclient.exe" for you to debug the WCF class library
when you hit F5 key in vs 2008. (This is a new feature of VS2008 for WCF
service library debugging, you do not need to write a dedicated client app
for test the service library). Here is an article describing this:

#WcfSvcHost and WcfTestClient in VS 2008
http://blogs.msdn.com/knom/archive/2...cftestclient-i
n-vs-2008.aspx

And for your scenario, since the service is already started in IIS6, when
you try hiting F5 to start debugging, the WcfTestClient will try host the
endpont again which result to the error at beginning.
2. When you host your WCF service in IIS, I think the reasonable approach
debugging is as below:

** If your WCF host webapplication and the client application which call it
is in the same solution, you can just start F5 debug in client appliation
project, and you should be able to step from client code into server-side
WCF service code.

** If you want to debug the server-side WCF service code only, then you can
manually use "Debug---Attach Process" to attach the IIS worker process
which host the wcf service. For IIS6, it should be the ASP.NET worker
process (w3wp.exe).

if you have anything unclear on this, please feel free to let me know.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we

can improve the support we provide to you. Please feel free to let my
manager know what you think of

the level of service provided. You can send feedback directly to my manager
at: ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/en-us/subs...#notifications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from

the community or a Microsoft Support Engineer within 2 business day is
acceptable. Please note that

each follow up response may take approximately 2 business days as the
support professional working

with you may need further investigation to reach the most efficient
resolution. The offering is not

appropriate for situations that require urgent, real-time or phone-based
interactions. Issues of this

nature are best handled working with a dedicated Microsoft Support Engineer
by contacting Microsoft

Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subs.../aa948874.aspx
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
From: "GaryDean" <gd**********@newsgroup.nospam>
Subject: Debugging WCF apps
Date: Thu, 6 Nov 2008 09:35:58 -0700

(this was also posted on the MSDN WCF forum but the answers over there are
not so good)
I have a WCF Library hosted by IIS 6 and it all works fine. However I need
to step through the code in the service. But when I hit F5 in VS2008 I get
the following error message. . .

A binding instance has already been associated to listen URI
'http://localhost:8877/VtaxDataService'. If two endpoints want to share the
same ListenUri, they must also share the same binding object instance.

nothing else on my machine is listening on that URI. I thought the message
might be referring to the website hosting my service but I stopped the web
site in IIS and I still get the message. I also stopped IIS and still get
the message My app.config is pasted below.

Why am I getting this message? What is the problem and how can I step
through this code?
Thanks
Gary

<system.serviceModel>
<diagnostics>
<messageLogging logMalformedMessages="true"
logMessagesAtServiceLevel="true"
logMessagesAtTransportLevel="true">
<filters>

</filters>
</messageLogging>
</diagnostics>
<services>
<service behaviorConfiguration="VtaxDataService.Service1Beh avior"
name="VtaxDataService.VtaxDataService">
<endpoint address="" binding="wsHttpBinding"
contract="VtaxDataService.IVtaxDataService" />
<endpoint address="mex" binding="mexHttpBinding"
contract="IMetadataExchange" />
<endpoint binding="basicHttpBinding"
contract="VtaxDataService.IVtaxDataService" />
<host>
<baseAddresses>
<add baseAddress="http://localhost:8877/VtaxDataService" />
</baseAddresses>
</host>
</service>
</services>
<behaviors>
<serviceBehaviors>
<behavior name="VtaxDataService.Service1Behavior">
<!-- To avoid disclosing metadata information,
set the value below to false and remove the metadata endpoint
above before deployment -->
<serviceMetadata httpGetEnabled="True"/>
<!-- To receive exception details in faults for debugging
purposes,
set the value below to true. Set to false before deployment
to avoid disclosing exception information -->
<serviceDebug includeExceptionDetailInFaults="False" />
</behavior>
</serviceBehaviors>
</behaviors>
</system.serviceModel>

Nov 7 '08 #2
Steven, thanks for your timely response. I have a problem with each of your
suggestions...

1. As I said in my post, I also thought the reason for the error message
was because IIS was also listening on that url. So I turned IIS completely
off. I stopped the service. I still get the error message. I am thinking
that since IIS is stopped this could not be the reason. No?

2. Regarding attach to process: I am opening up my vs2008 project that
contains my WCF Library project along with my hosting website project. I
bring up the attach to process dialog box. My Transport is "default" my
Qualifier is my machine name. I'm attached to Managed code, native code.
Checkbox for all users is checked. Checkbox for all sesssions is checked.
There is no process listed by the name of W3wp.exe or anything like it.
(also I notice that task manager (using server2003) shows no process by that
name, nor on my Vista system, nor on my XP Pro system)

Regards,
Gary Blakely

""Steven Cheng"" <st*****@online.microsoft.comwrote in message
news:rz*************@TK2MSFTNGHUB02.phx.gbl...
Hi Gary,

Regarding on the "A binding instance has already been associated to listen
URI " problem you encountered, here are some of my understanding and
suggestion.

1. For the error message above, it indicate that you're trying to startup
an service host/endponit at a URL which is already occuplied. Based on my
understanding, one possible issue is that you create the WCF class library
via "WCF Service LIbrary" project type. And for this kind of project, it
will use the new "WCFTestclient.exe" for you to debug the WCF class
library
when you hit F5 key in vs 2008. (This is a new feature of VS2008 for WCF
service library debugging, you do not need to write a dedicated client app
for test the service library). Here is an article describing this:

#WcfSvcHost and WcfTestClient in VS 2008
http://blogs.msdn.com/knom/archive/2...cftestclient-i
n-vs-2008.aspx

And for your scenario, since the service is already started in IIS6, when
you try hiting F5 to start debugging, the WcfTestClient will try host the
endpont again which result to the error at beginning.
2. When you host your WCF service in IIS, I think the reasonable approach
debugging is as below:

** If your WCF host webapplication and the client application which call
it
is in the same solution, you can just start F5 debug in client appliation
project, and you should be able to step from client code into server-side
WCF service code.

** If you want to debug the server-side WCF service code only, then you
can
manually use "Debug---Attach Process" to attach the IIS worker process
which host the wcf service. For IIS6, it should be the ASP.NET worker
process (w3wp.exe).

if you have anything unclear on this, please feel free to let me know.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we

can improve the support we provide to you. Please feel free to let my
manager know what you think of

the level of service provided. You can send feedback directly to my
manager
at: ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/en-us/subs...#notifications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from

the community or a Microsoft Support Engineer within 2 business day is
acceptable. Please note that

each follow up response may take approximately 2 business days as the
support professional working

with you may need further investigation to reach the most efficient
resolution. The offering is not

appropriate for situations that require urgent, real-time or phone-based
interactions. Issues of this

nature are best handled working with a dedicated Microsoft Support
Engineer
by contacting Microsoft

Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subs.../aa948874.aspx
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
From: "GaryDean" <gd**********@newsgroup.nospam>
Subject: Debugging WCF apps
Date: Thu, 6 Nov 2008 09:35:58 -0700

(this was also posted on the MSDN WCF forum but the answers over there are
not so good)
I have a WCF Library hosted by IIS 6 and it all works fine. However I
need
to step through the code in the service. But when I hit F5 in VS2008 I
get
the following error message. . .

A binding instance has already been associated to listen URI
'http://localhost:8877/VtaxDataService'. If two endpoints want to share
the
same ListenUri, they must also share the same binding object instance.

nothing else on my machine is listening on that URI. I thought the
message
might be referring to the website hosting my service but I stopped the web
site in IIS and I still get the message. I also stopped IIS and still get
the message My app.config is pasted below.

Why am I getting this message? What is the problem and how can I step
through this code?
Thanks
Gary

<system.serviceModel>
<diagnostics>
<messageLogging logMalformedMessages="true"
logMessagesAtServiceLevel="true"
logMessagesAtTransportLevel="true">
<filters>

</filters>
</messageLogging>
</diagnostics>
<services>
<service behaviorConfiguration="VtaxDataService.Service1Beh avior"
name="VtaxDataService.VtaxDataService">
<endpoint address="" binding="wsHttpBinding"
contract="VtaxDataService.IVtaxDataService" />
<endpoint address="mex" binding="mexHttpBinding"
contract="IMetadataExchange" />
<endpoint binding="basicHttpBinding"
contract="VtaxDataService.IVtaxDataService" />
<host>
<baseAddresses>
<add baseAddress="http://localhost:8877/VtaxDataService" />
</baseAddresses>
</host>
</service>
</services>
<behaviors>
<serviceBehaviors>
<behavior name="VtaxDataService.Service1Behavior">
<!-- To avoid disclosing metadata information,
set the value below to false and remove the metadata endpoint
above before deployment -->
<serviceMetadata httpGetEnabled="True"/>
<!-- To receive exception details in faults for debugging
purposes,
set the value below to true. Set to false before deployment
to avoid disclosing exception information -->
<serviceDebug includeExceptionDetailInFaults="False" />
</behavior>
</serviceBehaviors>
</behaviors>
</system.serviceModel>

Nov 7 '08 #3
Steven,
Do you have any response on this issue?

I also hit a dead end on the WCF forum on these two issues:

1. Why do I get the two endpoint message when IIS is shutdown
2. Why is there no W3wp.exe process to attach to

Regards,
Gary

""Steven Cheng"" <st*****@online.microsoft.comwrote in message
news:rz*************@TK2MSFTNGHUB02.phx.gbl...
Hi Gary,

Regarding on the "A binding instance has already been associated to listen
URI " problem you encountered, here are some of my understanding and
suggestion.

1. For the error message above, it indicate that you're trying to startup
an service host/endponit at a URL which is already occuplied. Based on my
understanding, one possible issue is that you create the WCF class library
via "WCF Service LIbrary" project type. And for this kind of project, it
will use the new "WCFTestclient.exe" for you to debug the WCF class
library
when you hit F5 key in vs 2008. (This is a new feature of VS2008 for WCF
service library debugging, you do not need to write a dedicated client app
for test the service library). Here is an article describing this:

#WcfSvcHost and WcfTestClient in VS 2008
http://blogs.msdn.com/knom/archive/2...cftestclient-i
n-vs-2008.aspx

And for your scenario, since the service is already started in IIS6, when
you try hiting F5 to start debugging, the WcfTestClient will try host the
endpont again which result to the error at beginning.
2. When you host your WCF service in IIS, I think the reasonable approach
debugging is as below:

** If your WCF host webapplication and the client application which call
it
is in the same solution, you can just start F5 debug in client appliation
project, and you should be able to step from client code into server-side
WCF service code.

** If you want to debug the server-side WCF service code only, then you
can
manually use "Debug---Attach Process" to attach the IIS worker process
which host the wcf service. For IIS6, it should be the ASP.NET worker
process (w3wp.exe).

if you have anything unclear on this, please feel free to let me know.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we

can improve the support we provide to you. Please feel free to let my
manager know what you think of

the level of service provided. You can send feedback directly to my
manager
at: ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/en-us/subs...#notifications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from

the community or a Microsoft Support Engineer within 2 business day is
acceptable. Please note that

each follow up response may take approximately 2 business days as the
support professional working

with you may need further investigation to reach the most efficient
resolution. The offering is not

appropriate for situations that require urgent, real-time or phone-based
interactions. Issues of this

nature are best handled working with a dedicated Microsoft Support
Engineer
by contacting Microsoft

Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subs.../aa948874.aspx
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
From: "GaryDean" <gd**********@newsgroup.nospam>
Subject: Debugging WCF apps
Date: Thu, 6 Nov 2008 09:35:58 -0700

(this was also posted on the MSDN WCF forum but the answers over there are
not so good)
I have a WCF Library hosted by IIS 6 and it all works fine. However I
need
to step through the code in the service. But when I hit F5 in VS2008 I
get
the following error message. . .

A binding instance has already been associated to listen URI
'http://localhost:8877/VtaxDataService'. If two endpoints want to share
the
same ListenUri, they must also share the same binding object instance.

nothing else on my machine is listening on that URI. I thought the
message
might be referring to the website hosting my service but I stopped the web
site in IIS and I still get the message. I also stopped IIS and still get
the message My app.config is pasted below.

Why am I getting this message? What is the problem and how can I step
through this code?
Thanks
Gary

<system.serviceModel>
<diagnostics>
<messageLogging logMalformedMessages="true"
logMessagesAtServiceLevel="true"
logMessagesAtTransportLevel="true">
<filters>

</filters>
</messageLogging>
</diagnostics>
<services>
<service behaviorConfiguration="VtaxDataService.Service1Beh avior"
name="VtaxDataService.VtaxDataService">
<endpoint address="" binding="wsHttpBinding"
contract="VtaxDataService.IVtaxDataService" />
<endpoint address="mex" binding="mexHttpBinding"
contract="IMetadataExchange" />
<endpoint binding="basicHttpBinding"
contract="VtaxDataService.IVtaxDataService" />
<host>
<baseAddresses>
<add baseAddress="http://localhost:8877/VtaxDataService" />
</baseAddresses>
</host>
</service>
</services>
<behaviors>
<serviceBehaviors>
<behavior name="VtaxDataService.Service1Behavior">
<!-- To avoid disclosing metadata information,
set the value below to false and remove the metadata endpoint
above before deployment -->
<serviceMetadata httpGetEnabled="True"/>
<!-- To receive exception details in faults for debugging
purposes,
set the value below to true. Set to false before deployment
to avoid disclosing exception information -->
<serviceDebug includeExceptionDetailInFaults="False" />
</behavior>
</serviceBehaviors>
</behaviors>
</system.serviceModel>

Nov 10 '08 #4
Thanks for your reply Gary,

Yes, I'm still researching on this issue. It does be a bit unexpected that
even you stop IIS service, there is still service occupy the url resource.
I'd like to suggest you try the following approach:

1. stop the website and Apppool(if using IIS 6), for the http port(your wcf
service is configured to listen), use netstat to check whether there is any
other program still using it.

2. If no other program using it, you can try directdly F5 debug on the WCF
service library project, by default the WCFTestclient.exe will help start a
test application which can let you invoke the WCF service.

You can check whether the above approaches works.

For the w3wp.exe, it is the worker process of windows 2003 server(if you're
not using IIS 5 compatible model). If you 're using windows 2003/IIS6 in
IIS5 compiable model or if you're using win xp/IIS5, the worker process
should be "aspnet_wp.exe"

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we

can improve the support we provide to you. Please feel free to let my
manager know what you think of

the level of service provided. You can send feedback directly to my manager
at: ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/en-us/subs...#notifications.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
From: "GaryDean" <gd**********@newsgroup.nospam>
References: <#e**************@TK2MSFTNGP02.phx.gbl>
<rz*************@TK2MSFTNGHUB02.phx.gbl>
Subject: Re: Debugging WCF apps
Date: Mon, 10 Nov 2008 10:42:08 -0700

Steven,
Do you have any response on this issue?

I also hit a dead end on the WCF forum on these two issues:

1. Why do I get the two endpoint message when IIS is shutdown
2. Why is there no W3wp.exe process to attach to

Regards,
Gary

""Steven Cheng"" <st*****@online.microsoft.comwrote in message
news:rz*************@TK2MSFTNGHUB02.phx.gbl...
Hi Gary,

Regarding on the "A binding instance has already been associated to listen
URI " problem you encountered, here are some of my understanding and
suggestion.

1. For the error message above, it indicate that you're trying to startup
an service host/endponit at a URL which is already occuplied. Based on my
understanding, one possible issue is that you create the WCF class library
via "WCF Service LIbrary" project type. And for this kind of project, it
will use the new "WCFTestclient.exe" for you to debug the WCF class
library
when you hit F5 key in vs 2008. (This is a new feature of VS2008 for WCF
service library debugging, you do not need to write a dedicated client app
for test the service library). Here is an article describing this:

#WcfSvcHost and WcfTestClient in VS 2008
http://blogs.msdn.com/knom/archive/2...cftestclient-i
n-vs-2008.aspx

And for your scenario, since the service is already started in IIS6, when
you try hiting F5 to start debugging, the WcfTestClient will try host the
endpont again which result to the error at beginning.


Nov 11 '08 #5
Steven,
Issue # 1
I don't think the problem using the test client in VS2008 is a problem any
more. I was hitting F5 and getting the error I described. But I then
remembered the reccomended way to do this is to browse the .svc file in the
hosting web project, get the screen showing the wsdl url then put that into
a console window running WCFTestClient. That works. However is not of much
use if anything other than simple data types are being used.

Issue #2
I am using Server 2003 with IIS6. There is no aspnet_wp.exe process. no
w3wp.exe. Not in task manager either. I checked several other peoples
machnines running different op sys and same there. I know it is running
because the WCF service works.

Regards,
Gary

""Steven Cheng"" <st*****@online.microsoft.comwrote in message
news:l%****************@TK2MSFTNGHUB02.phx.gbl...
Thanks for your reply Gary,

Yes, I'm still researching on this issue. It does be a bit unexpected that
even you stop IIS service, there is still service occupy the url resource.
I'd like to suggest you try the following approach:

1. stop the website and Apppool(if using IIS 6), for the http port(your
wcf
service is configured to listen), use netstat to check whether there is
any
other program still using it.

2. If no other program using it, you can try directdly F5 debug on the
WCF
service library project, by default the WCFTestclient.exe will help start
a
test application which can let you invoke the WCF service.

You can check whether the above approaches works.

For the w3wp.exe, it is the worker process of windows 2003 server(if
you're
not using IIS 5 compatible model). If you 're using windows 2003/IIS6 in
IIS5 compiable model or if you're using win xp/IIS5, the worker process
should be "aspnet_wp.exe"

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we

can improve the support we provide to you. Please feel free to let my
manager know what you think of

the level of service provided. You can send feedback directly to my
manager
at: ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/en-us/subs...#notifications.

==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
From: "GaryDean" <gd**********@newsgroup.nospam>
References: <#e**************@TK2MSFTNGP02.phx.gbl>
<rz*************@TK2MSFTNGHUB02.phx.gbl>
Subject: Re: Debugging WCF apps
Date: Mon, 10 Nov 2008 10:42:08 -0700

Steven,
Do you have any response on this issue?

I also hit a dead end on the WCF forum on these two issues:

1. Why do I get the two endpoint message when IIS is shutdown
2. Why is there no W3wp.exe process to attach to

Regards,
Gary

""Steven Cheng"" <st*****@online.microsoft.comwrote in message
news:rz*************@TK2MSFTNGHUB02.phx.gbl...
>Hi Gary,

Regarding on the "A binding instance has already been associated to
listen
URI " problem you encountered, here are some of my understanding and
suggestion.

1. For the error message above, it indicate that you're trying to startup
an service host/endponit at a URL which is already occuplied. Based on my
understanding, one possible issue is that you create the WCF class
library
via "WCF Service LIbrary" project type. And for this kind of project, it
will use the new "WCFTestclient.exe" for you to debug the WCF class
library
when you hit F5 key in vs 2008. (This is a new feature of VS2008 for WCF
service library debugging, you do not need to write a dedicated client
app
for test the service library). Here is an article describing this:

#WcfSvcHost and WcfTestClient in VS 2008
http://blogs.msdn.com/knom/archive/2...cftestclient-i
>n-vs-2008.aspx

And for your scenario, since the service is already started in IIS6, when
you try hiting F5 to start debugging, the WcfTestClient will try host the
endpont again which result to the error at beginning.



Nov 11 '08 #6
Hi Gary,

It seems the behaviory you encounter is a bit different from my local
tests. If possible, would you send me a simple solution that contain the
WCFservice library project(a simplified one). I'll perform some test on it
locally. If it works, I think there must be some machine wide configuration
issue which is not specfiic to the WCF service code itself.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we

can improve the support we provide to you. Please feel free to let my
manager know what you think of

the level of service provided. You can send feedback directly to my manager
at: ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/en-us/subs...#notifications.
--------------------
From: "GaryDean" <gd**********@newsgroup.nospam>
References: <#e**************@TK2MSFTNGP02.phx.gbl>
<rz*************@TK2MSFTNGHUB02.phx.gbl>
<OL**************@TK2MSFTNGP06.phx.gbl>
<l#**************@TK2MSFTNGHUB02.phx.gbl>
Subject: Re: Debugging WCF apps
Date: Tue, 11 Nov 2008 15:17:56 -0700
Steven,
Issue # 1
I don't think the problem using the test client in VS2008 is a problem any
more. I was hitting F5 and getting the error I described. But I then
remembered the reccomended way to do this is to browse the .svc file in the
hosting web project, get the screen showing the wsdl url then put that into
a console window running WCFTestClient. That works. However is not of
much
use if anything other than simple data types are being used.

Issue #2
I am using Server 2003 with IIS6. There is no aspnet_wp.exe process. no
w3wp.exe. Not in task manager either. I checked several other peoples
machnines running different op sys and same there. I know it is running
because the WCF service works.

Regards,
Gary

Nov 14 '08 #7
In my last message I said the WCF problem was solved. The remaining issue
is:
Issue #2
I am using Server 2003 with IIS6. There is no aspnet_wp.exe process. no
w3wp.exe. Not in task manager either. I checked several other peoples
machnines running different op sys and same there. I know it is running
because the WCF service works.

In a nutshell, there is no aspnet_wp or w3wp.exe process to attach to. On
any of my machines.
Gary

""Steven Cheng"" <st*****@online.microsoft.comwrote in message
news:xy**************@TK2MSFTNGHUB02.phx.gbl...
Hi Gary,

It seems the behaviory you encounter is a bit different from my local
tests. If possible, would you send me a simple solution that contain the
WCFservice library project(a simplified one). I'll perform some test on
it
locally. If it works, I think there must be some machine wide
configuration
issue which is not specfiic to the WCF service code itself.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we

can improve the support we provide to you. Please feel free to let my
manager know what you think of

the level of service provided. You can send feedback directly to my
manager
at: ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/en-us/subs...#notifications.
--------------------
From: "GaryDean" <gd**********@newsgroup.nospam>
References: <#e**************@TK2MSFTNGP02.phx.gbl>
<rz*************@TK2MSFTNGHUB02.phx.gbl>
<OL**************@TK2MSFTNGP06.phx.gbl>
<l#**************@TK2MSFTNGHUB02.phx.gbl>
Subject: Re: Debugging WCF apps
Date: Tue, 11 Nov 2008 15:17:56 -0700
Steven,
Issue # 1
I don't think the problem using the test client in VS2008 is a problem any
more. I was hitting F5 and getting the error I described. But I then
remembered the reccomended way to do this is to browse the .svc file in
the
hosting web project, get the screen showing the wsdl url then put that
into
a console window running WCFTestClient. That works. However is not of
much
use if anything other than simple data types are being used.

Issue #2
I am using Server 2003 with IIS6. There is no aspnet_wp.exe process. no
w3wp.exe. Not in task manager either. I checked several other peoples
machnines running different op sys and same there. I know it is running
because the WCF service works.

Regards,
Gary

Nov 14 '08 #8

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Development | last post: by
5 posts views Thread by Bruce Schechter | last post: by
6 posts views Thread by gerry | last post: by
23 posts views Thread by keyser_Soze | last post: by
3 posts views Thread by Sathyaish | last post: by
20 posts views Thread by krypto.wizard | last post: by
3 posts views Thread by Randy Magruder | last post: by
1 post views Thread by David C | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
reply views Thread by Gurmeet2796 | last post: by
reply views Thread by harlem98 | last post: by
reply views Thread by listenups61195 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.