By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,299 Members | 1,200 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,299 IT Pros & Developers. It's quick & easy.

Need Feedback on using many user controls

P: n/a
I am planning a very large project in vb.net and I want to make it modular.
If the project needs 200-300 forms what do you think about creating a user
control for each of these forms? The main program would dynamically load,
place and dispose each one as required.
Is this a good idea from application size, modularity, performance of slower
PC's, etc.

I am also considering creating all modular forms dynamically. The main
program would only have common controls and act as a parsing / controling
program.

Any feedback would be appreciated.

Gary...
--
-------------------------------------------------------------------------
Gary Kahrau - VP Technology
ka****@monair.com
Stellex Monitor Aerospace Inc.
-------------------------------------------------------------------------

Nov 21 '05 #1
Share this Question
Share on Google+
6 Replies

P: n/a
Does it really need 200 - 300 forms? Are these forms unique, or are many of
them variations of something more general. In other words, I'm wondering if
you could make certain forms more dynamic, and cut the number way down.
Creating 200 - 300 user controls won't make your code really much more
modular.

Scott Swigart
blog.swigartconsulting.com

"Gary Kahrau" wrote:
I am planning a very large project in vb.net and I want to make it modular.
If the project needs 200-300 forms what do you think about creating a user
control for each of these forms? The main program would dynamically load,
place and dispose each one as required.
Is this a good idea from application size, modularity, performance of slower
PC's, etc.

I am also considering creating all modular forms dynamically. The main
program would only have common controls and act as a parsing / controling
program.

Any feedback would be appreciated.

Gary...
--
-------------------------------------------------------------------------
Gary Kahrau - VP Technology
ka****@monair.com
Stellex Monitor Aerospace Inc.
-------------------------------------------------------------------------

Nov 21 '05 #2

P: n/a
Does it really need 200 - 300 forms? Are these forms unique, or are many of
them variations of something more general. In other words, I'm wondering if
you could make certain forms more dynamic, and cut the number way down.
Creating 200 - 300 user controls won't make your code really much more
modular.

Scott Swigart
blog.swigartconsulting.com

"Gary Kahrau" wrote:
I am planning a very large project in vb.net and I want to make it modular.
If the project needs 200-300 forms what do you think about creating a user
control for each of these forms? The main program would dynamically load,
place and dispose each one as required.
Is this a good idea from application size, modularity, performance of slower
PC's, etc.

I am also considering creating all modular forms dynamically. The main
program would only have common controls and act as a parsing / controling
program.

Any feedback would be appreciated.

Gary...
--
-------------------------------------------------------------------------
Gary Kahrau - VP Technology
ka****@monair.com
Stellex Monitor Aerospace Inc.
-------------------------------------------------------------------------

Nov 21 '05 #3

P: n/a
Scott,

That is a good question that I am not sure how to answer!
This is a major ERP system (cust orders, supplier orders, shop
control, scheduling, ERP, DNC,accounting, ship,recv,etc).
Many screens have common themes (look and feel).
It is currently programmed in a char based 4GL of about 500K lines of
code. I want to migrate to a windows client, SQL, and a lower cost DB
like MySql.
I have roughed out some code that creates dynamic form layouts from a
flat definition file. It was suggested to me that using user controls
is more like what .net was designed to do. I want to separate the
modules (MRP, engineering,PO,...) into separate source for
maintainability and allow a number of people to work in different
sections at the same time.
On Wed, 26 Jan 2005 15:47:02 -0800, "Scott Swigart"
<sc***@swigartconsulting.com> wrote:
Does it really need 200 - 300 forms? Are these forms unique, or are many of
them variations of something more general. In other words, I'm wondering if
you could make certain forms more dynamic, and cut the number way down.
Creating 200 - 300 user controls won't make your code really much more
modular.

Scott Swigart
blog.swigartconsulting.com

"Gary Kahrau" wrote:
I am planning a very large project in vb.net and I want to make it modular.
If the project needs 200-300 forms what do you think about creating a user
control for each of these forms? The main program would dynamically load,
place and dispose each one as required.
Is this a good idea from application size, modularity, performance of slower
PC's, etc.

I am also considering creating all modular forms dynamically. The main
program would only have common controls and act as a parsing / controling
program.

Any feedback would be appreciated.

Gary...
--
-------------------------------------------------------------------------
Gary Kahrau - VP Technology
ka****@monair.com
Stellex Monitor Aerospace Inc.
-------------------------------------------------------------------------


-----------------------------------------------------------
Gary Kahrau - VP Technology
ka****@monair.com (W)
gk*****@optonline.net (H)
Stellex Monitor Aerospace Corp.
-----------------------------------------------------------
Nov 21 '05 #4

P: n/a
Scott,

That is a good question that I am not sure how to answer!
This is a major ERP system (cust orders, supplier orders, shop
control, scheduling, ERP, DNC,accounting, ship,recv,etc).
Many screens have common themes (look and feel).
It is currently programmed in a char based 4GL of about 500K lines of
code. I want to migrate to a windows client, SQL, and a lower cost DB
like MySql.
I have roughed out some code that creates dynamic form layouts from a
flat definition file. It was suggested to me that using user controls
is more like what .net was designed to do. I want to separate the
modules (MRP, engineering,PO,...) into separate source for
maintainability and allow a number of people to work in different
sections at the same time.
On Wed, 26 Jan 2005 15:47:02 -0800, "Scott Swigart"
<sc***@swigartconsulting.com> wrote:
Does it really need 200 - 300 forms? Are these forms unique, or are many of
them variations of something more general. In other words, I'm wondering if
you could make certain forms more dynamic, and cut the number way down.
Creating 200 - 300 user controls won't make your code really much more
modular.

