Yes I replaced YourCompany.Modules.ThingsForSale.ThingsForSaleController" (just referenced it here to simplify this post).
I have a solution set up with the main DNN code project and then the project module below this. If I look at the build output path for the module project it points to ..\..\bin\, and the module manifests itself in the main DNN code bin file. Whole solution builds/rebuilds fine.
If I change it to \bin, a "rebuild all" fails with a load of reference errors starting with "Could not locate the assembly dotnetnuke". However DotNetNuke appears to be referenced in the module project. If I change the build output path back to ..\..\bin\ it works again. Note the module is contained in the desktopmodules folder as expected.
Looking at the solution file there are no project dependencies set up, and the main Dotnetnuke project is set up as single startup project. Configuration properties are set as debug for both projects, the platform for the dotnetnuke project is set up as .NET and the module project as "Any CPU" (no option for .NET it seems).
Cheers!
Alex
p.s.
Just received the Building websites book last week you played a part in (after reading the Pro DotNetNuke 4 book). Very impressed... thanks Michael. I wish I read your book first! I think another book is required that contains the scope of chapters 6 to 9 approx 300-400 pages long, written in the style of "building websites" could make a great DNN programmers reference.