webservices returning custom types

[=?Utf-8?B?a2lzaG9y?=]

Hi,
has any one used webservices for returning custom objects other than datasets
like custom classes and their internal classes ?.

What problems you have faced if any ? is there any limitation ?
what are advantages and disadvantages.. please let me know
Kishor

[John Saunders [MVP]]

"kishor" <ki****@discussions.microsoft.comwrote in message
news:8F**********************************@microsof t.com...

Hi,
has any one used webservices for returning custom objects other than
datasets
like custom classes and their internal classes ?.

What problems you have faced if any ? is there any limitation ?
what are advantages and disadvantages.. please let me know

DataSets are exactly what _not_ to return from a web service, at least if
you want the web service to be platform-neutral.

The sort of thing you should aim to pass to and return from a web service is
primitive types, and objects composed of primitive types. This would include
arrays and structs.

Note that any methods on your object cannot be used by the client. Only the
data can be returned or passed. That's why I recommend structs, arrays, etc.
--
--------------------------------------------------------------------------------
John Saunders | MVP – Windows Server System – Connected System Developer

[=?Utf-8?B?RGF2aWQ=?=]

Does WCF bring anything to the table in regard to using .NET types with Web
Services?

"John Saunders [MVP]" wrote:

"kishor" <ki****@discussions.microsoft.comwrote in message
news:8F**********************************@microsof t.com...

Hi,
has any one used webservices for returning custom objects other than
datasets
like custom classes and their internal classes ?.

What problems you have faced if any ? is there any limitation ?
what are advantages and disadvantages.. please let me know

DataSets are exactly what _not_ to return from a web service, at least if
you want the web service to be platform-neutral.

The sort of thing you should aim to pass to and return from a web service is
primitive types, and objects composed of primitive types. This would include
arrays and structs.

Note that any methods on your object cannot be used by the client. Only the
data can be returned or passed. That's why I recommend structs, arrays, etc.
--
--------------------------------------------------------------------------------
John Saunders | MVP – Windows Server System – Connected System Developer

[John Saunders [MVP]]

"David" <Da***@discussions.microsoft.comwrote in message
news:59**********************************@microsof t.com...

Does WCF bring anything to the table in regard to using .NET types with
Web
Services?

No.

"Web Services" is a shorthand for "XML Web Services". It's about sending XML
back and forth, not about sending objects of some .NET-specific type.

In thinking about this subject, ask yourself: what if the client were
written in Java? In JavaScript? In VB6? In Unix Shell Script?

Web Services are meant to be general enough to handle clients of all of
these kinds. But the downside is that it knows nothing at all about types.
Any
such knowledge is the result of a hack - either a customer hack, or a
Microsoft hack. If you don't want your application to be dependent on hacks,
then don't use them. Instead, understand what Web Services are and what they
are not.

..NET Remoting, on the other hand, has little or no interest in being
cross-platform. It is all about remoting .NET types.

My general suggestion is that if cross-platform is off the table, then use
..NET Remoting.
If cross-platform is _on_ the table, either now or in the future, then use
Web Services but understand that you're getting a facade over XML.
--
--------------------------------------------------------------------------------
John Saunders | MVP – Windows Server System – Connected System Developer

[John Saunders [MVP]]

"kishor" <ki****@discussions.microsoft.comwrote in message
news:95**********************************@microsof t.com...

hey John ,
you are right I have not considered your point. but what if I have a c# or
VB.net client or instead of making a platform independent webservide if we
consider microsoft platform what would be scenerio.

I generally recommend the use of .NET Remoting if you have a Microsoft-only
environment.
--
--------------------------------------------------------------------------------
John Saunders | MVP – Windows Server System – Connected System Developer