Vista - "Unspecified error" on compile

One of my projects is giving me the output "Error: The operation could
not be completed. Unspecified error" when I try to compile it (either
on its own, as the solution or as a prerequisite to some other
project).

Searching Google doesn't seem to provide me any help here and it's not
a problem other users are experiencing with the same CSPROJ file, nor
have I always had this problem (though I don't know what on my machine
has changed since I could last compile it, obviously). I can happily
compile several other projects, the problem only seems to affect this
project. I still get the problem if I start VS using the command-line
switch to reset my addons.

Aside from uninstalling and reinstalling Visual Studio, which won't
necessarily help, does anyone have any ideas how I might resolve this
issue, so that I may once again compile this project?

Thanks in advance for any suggestions!


Owen
--
Owen Blacker, Technical team lead, Iris Digital

"Owen Blacker (mySociety)" <owenblacker.projects@xxxxxx> wrote in
message
news:5d9c8089-1df6-4162-bbe4-0973e06b57dd@xxxxxxLet's start with some additional information needed, but not supplied, to
intelligently address your issue.
Although some here have crystal balls, they are not powerful enough the
divine the answers to the following:

What version and edition of Visual Studio?
Which language are you using?
What version/edition of Windows?
What type of project is this symptom observed in?
Is the symptom consistent across multiple projects of the same type, or in
one, only?
Is the symptom consistent across projects of different types?

"Owen Blacker (mySociety)" wrote:
Hi Owen,

Are you having several solutions open? I have seen the unspecified error
when trying to compile a solution containing a database project, while at the
same time having another solution with another database project opened. In
that case the problem was solved by closing the other visual studio solution.

--
Happy Coding!
Morten Wennevik [C# MVP]

On 14 Apr, 18:03, "PvdG42" <p...@xxxxxx> wrote:Sorry.

Visual Studio 2008 v9.0.21022.8 RTM
C#
Windows XP (v5.1 build 2600.xpsp_sp3_gdr.080814-1236 : Service Pack 3)
It's a Web site project (not a Web application)
The problem is only occurring with this one project; other projects
(Web site projects in other solutions and class libraries in this
solution) are building fine.


Owen

On 15 Apr, 07:33, Morten Wennevik [C# MVP]
<MortenWenne...@xxxxxx> wrote:No, this problem occurs both when other VS instances are open and when
this solution is the only instance open.

"Owen Blacker" <owenblacker.projects@xxxxxx> wrote in message
news:3efec0b3-3296-4188-8928-84d9b238ed8f@xxxxxxOK, it's pretty clear that VS is absolved of blame, and that the issue is
within the web site in question. This is hardly "intelligent", but have you
tried deleting all files from the site that were created by the build
process? Candidates would be anything found in debug or release folders
and/or anything with the extension .dll or .exe. The theory is that one or
more such files have become corrupt and are causing the issue, and that a
rebuild after physical removal will not be impeded by the corruption.

On 15 Apr, 13:59, "PvdG42" <p...@xxxxxx> wrote:Well, certainly the unhelpful nature of the error message is Visual
Studio's fault ;o)
I hadn't actually thought of that, but just deleted the entire project
and re-fetched it from Subversion (the same location that other
developers can successfully build from and that our Cruise Control
instance is building quite happily).

I still get precisely the same problem, I'm afraid, despite having
deleted *everything* and restoring the files from a source that works
for other developers.


Owen

Owen Blacker wrote:Maybe they're using VS2008SP1?

Andrew

What's the full path to your sln on your machine?
If it's really long that may be the cause of the problem.

AB
==

On 15 Apr, 15:22, "Andrew Morton" <a...@xxxxxx-press.co.uk.invalid> wrote:Thank you, Andrew. Installing SP1 seems to have made the problem go
away.

Whatever stupid bug it was in VS, SP1 apparently fixes it )


Owen