application design

[bill]

I am migrating a VB6 webclass (IIS application) to a dotNet webforms
project.

There are dozens of designers, class modules, and code modules in this
webclass project, which I will move into VB.NET or CS.NET classes to be
referenced from the web forms project.

I am trying to decide whether to pack all the logic into a single
assembly/dll with numerous classes, or use numerous assemblies with some
classes in each. I guess the answer is somewhere in between, but I don't
want to be arbitrary about it.

There are also dozens of screens in this webclass project, each with an html
template. When designing a web forms project, is it typical to utilize one
web form with many user controls being hidden and moved, or use a number of
web forms to create the interface?

My question is whether there is any conventional wisdom in making these
determinations, and if there are any good, concise references to provide
guidance.

The books and documentation I've read describe how to build the
functionality, but I haven't found much on actually designing the structure
of the whole project.

Thanks
Bill

[Robbe Morris [C# MVP]]

As a rule, your pages and code behind should be in a single assembly.
Optionally, you can create separate assemblies for your business logic
and database layers. That is up to you. There is a "small" performance
hit (very small) with using a large number of separate assemblies. One
reason is the security checks by the framework to ensure the account
attempting to use the assembly has the proper authentication.

Microsoft's performance book recommends fewer assemblies if
the choice is a choice of preference but does not say you shouldn't
use multiple assemblies for your different layers.

There is also nothing wrong with putting all of your classes in the
same assembly even though they may not be in the same layer.
Just remember to keep the functionality of the classes separate
based on the layer they belong in.

--
2005 Microsoft MVP C#
Robbe Morris
http://www.robbemorris.com
http://www.masterado.net/home/listings.aspx

"bill" <be****@datamti .com> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..

I am migrating a VB6 webclass (IIS application) to a dotNet webforms
project.

There are dozens of designers, class modules, and code modules in this
webclass project, which I will move into VB.NET or CS.NET classes to be
referenced from the web forms project.

I am trying to decide whether to pack all the logic into a single
assembly/dll with numerous classes, or use numerous assemblies with some
classes in each. I guess the answer is somewhere in between, but I don't
want to be arbitrary about it.

There are also dozens of screens in this webclass project, each with an
html
template. When designing a web forms project, is it typical to utilize
one
web form with many user controls being hidden and moved, or use a number
of
web forms to create the interface?

My question is whether there is any conventional wisdom in making these
determinations, and if there are any good, concise references to provide
guidance.

The books and documentation I've read describe how to build the
functionality, but I haven't found much on actually designing the
structure
of the whole project.

Thanks
Bill

[Steve C. Orr [MVP, MCSD]]

Here's some information about how you can easily tinker with different
designs and to see what works out best for your application.
http://www.dotnetjunkies.com/Article...D849E4A62.dcik

I used that technique to experiment and generate code conforming to the CSLA
object structure that's defined in this highly recommended book on object
modeling:

Expert One-on-One Visual Basic .NET Business Objects (by Rockford Lhotka)
http://www.amazon.com/exec/obidos/AS...&link_code=as1

or here's the C# version if you prefer:
http://www.amazon.com/exec/obidos/AS...&link_code=as1

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://SteveOrr.net
"bill" <be****@datamti .com> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..

I am migrating a VB6 webclass (IIS application) to a dotNet webforms
project.

There are dozens of designers, class modules, and code modules in this
webclass project, which I will move into VB.NET or CS.NET classes to be
referenced from the web forms project.

I am trying to decide whether to pack all the logic into a single
assembly/dll with numerous classes, or use numerous assemblies with some
classes in each. I guess the answer is somewhere in between, but I don't
want to be arbitrary about it.

There are also dozens of screens in this webclass project, each with an
html
template. When designing a web forms project, is it typical to utilize
one
web form with many user controls being hidden and moved, or use a number
of
web forms to create the interface?

My question is whether there is any conventional wisdom in making these
determinations, and if there are any good, concise references to provide
guidance.

The books and documentation I've read describe how to build the
functionality, but I haven't found much on actually designing the
structure
of the whole project.

Thanks
Bill

[bill]

Thanks for the advice - that's what I was looking for. What is the book you
refer to?

-Bill

"Robbe Morris [C# MVP]" <in**@turnkeyto ols.com> wrote in message
news:eo******** ******@TK2MSFTN GP14.phx.gbl...

As a rule, your pages and code behind should be in a single assembly.
Optionally, you can create separate assemblies for your business logic
and database layers. That is up to you. There is a "small" performance
hit (very small) with using a large number of separate assemblies. One
reason is the security checks by the framework to ensure the account
attempting to use the assembly has the proper authentication.

Microsoft's performance book recommends fewer assemblies if
the choice is a choice of preference but does not say you shouldn't
use multiple assemblies for your different layers.

There is also nothing wrong with putting all of your classes in the
same assembly even though they may not be in the same layer.
Just remember to keep the functionality of the classes separate
based on the layer they belong in.

--
2005 Microsoft MVP C#
Robbe Morris
http://www.robbemorris.com
http://www.masterado.net/home/listings.aspx

"bill" <be****@datamti .com> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..

I am migrating a VB6 webclass (IIS application) to a dotNet webforms
project.

There are dozens of designers, class modules, and code modules in this
webclass project, which I will move into VB.NET or CS.NET classes to be
referenced from the web forms project.

I am trying to decide whether to pack all the logic into a single
assembly/dll with numerous classes, or use numerous assemblies with some
classes in each. I guess the answer is somewhere in between, but I don't want to be arbitrary about it.

There are also dozens of screens in this webclass project, each with an
html
template. When designing a web forms project, is it typical to utilize
one
web form with many user controls being hidden and moved, or use a number
of
web forms to create the interface?

My question is whether there is any conventional wisdom in making these
determinations, and if there are any good, concise references to provide
guidance.

The books and documentation I've read describe how to build the
functionality, but I haven't found much on actually designing the
structure
of the whole project.

Thanks
Bill

[bill]

Thanks - it's been a while since i looked at Visio.
I'll get the book on business objects you refer to.
-Bill
"Steve C. Orr [MVP, MCSD]" <St***@Orr.ne t> wrote in message
news:eo******** ******@TK2MSFTN GP15.phx.gbl...

Here's some information about how you can easily tinker with different
designs and to see what works out best for your application.
http://www.dotnetjunkies.com/Article...D849E4A62.dcik
I used that technique to experiment and generate code conforming to the CSLA object structure that's defined in this highly recommended book on object
modeling:

Expert One-on-One Visual Basic .NET Business Objects (by Rockford Lhotka)
http://www.amazon.com/exec/obidos/AS...&link_code=as1
or here's the C# version if you prefer:
http://www.amazon.com/exec/obidos/AS...&link_code=as1
--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://SteveOrr.net
"bill" <be****@datamti .com> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..

I am migrating a VB6 webclass (IIS application) to a dotNet webforms
project.

There are dozens of designers, class modules, and code modules in this
webclass project, which I will move into VB.NET or CS.NET classes to be
referenced from the web forms project.

I am trying to decide whether to pack all the logic into a single
assembly/dll with numerous classes, or use numerous assemblies with some
classes in each. I guess the answer is somewhere in between, but I don't want to be arbitrary about it.

There are also dozens of screens in this webclass project, each with an
html
template. When designing a web forms project, is it typical to utilize
one
web form with many user controls being hidden and moved, or use a number
of
web forms to create the interface?

My question is whether there is any conventional wisdom in making these
determinations, and if there are any good, concise references to provide
guidance.

The books and documentation I've read describe how to build the
functionality, but I haven't found much on actually designing the
structure
of the whole project.

Thanks
Bill