Making Windows Forms Controls Resize (Fill Up) To Screen Resolution C#

[Hamster]

Thanks a lot guys for the pointers... I definitely will not forget what I have read here Will look at Entity Framework, experiment with it, see how far that goes. Not sure if I should put it in now, or I should rework my entire project to this Framework, after the submission date (09 October). Will remove that DataSet business happening, and replace it with a List<> collection.

NO!!!

/throws tantrum

 

[semaphore]

Thanks a lot guys for the pointers... I definitely will not forget what I have read here Will look at Entity Framework, experiment with it, see how far that goes. Not sure if I should put it in now, or I should rework my entire project to this Framework, after the submission date (09 October). Will remove that DataSet business happening, and replace it with a List<> collection.

If you enjoy your anus being abused use entityframework.

 

[Spacerat]

I am with the above on EF. Very heavyweight. I would use a very lightweight ORM that you can just slot in place of all the low-level ADO.NET stuff you have with very low impact. It should be a one-liner to read rows from a DB.

 

[Kilgore_Trout_Redux]

SqlDataReader is really annoying... If you forget to close it in one part of your code, and you need to do a database related operation in another part of your code, the program crashes I should find an alternate to this

You should always be wrapping objects that implement IDisposable in a using clause or a try/finally pattern.

Also using direct ADO.NET is sometimes required when performance is crucial. Stuff like Entity Framework introduces a large performance penalty.

Have a look at using Dapper (Thanks Hamster) for data access.