What is the optimal way to organize shared .net assemblies in SVN?

Question

We are starting a new SOA project with a lot of shared .net assemblies. The code for these assemblies will be stored in SVN.

In development phase, we would like to

Answer 1

What we did with shared assemblies during development phase (in a project which had loads of these), is that we put them on a network share (N Drive) type of a place, and every developer referenced them from there.

Our build process would always update this share with the latest versions. This way the actual assemblies never had to be kept in source control. Only the code.