Just select the Class Library project type in VS when you start your new
solution.
To test it you'll want to add a Windows.Forms or Console project to your
solution that you can build as a client for your class library. Make it the
startup project for your solution. Whether you use a Windows.Forms project
or a Console project makes absolutely no difference, as long as it exercises
all the methods of all the classes in your library, in accordance with your
test plan. It's only for test purposes. So it's up to you: whatever you
feel happiest with.
You do have a test plan, don't you? :0)
Make sure all your classes in your library are in the same namespace: and
pick your namespace wisely. This is probably more important than having all
the classes in the same assembly. I'd make sure all the assemblies that
make up the library (namespace) were signed, so that they can be deployed to
the GAC. This will help you with versioning.
Of course you could always do things the other way around and start your
solution with the test executable and then include another project for your
library (right click on the solution -Add -new project, and then select
"Class library"). As the Perl guys say, "TMTOWTDI". The end result will be
exactly the same.
HTH
Peter
"Rainer Queck" <Ra****@noemail.noemailwrote in message
news:eA**************@TK2MSFTNGP05.phx.gbl...
Hi,
What would be the best way to develop a class library?
I am planing to develop a couple of classes, needed in our company
enviroment.
These classe will be later used in several projects.
Are there any "how to" links available on how to do that with visual
studio?
Would it be best to have a "Windows" or "Console" application to develop
and test each class and then put it into a library later on or is it
possible to have a Library project that can be included into a test
application and thereby still be debuggable?
Thanks for hint, links and help.
Regards
Rainer Queck
