>>Hi everybody,
>>
>>Getting this error and no more info. Googling brings this http://geekswithblogs.net/michelotti/archive/2006/07/31/86754.aspx and others I haven't checked yet.
>>
>>The solution is huge and it didn't have this error before. There are files in different directories with the same name, but I'm not sure why would the problem appear now.
>
>I don't think simply having files of the same name would be a problem - but, as in the link, if the files contain classes with the same name (and using the same namespace) that will cause the error.
>
>
> My changes so far were really minor and I didn't add new files to the solution.
>>
>>Do you have ideas of solving it?
>
>The suggestion to raise the level of the 'output verbosity' (lovely phrase) should identify the conflict....

I don't know. I have it set to Detailed already, changed to Diagnostic with the same result.

Anyway, I found that if I remove FCAdmin_Deploy project from the solution, the build succeeds. As long as I try to include this project back (and it only has proj file), the build fails. I'm running one more experiement now, and if it would fail, I would suggest to remove this project for now at all.

UPDATE. My experiment succeeded, though I still have a bunch of warnings.