Files get built into the release folder only when you have the project set to release mode. You set that by changing the drop down on the VS toolbar next to your "Start Debugging" button. Files in release and debug do not affect each other.

The winforms project should have dll files in the debug folder if you have built the project with a reference to your business object project. The winforms project would be built and you would have an exe file in there for it plus a dll for every other project you have a reference for.

You could try creating a new solution file and adding just the winforms project and the business project to that solution to see if you still have the problem although if there isn't any dependencies to other projects, that shouldn't make any difference.
Tim

>>Is this issue is in your windows project? You should be able to tell by building them separately to determine which is reporting the problem. It should also indicate which assembly has two different versions included. For windows applications there isn't anything in the app.config file that would be an issue; only a web.config for web applications.
>>
>
>I've tried building them separately by right clicking on each project and choosing build in Solution Explorer. The warning never disappeared, so I closed the solution re-opened it and then built them one by one again. The warning displayed when I built the Winforms project.
>
>>What you need to be checking for once you know what assembly is involved is make sure you have the right one under the references node in your solution explorer for that project. Also compare to make sure any dependant projects such as the business object project is using the same one. In other words, if you expand the references node in the solution explorer and click (to highlight) one of the MM references, then look in the properties window at the version number. These need to be the correct one for your installed product and the same.
>>
>
>All common references in my BO and Winforms project are the same version
>
>>Also, you need to open windows explorer and navigate to your project folder, expand the bin folder, and the debug and release folder and see if there are files in there (*.dll) files that are from earlier versions of mm. If they are in there, just delete them. You should be able to delete anything from those directories under the bin folder because they would be re-added when the project is built again.
>>
>
>In my Winforms project there is nothing in the bin folder except the debug folder and in the debug folder there are no dlls.
>
>The Business project has my SamaanSystems.IAS Business.dll with a date of 15th Sep. whereas the Release one has the same file dated 5th May. Could this be the problem?
>
>>The key here is knowing which project and which assembly is the one that is being tagged as an issue. By the way, if you have WPF, Win, And Web projects all in the same solution, which is the startup project? Typically I create a separate solution for different UI's. So I might have a solution for Web that has the web UI plus the business objects, and another solution that is WPF and also includes the same business objects, and so forth. That way the startup project can be set to what ever UI and I don't have any dependencies between web and win or wpf projects.
>>Tim
>
>I've just been testing the WPF and Win projects while I was stuck on the Web one with all the problems I am trying to get past so I just added the projects into the existing one. I just set the startup project to whichever one I want to run. When I release the project it will be without the WPF and Winforms ones.