Typed DataSet - why compile to dll?

16 Mar 2006 4:14 AM

deko

I understand that I can generate a strongly typed DataSet using the XSD.exe tool
provided with the .NET Framework SDK. I also understand that I can compile the
class generated by the xsd tool into a dll. (
http://msdn2.microsoft.com/en-us/library/wha85tzb.aspx )

My question is this:

Why would I want a dll rather than the generated class? What can I do with the
dll that I can't do with the class? Are there any advantages of one over the
other? Is there any difference - syntax or otherwise - in accessing the dll vs.
the generated class?

Thanks in advance.

16 Mar 2006 9:31 AM

Miha Markic [MVP C#]

I think it is just a feature that does compiling for you.
It is on you whether you need it or not.

--
Miha Markic [MVP C#]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

Show quote

"deko" <deko@nospam.com> wrote in message
news:kqSdneG8P-VxeIXZnZ2dnUVZ_vmdnZ2d@comcast.com...
>I understand that I can generate a strongly typed DataSet using the XSD.exe
>tool provided with the .NET Framework SDK. I also understand that I can
>compile the class generated by the xsd tool into a dll. (
>http://msdn2.microsoft.com/en-us/library/wha85tzb.aspx )
>
> My question is this:
>
> Why would I want a dll rather than the generated class? What can I do
> with the dll that I can't do with the class? Are there any advantages of
> one over the other? Is there any difference - syntax or otherwise - in
> accessing the dll vs. the generated class?
>
> Thanks in advance.
>
>

17 Mar 2006 1:33 AM

Otis Mukinfus

Show quote

On Wed, 15 Mar 2006 20:14:44 -0800, "deko" <deko@nospam.com> wrote:

>I understand that I can generate a strongly typed DataSet using the XSD.exe tool
>provided with the .NET Framework SDK. I also understand that I can compile the
>class generated by the xsd tool into a dll. (
>http://msdn2.microsoft.com/en-us/library/wha85tzb.aspx )
>
>My question is this:
>
>Why would I want a dll rather than the generated class? What can I do with the
>dll that I can't do with the class? Are there any advantages of one over the
>other? Is there any difference - syntax or otherwise - in accessing the dll vs.
>the generated class?
>
>Thanks in advance.
>

Suppose you want to access the same data from more than one application. If you
have the dll you can reference it in another application and use it there
(portability).

Otis Mukinfus
http://www.arltex.com
http://www.tomchilders.com