473,574 Members | 2,593 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

Web Service debugging ?

Hi All,

Did somebody see the situation when the VS refuses to debug the Web Service
at all? I can't catch why, the initially created Web Service can be debugged
very easy but after some changes in a source code, maybe the source code
becomes bigger that some hidden threshold, the debugger can't enter into
this code anymore. I can use this web service, all methods but can't see in
debugger what's going on. I have already catched this situation several
times beginning a new solution from scratch and adding a web service.
Suddenly debugger loses the web service at all.

Windows 2000 Pro, VS .NET 2003, C#.

Help, please, if somebody knows any possible reason!

Thank you.
Dmitri S.
Nov 13 '05 #1
6 25192
Not sure how relevant it is, but I use this method to debug XML-RPC services
I write in C#:

1. Compile your web app, and bring up the .asmx file in your browser for
your asp.net service to run.

2. Click the Debug -> Processes menu to bring up a list of active processes
on your machine.

3. Double click on the aspnet_wp.exe process, and check "Common Language
Runtime", and click OK.

4. VS.NET will go into debug mode, and you can set your breakpoints etc.
from there.

5. Call your service, etc. and you should get full debug in VS.NET

Regards,

Phil (miseldinedev.c om)

"Dmitri Shvetsov" <ds*******@cox. net> wrote in message
news:P92Pa.263$ Bd5.20@fed1read 01...
Hi All,

Did somebody see the situation when the VS refuses to debug the Web Service at all? I can't catch why, the initially created Web Service can be debugged very easy but after some changes in a source code, maybe the source code
becomes bigger that some hidden threshold, the debugger can't enter into
this code anymore. I can use this web service, all methods but can't see in debugger what's going on. I have already catched this situation several
times beginning a new solution from scratch and adding a web service.
Suddenly debugger loses the web service at all.

Windows 2000 Pro, VS .NET 2003, C#.

Help, please, if somebody knows any possible reason!

Thank you.
Dmitri S.

Nov 13 '05 #2
You know, it's funny but when you create the Web Service from scratch and a
program that uses this Service, you can trace step by step the Web Service
also. It's easy. But after some step the built-in debugger refuses to enter
into the Web Service code at all. That's a problem that I can not
understand.

Regards,
Dmitri.

"Philip Miseldine" <ne**@miseldine .com> wrote in message
news:O1******** ******@TK2MSFTN GP10.phx.gbl...
Not sure how relevant it is, but I use this method to debug XML-RPC services I write in C#:
1. Compile your web app, and bring up the .asmx file in your browser for
your asp.net service to run.
2. Click the Debug -> Processes menu to bring up a list of active processes on your machine.
3. Double click on the aspnet_wp.exe process, and check "Common Language
Runtime", and click OK.
4. VS.NET will go into debug mode, and you can set your breakpoints etc.
from there.
5. Call your service, etc. and you should get full debug in VS.NET
Regards,
Phil (miseldinedev.c om) "Dmitri Shvetsov" <ds*******@cox. net> wrote in message
news:P92Pa.263$ Bd5.20@fed1read 01...
Hi All,
Did somebody see the situation when the VS refuses to debug the Web

Service
at all? I can't catch why, the initially created Web Service can be

debugged
very easy but after some changes in a source code, maybe the source code
becomes bigger that some hidden threshold, the debugger can't enter into
this code anymore. I can use this web service, all methods but can't see

in
debugger what's going on. I have already catched this situation several
times beginning a new solution from scratch and adding a web service.
Suddenly debugger loses the web service at all.

Windows 2000 Pro, VS .NET 2003, C#.

Help, please, if somebody knows any possible reason!

Thank you.
Dmitri S.


Nov 13 '05 #3
Not exactly. Even when I reboot the VS refuses to enter inside this code.
That's still a problem for me.

When I create a new Web Service I can debug it but for some reason the VS
begins to refuse to get into the Web Service methods at all. I tried to
change Configurations, Paths, something else, I'm sure that the project and
the Solution at all are compiled in DEBUG mode, nothing can help. I have a
suspicion that VS has something like a board size after that the built-in
debugger can't work correctly. I met that already several time and ca not
find a reasonable answer. And this occurs ONLY for Web Services, other
applications, class libraries etc can be debugged as usually.

Regards,
Dmitri.

"Mark Pearce" <ev**@bay.com >
What's probably happening is that when you stop debugging, the ASP.NET
worker process is not being terminated. That means that as you start and
stop debugging, you're gathering a bunch of orphaned ASP.NET worker
processes, and the debugger becomes confused about which of these processes is handling your current ASP.NET debug session.

