Code reuse in C#

[Frank Oquendo]

I'm looking for advice from people who are using C# in a production
environment with multiple developers. How do you reuse your code between
projects? Do you organize your class files into namespaces and reuse
them at the source level? Or do you maintain versioned assemblies?

Any asistance you can offer would be greatly appreciated.

--
There are 10 kinds of people. Those who understand binary and those who
don't.

http://code.acadx.com
(Pull the pin to reply)

 

[Martin Dew]

We use projects defined with their own namespaces, an simply include them in
the relevant solutions we need them in.

The source itself is shared via Sourcesafe.

 

[Dmitriy Lapshin [C# / .NET MVP]]

I organize class files into namespaces and try to distribute them among
several projects (say, one project for presentation layer, one for business
logic, one for utility classes etc.)

 

[Robert Hooker]

We use them at a 'binary' level, with loosely versioned assemblies.

 

[Laszlo Szijarto]

we use versioned assemblies --

whatever works for you

 

[Ben Fidge]

Thats pretty much what I do myself. I have a Common
project which is an ever-growing library of utility
classes, with related classes using their own namespace
under the Common namespace.

Ie

Common.EmailTools
Common.LogFiles
Common.WebServiceTools

etc etc

Ben Fidge

 

[Ivan Krivyakov]

We use them at a 'binary' level, with loosely versioned assemblies.

Can you please elaborate on the "loosely versioned"?
Do they have a strong name?
What do they have in AssemblyVersion attribute?

Ivan