Assembly design guidance required

  • Thread starter Thread starter Donal McWeeney
  • Start date Start date
D

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
 
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
 
Hi Richard,

Thanks for the pointers...

Donal



Richard A. Lowe said:
Just to address a small part of your question:

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
 
Back
Top