I don't understand the bin folders in C#.Net solutions

I normally have only one project in my solutions.  Recently, I started a project which was to be a dll.  It resides in a folder c:\clients\Client_name\RMAProcessing (this is where the classes, the sln, suo, and project files are).  The end result is a dll called RMAProcessing.dll.

In order to test the dll, I wanted to add a project to my solution to produce TestDll.exe.  it resides in c:\clients\Client_name\TestDll (this is where the classes and project file are, but, of course, no sln or suo file).

After compiling the solution, I am confused re: the dll.

In c:\clients|Client_name\RmaProcessing\bin\release, the dll is 823 kb
In c:\clients\Client_name\TestDll\bin\release, the dll is 908 kb

Both were created at the same time.

Which version is my deliverable dll?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I suggest to throw them both away (the dll files) and recompile your dll project and import the reference in your test application.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
You must have created a class to test you RMA function, this created the 2nd dll.
Your project dll is the same name as your project name.

I would make sure you don't have any ties between the 2 or that you deploy them together if you need them.

This would happen if you have 2 projects in your solution
Many of my helper DLLs I keep as a seperate project;  I then manually move them to a "dllfolder" under the desired project which is linked into the project.

I adopted this model so that the parent DLL project is more under lock-and-key in safe source.
Also since its part of the file/folders of the desired project someone new can open the project from safesource and not need anything seperate.  If they need changes to said DLL they have to go through the revision process.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.