Memory Management and GC

[RG]

I am planning to write an explorer like SDI application utilizing ADO
..NET/ACCESS DB.

There will be a number of different detail views (referencing and updating
data on the db) depending on the selected tree node.

I have tried creating multiple pannels and plant controls on them and show
or hide them depending on the tree node. However, It didn't seem like the
right aproach. The size of the executable was gigantic. Once constucted,
the classes couldn't be destructed(framework handles destruction). Problems
re-querying db.

It seems to me that there must me neeter method. All I am looking for is a
general design aproach to this type of application.

Any suggestions would be greatly appreciated.

Thanks in advance

 

[Cor Ligthert]

RG,

In my opinion should you not search in the way of the management approach
when your program is growing, however asking yourself why your program is
growing.

A good program is not huge. Depending of course that you have no very big
solid datastores in it.

Just my thought

Cor

 

[Guest]

Hi,

The framework will dispose of objects for you but there is nothing to
prevent you from disposing of them yourself. Take a look at smart clients.
Here is an article by Billy Hollis about them.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnreal/html/realworld03232004.asp

Sample code
http://www.dotnetmasters.com/SampleCode/DataCentricSmartClientTechEd.zip

Ken