<div>
If you want to keep all the business logic in a single assembly/dll, and then re-use that across multiple projects. You only have to maintain 1 set of source code, and the actual assembly. For example, all of your data access in one assembly that 5 different projects can then use. And they all use the same version.<br />
<br />
It makes your code more granular and re-usable, and allows you to fix multiple applications (assuming there is a bug) with one recompile. Also, you can extend functionality to all of them att he same time.
</div>


If you want to keep all the business logic in a single assembly/dll, and then re-use that across multiple projects. You only have to maintain 1 set of source code, and the actual assembly. For example, all of your data access in one assembly that 5 different projects can then use. And they all use the same version.

It makes your code more granular and re-usable, and allows you to fix multiple applications (assuming there is a bug) with one recompile. Also, you can extend functionality to all of them att he same time.

<div>
Nightman Thanks.<br />
<br />
BUT, can you clear the mud just a bit. &nbsp;When you say Business Logic in a single assembly/dll. &nbsp;Are you saying use a DLL or just projects?<br />
<br />
I think you have answered the question, but I am not see your decision point of when this is going to be a DLL or what. &nbsp;I am not trying to be mean with you.<br />
thanks,<br />
Keith
</div>


Nightman Thanks.

BUT, can you clear the mud just a bit.  When you say Business Logic in a single assembly/dll.  Are you saying use a DLL or just projects?

I think you have answered the question, but I am not see your decision point of when this is going to be a DLL or what.  I am not trying to be mean with you.
thanks,
Keith

<div>
<div class="content wysiwyg-content">
What are the factors leading up to the decision to build a DLL instead of just building a method or class for a 2005 Visual Studio C# project? &nbsp; Also, if a DLL is needed can you point me to a good development source document?<br />
<br />
Thanks<br />

</div>
</div>


What are the factors leading up to the decision to build a DLL instead of just building a method or class for a 2005 Visual Studio C# project?   Also, if a DLL is needed can you point me to a good development source document?

Thanks


C# Visual Studio 2005 - When to build a DLL and the main reason to build a DLL

C# is an object-oriented programming language created in conjunction with Microsoft’s .NET framework. Compilation is usually done into the Microsoft Intermediate Language (MSIL), which is then JIT-compiled to native code (and cached) during execution in the Common Language Runtime (CLR).