>As you type the fully qualified namespace, does intellisense find the namespace paths to the correct object?

>Either way, I would try removing all references to the business object project and comment all business object code in the Windows project. Then, compile the business project (by itself), re-add the business assembly reference to the Windows project, check the reference path to be sure it's correct, and try again.

>Another thought... are you putting the business project assembly in the GAC?

>---J

I finally threw away the entire windows project and started over. I got the same error. This made me examine the Business Object project more closely and I discovered that, even though the solution and project were named My Project Business, the resulting dll was named My Project - the same name as the Windows exe. Fixing the name of the Business Object assembly solved the problem.

Now if I only knew how the assembly name ended up different from the project's name...

Thanks for the help!