Like Jeff mentions, it's probably best to show the code.
"Michael Reinhart" <(E-Mail Removed)> wrote in
message news:566687BD-1575-4508-AE05-(E-Mail Removed)...
> Yes... I'm using it exactly as I am for methods that ARE working...
>
> Any thoughts?
>
> Michael
>
>
> "W.G. Ryan [MVP]" wrote:
>
>> Do you have it marked with the WebMethod attribute? That's the usual
>> culprit. You can use the debugger like you normally would but I'd
>> recommend
>> logging once it's past development.
>> "Michael Reinhart" <(E-Mail Removed)> wrote in
>> message news:8E82C411-9BAC-4DD5-948C-(E-Mail Removed)...
>> > Hi all...
>> >
>> > I'm fairly new to buildling web services in .NET 2.0. Using VB.NET
>> > (2005),
>> > I'm doing something like this in a webmethod:
>> >
>> > - instantiating a 3rd party business object (QuickBooks customers
>> > actually)
>> > - iterating through the collection and adding rows to a DataTable in a
>> > DataSet
>> > - Returning the DataSet ("Return dsCustomers")
>> >
>> > I've got other webmethods that return strings working just fine. I
>> > know
>> > the
>> > code in this method works, because I've tested it inside an ASP.NET
>> > page.
>> >
>> > My questions are:
>> >
>> > 1) if it compiles, why wouldn't the method show up in the service's
>> > ASMX
>> > page?
>> > 2) what's the best way to debug a web service like this?
>> >
>> > Thanks,
>> > Michael
>>
>>
>>
|