G
Giulio Petrucci
Hi everybody,
I'm getting confused about "which-name-give-to-what" developing my
applications using Visual Studio.
If I have to develop a "Utilities" library containing some classes for
logging and other classes used for cryptography shall I build a new
Solution named "Utilities"? And how many projects shall I set in it? Let's
suppose I need to have two namespaces "Utilities.Log" and
"Utilities.Cryptography", in the same assembly... shall I create just _one_
project inside the solution? Is there a perfect correspondences
projects-->assemblies? If it's like this, there's no way to keep separated
different namespaces belonging to the same assembly in visual studio (and
it would seem to me quite "silly"...).
What am I missing?
Thanks,
Giulio
I'm getting confused about "which-name-give-to-what" developing my
applications using Visual Studio.
If I have to develop a "Utilities" library containing some classes for
logging and other classes used for cryptography shall I build a new
Solution named "Utilities"? And how many projects shall I set in it? Let's
suppose I need to have two namespaces "Utilities.Log" and
"Utilities.Cryptography", in the same assembly... shall I create just _one_
project inside the solution? Is there a perfect correspondences
projects-->assemblies? If it's like this, there's no way to keep separated
different namespaces belonging to the same assembly in visual studio (and
it would seem to me quite "silly"...).
What am I missing?
Thanks,
Giulio