To prevent this behaviour, before you stop debugging you need to ensure that the debugger terminates the ASP.NET worker process rather than just
detaching from it. This option is available on the Processes... dialog
window on the Debug menu. ----------------------------------------------------------------------------
----- Did somebody see the situation when the VS refuses to debug the Web Service at all? I can't catch why, the initially created Web Service can be debugged very easy but after some changes in a source code, maybe the source code
becomes bigger that some hidden threshold, the debugger can't enter into
this code anymore. I can use this web service, all methods but can't see in debugger what's going on. I have already catched this situation several
times beginning a new solution from scratch and adding a web service.
Suddenly debugger loses the web service at all.

Windows 2000 Pro, VS .NET 2003, C#.

Nov 13 '05 #4
Hi Dmitri,

So you can confirm that your environment is set to "Terminate" rather than
"Detach" from the ASP.NET worker process?

If so, you need to investigate other possibilities. When this problem
happens, have you tried setting a breakpoint within a web service method and
seeing whether it's triggered? IOW, is the debugger just refusing to step
into the web service, or is it refusing any interaction at all?

When you run the following command line, does it report that the web service
executable and its PDB file are matched?

dumpbin /PDBPATH:VERBOSE \C:\YourWebServ ice.exe

HTH,

Mark
--
Author of "Comprehens ive VB .NET Debugging"
http://www.apress.com/book/bookDisplay.html?bID=128
"Dmitri Shvetsov" <ds*******@cox. net> wrote in message
news:3GnRa.480$ Ne.92@fed1read0 3...
Not exactly. Even when I reboot the VS refuses to enter inside this code.
That's still a problem for me.

When I create a new Web Service I can debug it but for some reason the VS
begins to refuse to get into the Web Service methods at all. I tried to
change Configurations, Paths, something else, I'm sure that the project and
the Solution at all are compiled in DEBUG mode, nothing can help. I have a
suspicion that VS has something like a board size after that the built-in
debugger can't work correctly. I met that already several time and ca not
find a reasonable answer. And this occurs ONLY for Web Services, other
applications, class libraries etc can be debugged as usually.

Regards,
Dmitri.

"Mark Pearce" <ev**@bay.com >
What's probably happening is that when you stop debugging, the ASP.NET
worker process is not being terminated. That means that as you start and
stop debugging, you're gathering a bunch of orphaned ASP.NET worker
processes, and the debugger becomes confused about which of these processes is handling your current ASP.NET debug session.

To prevent this behaviour, before you stop debugging you need to ensure that the debugger terminates the ASP.NET worker process rather than just
detaching from it. This option is available on the Processes... dialog
window on the Debug menu. ----------------------------------------------------------------------------
----- Did somebody see the situation when the VS refuses to debug the Web Service at all? I can't catch why, the initially created Web Service can be debugged very easy but after some changes in a source code, maybe the source code
becomes bigger that some hidden threshold, the debugger can't enter into
this code anymore. I can use this web service, all methods but can't see in debugger what's going on. I have already catched this situation several
times beginning a new solution from scratch and adding a web service.
Suddenly debugger loses the web service at all.

Windows 2000 Pro, VS .NET 2003, C#.


Nov 13 '05 #5
Hi Mark, thank you for attention.

You know I use usual method to trace something inside this code. Initially
when I just created this code I can debug and go step by step inside this
code. But I wrote here that after some step debugger refuses to wrok inside
this block. I tried to include the code inside this Web Service like

//--------------------------------------------------------------------------
-----------
[Conditional("DE BUG")]
public static void Debug(string msg) {
Console.WriteLi ne(msg);
}

To print my information to console. Nothing. So, I understand that this code
doesn t have any debug info anymore. That's strange. I work with Web
Services for several months and already saw this joke with all my services.
After some size of the code the debugger refuses to work with this service
at all. It seems to me that it has some size limit, maybe something
undocumented in ideology, I don't know.

The main interesting thing for me that I don;t do anything to get this
effect. I remember some moment with this WS when I added another one
WebMethod and after that I could not debug. When I deleted this method - I
could debug again. That's anoying me so much.

That's the report from your query.

dumpbin /PDBPATH:VERBOSE WebServiceUpdat e.dll
Microsoft (R) COFF/PE Dumper Version 7.00.9466
Copyright (C) Microsoft Corporation. All rights reserved.

Dump of file WebServiceUpdat e.dll

File Type: DLL
PDB file found at '.\WebServiceUp date.pdb'

Summary

2000 .reloc
2000 .rsrc
2000 .text

Cool? Everything exists doesn't it?

Regards,
Dmitri.

"Mark Pearce" ev**@bay.com
So you can confirm that your environment is set to "Terminate" rather than
"Detach" from the ASP.NET worker process?

If so, you need to investigate other possibilities. When this problem
happens, have you tried setting a breakpoint within a web service method and seeing whether it's triggered? IOW, is the debugger just refusing to step
into the web service, or is it refusing any interaction at all?

When you run the following command line, does it report that the web service executable and its PDB file are matched?

