Click here to Skip to main content
15,868,141 members
Please Sign up or sign in to vote.
3.00/5 (2 votes)
Hi, I encounter a problem that is something like prebuild not executed.
I have a quite large team project in VS2010. Before build, I need to run sereval command to call perl.exe to modify the attribute.cpp file.
I am sure perl is correctly installed ,the file path and command is correct also, because it always works on other guy's computer.
So, I guess maybe some item of configurations in my IDE or environment is not right?

May any guy give me some idea??
Thanks.

We are working on the team project managed by clearcase.
I guess it might be the setting/configuration problem.
I detailly read the build log file.
It is found that no any command was executed..The log file is like this:


1>Target "PreBuildEvent" in file "C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets" from project "D:\xchftt\AS.vcxproj" (target "BuildGenerateSources" depends on it):
Task "Message"
Description: modify
Done executing task "Message".
1>Done building target "PreBuildEvent" in project "AS.vcxproj".
Target "CustomBuild" skipped, due to false condition; ('@(CustomBuild)' != '') was evaluated as ('' != '').

I am just trying to reinstall the .net 4.0..
Posted
Updated 24-Jan-11 22:00pm
v3
Comments
Indivara 24-Jan-11 22:56pm    
Try running them on the command line directly. Use the expanded versions of any macros you may have used.

This is what you can do to figure the problem

1. Watch the Output Window, whether the any exception is thrown below build.
2. Print some messages on the PERL, between few lines to check whether your PERL program is executing perfectly.

We use command batches to these kind of stuffs.
 
Share this answer
 
Comments
Dalek Dave 25-Jan-11 4:19am    
Good Answer.
You said "...it always works on other guy's computer".
How about comparing the other guy's computer development setting/configuration against yours? May be something in your setting is not right. May be you ask the other guy to check your development setting/configuration.
 
Share this answer
 
Comments
Dalek Dave 25-Jan-11 4:20am    
Good Call.
I have found the root cause:
microsoft.common.target file corrupted.

I reinstalled the .net 4.0 and vs2010.
the problem was solved.

Thank you guys!
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900