Okay, I've got a good compile and the program runs again.

I forced all of the framework DLLs to have the same version...1.4.0.1, before the version was set at 1.4.*

After compiling all of the framework's DLLs, I put those in one folder, so a compile inside of the framework won't affect the DLLs that the client app is referencing (don't know if this is good policy or not). Also, so the client will only have one path to search.

The client solution has 5 projects. I deleted everything out of the BIN/DEBUG folders for each project, removed all references to the CLSA DLLs, removed the project reference path hint from project properties, and added the references back (pointing the new location in the prev. paragraph).

Rebuilt the client, everything is cool in Texas again.

Don't know which of these steps, made it work. Spent too many hours on it already to try this incrementally (again).

Now I'm trying to get the remoting portion of the data access layer to work....

:)

>I'm working through Rocky Lhotka's CSLA framework, to help me learn C# and .NET. I made a small change to one of the classes in the framework, and now I'm at my wit's end.
>
>When running a client application, which uses the framework, I'm getting an unhandled exception:
>
>"The located assembly's manifest definition with name 'CSLA.Server.DataPortal' does not match the assembly reference.
>