Setting -inputdir and -output dir to the same deletes objects
Up to Bugs & Problems
Setting -inputdir and -output dir to the same deletes objects
Posted by
Anonymous
at
May 30. 2008
Your instructions suggest using the line:
"c:\Program Files\EQATEC\EQATECProfiler\EQATECHProfilerCmd.exe" -inputdir "$(TargetDir)." -outputdir "$(TargetDir)."
But when this happens, the program deletes the contents of the directory, leaving behind only your runtime dll.
The only way to make this work is to use:
"c:\Program Files\EQATEC\EQATECProfiler\EQATECHProfilerCmd.exe" -inputdir "$(TargetDir)."
copy /Y $(TargetDir)\profiled\*.* $(TargetDir)
"c:\Program Files\EQATEC\EQATECProfiler\EQATECHProfilerCmd.exe" -inputdir "$(TargetDir)." -outputdir "$(TargetDir)."
But when this happens, the program deletes the contents of the directory, leaving behind only your runtime dll.
The only way to make this work is to use:
"c:\Program Files\EQATEC\EQATECProfiler\EQATECHProfilerCmd.exe" -inputdir "$(TargetDir)."
copy /Y $(TargetDir)\profiled\*.* $(TargetDir)
Re: Setting -inputdir and -output dir to the same deletes objects
Posted by
Anonymous
at
May 30. 2008
Re: Setting -inputdir and -output dir to the same deletes objects
Posted by
Richard Flamsholt
at
May 30. 2008
Hi Torin,
Oops. You're absolutely right.
In 1.1 we added a small enhancement, namely that the output-dir would be emptied before writing the new profiled assemblies. This was to ensure that there would not be some obsolete assemblies lying there that could cause problems. (eg an old obsolete "plug-in"-assembly that the app would detect and pick up by mistake)
Frankly we hadn't thought about this bad side-effect. Deleting the output-dir in the case where inputdir=outputdir sure is pretty stupid!
I'm glad you've found a work-around, and thanks for telling us. I've filed this as a bug-report.
Oops. You're absolutely right.
In 1.1 we added a small enhancement, namely that the output-dir would be emptied before writing the new profiled assemblies. This was to ensure that there would not be some obsolete assemblies lying there that could cause problems. (eg an old obsolete "plug-in"-assembly that the app would detect and pick up by mistake)
Frankly we hadn't thought about this bad side-effect. Deleting the output-dir in the case where inputdir=outputdir sure is pretty stupid!
I'm glad you've found a work-around, and thanks for telling us. I've filed this as a bug-report.
Powered by
Ploneboard