A
AC [MVP MCMS]
I'm somewhat of a noob when it comes to WinForm development (all of my work
is within ASP.NET, serivces, and libraries). Currently in the design/scope
stage of a pet project, I'm looking for a bit of advice or direction as to
the best approach. The app is essentially a research & analysis tool where
there will be lots of raw data views with some visualization using charts &
graphs... it's also quite modular. Each "module" will have a specific
role... for instance one would be used to manage the data (import/granular
scrubbing), one for one type of research on the data, another for another
type of research, etc. For example, in Outlook, each module would be
Mail/Contacts/Tasks/Calendar.
I assume the best way is not to create giant panels and show/hide them when
a specific button/menu/tab is clicked as it won't be very performant but
rather create controls and load/dispose when needed.
I plan to use the latest VS2005 RC release as my foundation (using some 3rd
party stuff like Infragistics NetAdvantage... not sure if that matters for
this discussion) and have been reading through Chris Sells' book (granted,
it's for the v1.x Framework, but I'm assuming WinForms v1.x->2.0 is similar
to ASP.NET v1.x->2.0: it's not a complete change to what we're doing, just
makes many tasks easier like the BackgroundWorker for example).
Any pointers on the approach or best practices? I don't think I'm looking
for a SDI/MDI debate... just not sure as to where to go from here.
Thanks in advance...
is within ASP.NET, serivces, and libraries). Currently in the design/scope
stage of a pet project, I'm looking for a bit of advice or direction as to
the best approach. The app is essentially a research & analysis tool where
there will be lots of raw data views with some visualization using charts &
graphs... it's also quite modular. Each "module" will have a specific
role... for instance one would be used to manage the data (import/granular
scrubbing), one for one type of research on the data, another for another
type of research, etc. For example, in Outlook, each module would be
Mail/Contacts/Tasks/Calendar.
I assume the best way is not to create giant panels and show/hide them when
a specific button/menu/tab is clicked as it won't be very performant but
rather create controls and load/dispose when needed.
I plan to use the latest VS2005 RC release as my foundation (using some 3rd
party stuff like Infragistics NetAdvantage... not sure if that matters for
this discussion) and have been reading through Chris Sells' book (granted,
it's for the v1.x Framework, but I'm assuming WinForms v1.x->2.0 is similar
to ASP.NET v1.x->2.0: it's not a complete change to what we're doing, just
makes many tasks easier like the BackgroundWorker for example).
Any pointers on the approach or best practices? I don't think I'm looking
for a SDI/MDI debate... just not sure as to where to go from here.
Thanks in advance...