No libs or objs... you use DLLs.

One class per .cs file. Each project will get compiled into a separate DLL or EXE. You should logically group the .cs files, based on functionality, into their own project.

>Just getting started with .NET and some C# projects. At this point I'm a total newb to c# and .NET, hopefully my questions don't sound too stupid.
>
>I have a few questions on library design so that I can get a better handle on how to properly layout an app.
>
>I notice when I create a Windows control library project it gets compiled into a DLL, I don't see an option to change this into an obj or lib or similar type file, are all c# libraries external dlls or can they be statically linked into the main file at compile time?
>
>Link may not be the right term here, but if you've worked in c you can probably figure out what I mean.
>
>I've also heard that putting too many objects/classes into a c# library can cause troubles, don't know if that is true, but curious if there is an optimum size or number of classes for a library?
>
>I'm still struggling to learn the basics, but I'd like to get my head around the overall layout of a larger app so that I don't have to go back and recode too many times as I progress. Any feed back is appreciated.