Typed DataSet - why compile to dll?

  • Thread starter Thread starter deko
  • Start date Start date
D

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.
 
I think it is just a feature that does compiling for you.
It is on you whether you need it or not.
 
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.
Click to expand...
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
 
Back
Top