The problem is solved! In the first place, it is normal not be able to step
into the server side code for a OneWay Web method - this is so because
ASP.NET treats OneWay Web methods like the async web methods - that is it
just sends the HTTP request without waiting for the Web method to be
executed. However, I had to be able to debug my OneWay Web method attaching
to the ASP.NET worker process server-side, but unfortunately I still
couldn't hit the break point into my OneWay Web method. The problem now
turned out to be (you won't believe it but it is true) that the debug
information symbols are not loaded. I have couple of plane Class libraries,
which hold the business logic called by the Web service. However, for
Web-based projects, the configuration platform is ".NET" (on default), while
for Class libraries - "Any CPU" (on default). So in order to build the whole
solution, VS2005 builds it as "Mixed Platforms" platform, which obviously
cases the trouble. When I bring back the active platform to be ".NET", then
I am able to hit my breakpoints into the OneWay Web method.
Hope that if someone else experience the same problem, this will help
him/her as well :-)
Regards,
George Jordanov Ivanov
www.givanov.net
"George Jordanov Ivanov" <ge***********@newsgroups.nospam> wrote in message
news:eV**************@TK2MSFTNGP05.phx.gbl...
Folks,
I have a Web service with the two possible types of methods - OneWay and
Request/Response. The problem is while debugging I cannot step into the
OneWay methods, while trying to do the same with Request/Response methods
is working just fine! Have any ideas why this happens? I have Microsoft
.NET framework 2.0 and Visual Studio 2005 as the development platform.
Regards,
George Jordanov Ivanov
