How to prevent this?

[WSinc]

It looks like the VS is tying up the EXE longer than it need to - - 

Error    1     general error c101008d: Failed to write the updated manifest to the resource of file "d:\william data\my documents\visual studio 2010\Projects\ransk\Debug\ransk.exe". The process cannot access the file because it is being used by another process.    mt.exe  

[Steven_L_Intel1]

Do you still have a debug session running? This can tie up the executable. mt.exe is the Microsoft Manifest Tool which runs after the linker.

[WSinc]

I usually recompile after making a correction to the source code, then say "restart."

Should I do it differently ? What is the proper order? Kill the debug session first?

[WSinc]

I tried "stop debug" before compiling code and restarting.

But I still sometimes get that message.

[Paul_Curtis]

Here's a suggestion: turn off generation of manifest files, ther're not needed or used for Fortran programs.

[andrew_4619]

billsincl wrote:

I tried "stop debug" before compiling code and restarting.

But I still sometimes get that message.

me too until I got my AntiVirus to exclude by build folders, it blocked the attempt by mt.exe to modify the exe  being built.

[andrew_4619]

Paul Curtis wrote:

Here's a suggestion: turn off generation of manifest files, ther're not needed or used for Fortran programs.

Might you then get UAC issues as a result?

[WSinc]

OK Paul and app 6419.

I will try that. I do have AVAST running, so maybe I can turn that off.

It scans the NEW program I am running, but there aren't any security issues there.

Thanks ! ! 

[Paul_Curtis]

@app4619 - Why would UAC become a problem, esp in the context of manifests?  I have always disabled manifests (compile/link is faster, executables are smaller, etc.).  My fortran executables do not muck about with system settings or catch the attention of UAC, and are distributed to all manner of user machines running XP thru 8.1, never had any UAC or manifest-related issues.

[dboggs]

I hate the manifest file stuff--all those seemingly random warnings. I try to turn the feature off all the time, but sometimes I forget, then the warning pops up again. I would love to find a way to turn it off by default for every new project, but it seems there is none. Why can't Intel set it up for us this way?

[Steven_L_Intel1]

Because if we turned it off a lot of programs wouldn't work if they link to the Microsoft DLLs, which by default projects do now. It's rare for this to be a problem. I agree that some antivirus programs can cause problems with MT because they see an existing EXE being modified, which is something viruses do. The solution there is to exclude your project area from on-access scanning.

[WSinc]

Hi -

I looked at the project/properties, but could not figure out how to turn off the manifest file generation.

There is a sub-folder for "manifest" but it does not show how to disable that completely.

Just a bunch of choices that I could not understand.

any clues ?

[andrew_4619]

Paul Curtis wrote:

@app4619 - Why would UAC become a problem, esp in the context of manifests? 

I wouldn't know, that is why a posed a question. Having now read up on that I would not expect any UAC issues unless you need to prompt the system that the application needs to run as administrator. There are some cases where the manifest is needed as Steve indicates (versioning of runtime dlls etc). Adding the manifest maybe adds one second to my build times...

The only issues I have had with manifests are AV program issues which I currently do not get and when I have in the past a quick exclusion in the AV settings fixes it..

[andrew_4619 · Accepted solution]

billsincl wrote:

Hi -

I looked at the project/properties, but could not figure out how to turn off the manifest file generation.

There is a sub-folder for "manifest" but it does not show how to disable that completely.

Just a bunch of choices that I could not understand.

any clues ?

In solution explorer right click on the project and pick "properties". Under the manifest tool section on sub-section "input output" you will find the embed manifest option.

[WSinc]

OK, app4619 seems to have had a good suggestion, apparently it works.

Just curious - what does a MANIFEST actually do?

How is it useful?

Maybe there is a write-up somewhere ?

[Steven_L_Intel1]

http://msdn.microsoft.com/en-us/library/ms235531.aspx has some explanation. Primarily it is used to identify DLLs used in "side-by-side assemblies". Intel Fortran doesn't use these but Microsoft Visual C++ does, and by default you link to the MSVC DLLs.