Compile errors

When trying to Build Solution, we get a bunch of errors. I just configured this computer yesterday, and just installed Visual Studio 2010. This project, with all the source code works fine and compiles fine for all the other developers (using same solution). So I am assuming I am having a config/setup problem with my project/ visual studio.

Errors:
error CS0006: Metadata file C:\I1Source\Applications\...\...\bin\Debug\...Shared.Common.dll could not be found.
error CS0006: Metadata file C:\I1Source\Applications\...\...\bin\Debug\...ReportRepository.Common.dll could not be found.

The list goes on, but they are all the same error type.

I also tried going to Configuration Manager, and changing the Active Solution Platform from Any CPU to x64 and vice versa. Also unchecked all the checkboxes under Build, and reapplied them. Still no luck.
LVL 8
pzozulkaAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
pzozulkaConnect With a Mentor Author Commented:
The issue was with Build Events. The project solution is shared on a source controlled repository. By downloading the project to my computer, I inherited all the settings for the project into my visual studio environment.

The problem was that all the other developers have two hard drives -- system drive C: and development (SSD) drive D:.

Under project properties > Build Events, there was a Pre-build event command line that involved drive D.

My PC came with only a single drive (SSD) drive C: and the local source repository was downloaded to this drive. Once I changed the path of that command to drive C, everything compiled normally.
0
 
p_davisCommented:
do you have a process that is locking your build up? something that might hold on to a connection to one or more of your dll's or exe's if it isn't shutdown properly... i have had this happen many times.
0
 
pzozulkaAuthor Commented:
No I do not. I also rebooted my computer several times, and made sure to attempt a build before running/opening any other apps.
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
p_davisCommented:
have you tried to clean the solution and rebuild?
0
 
p_davisCommented:
are there third party tool you use that need to be integrated?
0
 
pzozulkaAuthor Commented:
I actually just went to the destination, and found out the dll files are actually not there.

To better understand the compilation errors, I am trying to understand what the compiler is looking for -- does it output those dll files to those directories, or is it actually needing those dll files in order to compile?
0
 
p_davisCommented:
its a reference that its looking for that is not there that should be giving you the errors. 2010 is fairly buggy so your guess is as good as mine as to why it wouldn't produce the files it knows it needs on  a build/debug... especially sense a debug run requires a build.


i usually have to clean the build and then rebuild if i get this errors ... sometimes doing this after closing out of the solution and visual studio.
0
 
pzozulkaAuthor Commented:
We use TortoiseSVN as the only 3rd party solution.

I tried cleaning, and then closing out of visual studio, the building the solution, but no luck.

I'm still a bit confused whether or not the files it's looking for were already suppose to be there, or are OUTPUT files that it was suppose to place there?
0
 
David Johnson, CD, MVPOwnerCommented:
if these dll's are in your debug/release folder then they are built on the fly.. Later on in your code you may have missing references to these dll's

Build each project in your solution separately  and see where it starts to fail.

Did you keep and install all of the extensions that you had in the older visual studio?
0
 
p_davisCommented:
might want to make sure the GAC is in order
0
 
pzozulkaAuthor Commented:
Found own solution.
0
All Courses

From novice to tech pro — start learning today.