1>Error: The operation could not be completed

[dannycat]

I'm getting this message "1>Error: The operation could not be completed" in Visual Studiobefore building commences. Does anyone know what's causing this message to appear? (Is it in the dependency checker?) Or how to fix it? The solution goes on to completion but when I try to execute I get a message box claiming that one of the projects within the solution is out of date.

Any help will be appreciated.

[Steven_L_Intel1]

The 1> simply means build thread 1. The other message is evidently coming from some tool being invoked by the build, such as the resource compiler. Please attach a copy of the buildlog.htm from a "rebuild" of the solution.

[Stephen_Sutcliffe1]

Quoting - Steve Lionel (Intel)

The 1> simply means build thread 1. The other message is evidently coming from some tool being invoked by the build, such as the resource compiler. Please attach a copy of the buildlog.htm from a "rebuild" of the solution.

Steve,

I've rebuilt the solution (after installing the latest compiler (11.1.054) and the problem went away. However there is something I was trying to do that may have caused it. Let me try and explain:

My application consists of several projects, only one of whichcreates a dll library, the rest are statics. I am trying to created release and debug versions of both 32 and 64 bit configurations for testing purposes. So far so good. The dll file has the same name irrespective of configuration which means when I copy the files (exe & dll) to my main computer (64-bit) there would be a problem as dll's can't coexist is same folder. (Use separate folders I hear you say!). Trying to be clever I thought that by changing the output name of the dll so that each configuration would have a unique file would be the answer. So I named them thus in the ddl project linker output property:

32-bit Release filename.dll (as original)
32-bit Debug filenameD.dll
64-bit Release filenamex64.dll
64-bit Debug filenamex64D.dll

I modified the Linker input libarary properties accordingly and all builds were successful, however when I tried to run the 32 bit debug version from within VS I got an error message saying that filenameD.dll was missing try reinstalling the application.

This is when I noticed the other message starting to appear.

Firstly should what I was trying to do work?
Or have I missed some other property setting that needs changing?

(I tried copying the filenameD.dll file to the Debug directory of the main application which resulted in a slightly different message that stated the file MSVCR90D.dll could not be found.)

While looking through forum for examples of this problem I noticed that I was not using latest compiler so I bit the bullet and downloaded it and rebuilt everything with original naming and nowall seems well again.


In the meantime I will use the default naming and separate folders.

[Steven_L_Intel1]

You could have different names for the different DLLs, but to do so you need to modify the Linker > General > Output File property. Leave everything else alone. Also, do not change the output path to be the output directory of the main application, as that will cause build problems. I recommend a post-build step that copies the DLL to the project directory for the executable.

I'm unsure what triggered the MSVCR90D error message.