Dataset designer question

When you use the constructor to create a dataset (XSD), you are creating a "typed dataset". Whenever possible, use typed datasets to create them in code. This data set improves your ability to support your applications. Instead of referring to your data columns by row name, you can refer to them using compiled properties.

Instead...

Dataset1.Datatable1(0)("UserId") = 1

      

        
        
        
      

    

You'll get...

Dataset1.Datatable1(0).UserId = 1

      

        
        
        
      

    

This may not be much, but you eliminate the possibility that somewhere in your code you misspelled your column name. There are many other benefits.

When it comes to performance, you won't notice a difference in runtime performance whether you build them with code or a designer. The designer generates code from your XSD file anyway. However, for very large amounts of data in memory, you are better off designing a custom class to use resources more efficiently.

Short...

• You should use typed datasets instead of untyped datasets because of development / maintenance benefits.
• In most cases, you won't notice a performance problem if you use datasets.