Scott Swigart
blog.swigartconsulting.com

"Gary Kahrau" wrote:
I am planning a very large project in vb.net and I want to make it modular.
If the project needs 200-300 forms what do you think about creating a user
control for each of these forms? The main program would dynamically load,
place and dispose each one as required.
Is this a good idea from application size, modularity, performance of slower
PC's, etc.

I am also considering creating all modular forms dynamically. The main
program would only have common controls and act as a parsing / controling
program.

Any feedback would be appreciated.

Gary...
--
-------------------------------------------------------------------------
Gary Kahrau - VP Technology
ka****@monair.com
Stellex Monitor Aerospace Inc.
-------------------------------------------------------------------------


-----------------------------------------------------------
Gary Kahrau - VP Technology
ka****@monair.com (W)
gk*****@optonline.net (H)
Stellex Monitor Aerospace Corp.
-----------------------------------------------------------
Nov 21 '05 #5

P: n/a
Yeah, hard to know for certain without knowing more specifics. A good
approach might be to prototype doing it a couple of different ways. Dynamic
forms, user controls, maybe even code generation (see Kathleen Dollard's book
: http://www.apress.com/book/bookDisplay.html?bID=212)

Sounds fun in any case..

"Gary Kahrau" wrote:
Scott,

That is a good question that I am not sure how to answer!
This is a major ERP system (cust orders, supplier orders, shop
control, scheduling, ERP, DNC,accounting, ship,recv,etc).
Many screens have common themes (look and feel).
It is currently programmed in a char based 4GL of about 500K lines of
code. I want to migrate to a windows client, SQL, and a lower cost DB
like MySql.
I have roughed out some code that creates dynamic form layouts from a
flat definition file. It was suggested to me that using user controls
is more like what .net was designed to do. I want to separate the
modules (MRP, engineering,PO,...) into separate source for
maintainability and allow a number of people to work in different
sections at the same time.
On Wed, 26 Jan 2005 15:47:02 -0800, "Scott Swigart"
<sc***@swigartconsulting.com> wrote:
Does it really need 200 - 300 forms? Are these forms unique, or are many of
them variations of something more general. In other words, I'm wondering if
you could make certain forms more dynamic, and cut the number way down.
Creating 200 - 300 user controls won't make your code really much more
modular.

Scott Swigart
blog.swigartconsulting.com

"Gary Kahrau" wrote:
I am planning a very large project in vb.net and I want to make it modular.
If the project needs 200-300 forms what do you think about creating a user
control for each of these forms? The main program would dynamically load,
place and dispose each one as required.
Is this a good idea from application size, modularity, performance of slower
PC's, etc.

I am also considering creating all modular forms dynamically. The main
program would only have common controls and act as a parsing / controling
program.

Any feedback would be appreciated.

Gary...
--
-------------------------------------------------------------------------
Gary Kahrau - VP Technology
ka****@monair.com
Stellex Monitor Aerospace Inc.
-------------------------------------------------------------------------


-----------------------------------------------------------
Gary Kahrau - VP Technology
ka****@monair.com (W)
gk*****@optonline.net (H)
Stellex Monitor Aerospace Corp.
-----------------------------------------------------------

Nov 21 '05 #6

P: n/a
Yeah, hard to know for certain without knowing more specifics. A good
approach might be to prototype doing it a couple of different ways. Dynamic
forms, user controls, maybe even code generation (see Kathleen Dollard's book
: http://www.apress.com/book/bookDisplay.html?bID=212)

Sounds fun in any case..

"Gary Kahrau" wrote:
Scott,

That is a good question that I am not sure how to answer!
This is a major ERP system (cust orders, supplier orders, shop
control, scheduling, ERP, DNC,accounting, ship,recv,etc).
Many screens have common themes (look and feel).
It is currently programmed in a char based 4GL of about 500K lines of
code. I want to migrate to a windows client, SQL, and a lower cost DB
like MySql.
I have roughed out some code that creates dynamic form layouts from a
flat definition file. It was suggested to me that using user controls
is more like what .net was designed to do. I want to separate the
modules (MRP, engineering,PO,...) into separate source for
maintainability and allow a number of people to work in different
sections at the same time.
On Wed, 26 Jan 2005 15:47:02 -0800, "Scott Swigart"
<sc***@swigartconsulting.com> wrote:
Does it really need 200 - 300 forms? Are these forms unique, or are many of
them variations of something more general. In other words, I'm wondering if
you could make certain forms more dynamic, and cut the number way down.
Creating 200 - 300 user controls won't make your code really much more
modular.

Scott Swigart
blog.swigartconsulting.com

"Gary Kahrau" wrote:
I am planning a very large project in vb.net and I want to make it modular.
If the project needs 200-300 forms what do you think about creating a user
control for each of these forms? The main program would dynamically load,
place and dispose each one as required.
Is this a good idea from application size, modularity, performance of slower
PC's, etc.

I am also considering creating all modular forms dynamically. The main
program would only have common controls and act as a parsing / controling
program.

Any feedback would be appreciated.

Gary...
--
-------------------------------------------------------------------------
Gary Kahrau - VP Technology
ka****@monair.com
Stellex Monitor Aerospace Inc.
-------------------------------------------------------------------------


-----------------------------------------------------------
Gary Kahrau - VP Technology
ka****@monair.com (W)
gk*****@optonline.net (H)
Stellex Monitor Aerospace Corp.
-----------------------------------------------------------

Nov 21 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.