John,

.NET has no concept of static linking - everything is dynamically loaded at runtime. The obj files etc. is purely internal stuff for the compiler that generates the appropriate IL assembly.

Given that .NET dynamically compiles code before it's executed and only loads what actually runs there's not much need to have static compilation/linking.

If you're after a single execution package there are a few tools like ILMerge that can package various .NET binaries into a single executable.

+++ Rick ---

>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.