dumpbin /PDBPATH:VERBOSE \C:\YourWebServ ice.exe

HTH,

Mark
--
Author of "Comprehens ive VB .NET Debugging"
http://www.apress.com/book/bookDisplay.html?bID=128
"Dmitri Shvetsov" <ds*******@cox. net> wrote in message
news:3GnRa.480$ Ne.92@fed1read0 3...
Not exactly. Even when I reboot the VS refuses to enter inside this code.
That's still a problem for me.

When I create a new Web Service I can debug it but for some reason the VS
begins to refuse to get into the Web Service methods at all. I tried to
change Configurations, Paths, something else, I'm sure that the project and the Solution at all are compiled in DEBUG mode, nothing can help. I have a
suspicion that VS has something like a board size after that the built-in
debugger can't work correctly. I met that already several time and ca not
find a reasonable answer. And this occurs ONLY for Web Services, other
applications, class libraries etc can be debugged as usually.

Regards,
Dmitri.

"Mark Pearce" <ev**@bay.com >
What's probably happening is that when you stop debugging, the ASP.NET
worker process is not being terminated. That means that as you start and
stop debugging, you're gathering a bunch of orphaned ASP.NET worker
processes, and the debugger becomes confused about which of these processes
is handling your current ASP.NET debug session.

To prevent this behaviour, before you stop debugging you need to ensure

that
the debugger terminates the ASP.NET worker process rather than just
detaching from it. This option is available on the Processes... dialog
window on the Debug menu.

--------------------------------------------------------------------------

-- -----
Did somebody see the situation when the VS refuses to debug the Web

Service
at all? I can't catch why, the initially created Web Service can be

debugged
very easy but after some changes in a source code, maybe the source code
becomes bigger that some hidden threshold, the debugger can't enter into
this code anymore. I can use this web service, all methods but can't see

in
debugger what's going on. I have already catched this situation several
times beginning a new solution from scratch and adding a web service.
Suddenly debugger loses the web service at all.

Windows 2000 Pro, VS .NET 2003, C#.


Nov 15 '05 #6
Hi Dmitri,

Can you debug this web service with the Dbgclr debugger, or with the
command-line debugger Cordbg? I'm trying to establish whether this is just
an issue with the Visual Studio debugger.

Regards,

Mark
--
Author of "Comprehens ive VB .NET Debugging"
http://www.apress.com/book/bookDisplay.html?bID=128
"Dmitri Shvetsov" <ds*******@cox. net> wrote in message
news:2K7Sa.5837 $Ne.4326@fed1re ad03...
Hi Mark, thank you for attention.

You know I use usual method to trace something inside this code. Initially
when I just created this code I can debug and go step by step inside this
code. But I wrote here that after some step debugger refuses to wrok inside
this block. I tried to include the code inside this Web Service like

//--------------------------------------------------------------------------
-----------
[Conditional("DE BUG")]
public static void Debug(string msg) {
Console.WriteLi ne(msg);
}

To print my information to console. Nothing. So, I understand that this code
doesn t have any debug info anymore. That's strange. I work with Web
Services for several months and already saw this joke with all my services.
After some size of the code the debugger refuses to work with this service
at all. It seems to me that it has some size limit, maybe something
undocumented in ideology, I don't know.

The main interesting thing for me that I don;t do anything to get this
effect. I remember some moment with this WS when I added another one
WebMethod and after that I could not debug. When I deleted this method - I
could debug again. That's anoying me so much.

That's the report from your query.

dumpbin /PDBPATH:VERBOSE WebServiceUpdat e.dll
Microsoft (R) COFF/PE Dumper Version 7.00.9466
Copyright (C) Microsoft Corporation. All rights reserved.

Dump of file WebServiceUpdat e.dll

File Type: DLL
PDB file found at '.\WebServiceUp date.pdb'

Summary

2000 .reloc
2000 .rsrc
2000 .text

Cool? Everything exists doesn't it?

Regards,
Dmitri.

"Mark Pearce" ev**@bay.com
So you can confirm that your environment is set to "Terminate" rather than
"Detach" from the ASP.NET worker process?

If so, you need to investigate other possibilities. When this problem
happens, have you tried setting a breakpoint within a web service method and seeing whether it's triggered? IOW, is the debugger just refusing to step
into the web service, or is it refusing any interaction at all?

When you run the following command line, does it report that the web service executable and its PDB file are matched?

dumpbin /PDBPATH:VERBOSE \C:\YourWebServ ice.exe

HTH,

Mark
--
Author of "Comprehens ive VB .NET Debugging"
http://www.apress.com/book/bookDisplay.html?bID=128
"Dmitri Shvetsov" <ds*******@cox. net> wrote in message
news:3GnRa.480$ Ne.92@fed1read0 3...
Not exactly. Even when I reboot the VS refuses to enter inside this code.
That's still a problem for me.

