Here's the output from my build using the MyModules structure:

------ Build started: Project: Spiratex.SPXCustomers, Configuration: Debug .NET ------

Preparing resources...

Updating references...

Warning: The dependency 'DotNetNuke, Version=3.1.1.33969, Culture=neutral' in project 'Spiratex.SPXCustomers' cannot be copied to the run directory because it would overwrite the reference 'DotNetNuke, Version=3.1.1.32786, Culture=neutral'.

Performing main compilation...

Building satellite assemblies...

------ Build started: Project: Spiratex.SPXCustomers.SqlDataProvider, Configuration: Debug .NET ------

Preparing resources...

Updating references...

Performing main compilation...

Building satellite assemblies...

------ Build started: Project: _DNNStub, Configuration: Debug .NET ------

Preparing resources...

Updating references...

Performing main compilation...

Building satellite assemblies...

---------------------- Done ----------------------

Build: 3 succeeded, 0 failed, 0 skipped


What is up with that warning?  How do I get rid of it?

Ling

I have a similar problem.  With Microsoft's help we traced to a bug in VS2003.
The problem is that VS opens files, then forget's that it has it open, then tries to overwrite a file that is already in use.

My work around is to delete dotnetnuke.dll file before I open the project.  Then for as long as the project stays open in VS, it will work fine.  But if the project is opened with the DLL file exists before the first build, it always fails for me.

Hope this helps

Tom

It seems unlikely that a file open problem is the cause.  This happens even after a reboot of the machine.  There should be no additional files open at that point.  I even deleted the VSWebCache contents before rebooting.

I will still try walking through what you outlined.  I will simply move the DLL out of the way, then try opening the project.  There will be a gob of errors, though, since no DLL exists in the bin.  I am not sure how this will work.  Maybe the actual procedure will make me see something that I am not thinking of right now.

In addition, I do not include the DotNetNuke project in any of my builds.  No way.  I do not want to change that code in any way.  If I leave it totally untouched, then future upgrades will be a snap.  Also, why would anyone want to rebuild that finished project, anyway?  Unless changes to the core are being made.

I did try the steps suggested.  None of them corrected the warning.  I even rebuilt the dll from the DotNetNuke.sln file from the root folder.  Still, no dice.  I blew away VSWebCache, temp files, restarted, etc.  Nothing.  Then...

Solved!

There were three sub-projects that this main project was dependent on.  I went into each of them and rebuilt them (after setting the copy local property to true--why it was false, I do not know!).  Then I rebuilt the main project and the warning message went away.

Suh-weet!!
Ling