Assembly design guidance required

[Donal McWeeney]

Hi,

Are there any good guidance white papers out there on the best way to design
and build assemblys in VS.Net that would cover the following questions I
have and requirements I know of:

The assembly(s) I build must be installed in the GAC.

My assembly(s) needs to include the following:
- my own class/utility librarary code
- custom web controls
- custom web parts
- support localization

Should I include all the above in the one assembly dll or partition based on
logical boundarys - partitioning would then create dependencys between
assemblys.

If I was to create in one assembly what is the best way to structure the
project within VS.Net - should I name files based on namespaces - or
separate files in subfolders based on namespaces.

Other problems I am likley to run into.

Thanks

Donal

[Richard A. Lowe]

Just to address a small part of your question:

If I was to create in one assembly what is the best way to structure the
project within VS.Net - should I name files based on namespaces - or
separate files in subfolders based on namespaces.
C# in VS.NET will assign namespaces based on folders, so use that feature.

You should check out FXCop which can help you since it's a very pedantic
'best practices' checker (you can even add your own rules).
http://www.gotdotnet.com/team/fxcop/

Richard
--
C# jiggery-pokery:
http://blogs.geekdojo.net/Richard
"Donal McWeeney" <do************@NO-SP-AM.aimware.com> wrote in message
news:O0**************@TK2MSFTNGP12.phx.gbl... Hi,

Are there any good guidance white papers out there on the best way to design and build assemblys in VS.Net that would cover the following questions I
have and requirements I know of:

The assembly(s) I build must be installed in the GAC.

My assembly(s) needs to include the following:
- my own class/utility librarary code
- custom web controls
- custom web parts
- support localization

Should I include all the above in the one assembly dll or partition based on logical boundarys - partitioning would then create dependencys between
assemblys.

If I was to create in one assembly what is the best way to structure the
project within VS.Net - should I name files based on namespaces - or
separate files in subfolders based on namespaces.

Other problems I am likley to run into.

Thanks

Donal

[Donal McWeeney]

Hi Richard,

Thanks for the pointers...

Donal

"Richard A. Lowe" <ch*****@yumspamyumYahoo.com> wrote in message
news:eB**************@TK2MSFTNGP10.phx.gbl...

Just to address a small part of your question:

If I was to create in one assembly what is the best way to structure the
project within VS.Net - should I name files based on namespaces - or
separate files in subfolders based on namespaces.
C# in VS.NET will assign namespaces based on folders, so use that feature.

You should check out FXCop which can help you since it's a very pedantic
'best practices' checker (you can even add your own rules).
http://www.gotdotnet.com/team/fxcop/

Richard
--
C# jiggery-pokery:
http://blogs.geekdojo.net/Richard
"Donal McWeeney" <do************@NO-SP-AM.aimware.com> wrote in message
news:O0**************@TK2MSFTNGP12.phx.gbl...

Hi,

Are there any good guidance white papers out there on the best way to

design

and build assemblys in VS.Net that would cover the following questions I
have and requirements I know of:

The assembly(s) I build must be installed in the GAC.

My assembly(s) needs to include the following:
- my own class/utility librarary code
- custom web controls
- custom web parts
- support localization

Should I include all the above in the one assembly dll or partition

based on

logical boundarys - partitioning would then create dependencys between
assemblys.

If I was to create in one assembly what is the best way to structure the
project within VS.Net - should I name files based on namespaces - or
separate files in subfolders based on namespaces.

Other problems I am likley to run into.

Thanks

Donal