When I create a new Web Service I can debug it but for some reason the VS
begins to refuse to get into the Web Service methods at all. I tried to
change Configurations, Paths, something else, I'm sure that the project and the Solution at all are compiled in DEBUG mode, nothing can help. I have a
suspicion that VS has something like a board size after that the built-in
debugger can't work correctly. I met that already several time and ca not
find a reasonable answer. And this occurs ONLY for Web Services, other
applications, class libraries etc can be debugged as usually.

Regards,
Dmitri.

"Mark Pearce" <ev**@bay.com >
What's probably happening is that when you stop debugging, the ASP.NET
worker process is not being terminated. That means that as you start and
stop debugging, you're gathering a bunch of orphaned ASP.NET worker
processes, and the debugger becomes confused about which of these processes
is handling your current ASP.NET debug session.

To prevent this behaviour, before you stop debugging you need to ensure

that
the debugger terminates the ASP.NET worker process rather than just
detaching from it. This option is available on the Processes... dialog
window on the Debug menu.

--------------------------------------------------------------------------

-- -----
Did somebody see the situation when the VS refuses to debug the Web

Service
at all? I can't catch why, the initially created Web Service can be

debugged
very easy but after some changes in a source code, maybe the source code
becomes bigger that some hidden threshold, the debugger can't enter into
this code anymore. I can use this web service, all methods but can't see

in
debugger what's going on. I have already catched this situation several
times beginning a new solution from scratch and adding a web service.
Suddenly debugger loses the web service at all.

Windows 2000 Pro, VS .NET 2003, C#.



Nov 15 '05 #7

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

3
1849
by: David Evans | last post by:
Hi I have a service created in VS.NET, which I can install and run quite happily. After teh service is running, I can attach and run the debugger. However, if I set a breakpoint in the IDE the break point is (presumably) hit, but after a long pause there is an error that says "Source code cannot be found" I have tried:
3
4422
by: Ivan G. | last post by:
Hi I'm just playing with Visual Studio 2003 trying to write simple windows service. I've created user service, installer and msi package, my cool service appeared in MMC service list. But when I try to start it following message appears: What's wrong? P.S. Working uder Windows 2003 Server.
3
5718
by: Chuck Bowling | last post by:
Ok, I'm not sure this is a C# question but here goes anyhow... I used this walkthru to create a windows service: ms-help://MS.VSCC.2003/MS.MSDNQTR.2003FEB.1033/vbcon/html/vbwlkwalkthroughcreatingwindowsserviceapplication.htm It appears to install ok but when I try to start it I get this message in a JIT Debugging window: "JIT...
3
1687
by: Sathyaish | last post by:
How do you debug a web service in Visual Studio .NET 2003? To give you some background, I have been programming for some over 8 years now and know how to debug VB, VC++ apps in Visual Studio 6.0 and also know how to debug WinForms apps, Console Apps and ASP.NET apps in Visual Studio ..NET 2003. It occurs that this is the first time I am...
0
1446
by: JT | last post by:
Hi, I've just realized that I'm not as smart as I thought I was. I have no problem creating Windows apps, class libraries, using windows references, etc. But, I absolutely cannot create and use a web service and Windows application pair in VS 2005, even following the walkthrough in Help. There are differences in some of the steps they...
4
3606
by: John Wilmot | last post by:
I have a service that is set up to use remoting. Is there a way that calls from a web page to this service can be debugged in Visual Studio 2005?
5
4710
by: eliasen | last post by:
Hi I have created a Windows Service using C# and .NET2.0. The service is quite simple - right now it doesn't do anything except throwing an exception in the OnStart method. It used to something more, but I couldn't get it working, so I boiled it down to the exception to test. Anyway, the service can be installed using InstalUtil but when...
4
269
by: emanuelanechei | last post by:
These days i'm creating a windows service in c# which reads some data from a file and saves it in a database. The data in the file changes every minute. I am using FileSystemWatcher object which monitors that file for LastWrite event. The problem is that after the reading of file and writing the data in the database the service quits...
5
5566
by: Oriane | last post by:
Hi, I have a .Net Visual Studio solution with one asp.net Web application, which uses a Asp.Net Web service. Both are compiled in debug mode, and both are using the Studio development web server for debugging. I have also add the Web reference to the web service with the "Add Web service in the solution" choice, that is the Web app starts...
0
7814
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main...
0
7736
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it. First, let's disable language...
0
8067
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed. This is as boiled down as I can make it. ...
0
8249
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that...
1
5631
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes...
0
5307
by: conductexam | last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one. At the time of converting from word file to html my equations which are in the word document file was convert...
0
3756
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
1
2252
by: 6302768590 | last post by:
Hai team i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
0
1071
bsmnconsultancy
by: bsmnconsultancy | last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.