Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Source file pickup issue ??

Status
Not open for further replies.

FeersumEndjinn

Programmer
Jun 1, 2004
7
GB
Hi All,

I noticed something when building a few Wise for Windows 5.21 releases yesterday, which could cause me more than a few problems if it re-occurs.
I had previously built a project and set a property to hold the root folder of all my source files. I rebuilt the project using the command line, and used the /p switch to reset the property holding the source path to another source location(with the same underlying structure). Watching the dialog as it compiled and built, the new source location was reflected in the status of the build process.
However, when I installed one of the releases - I found that not all of the files had picked up files from the location passed in at the command line.
This has far reaching implications for me, as I had intended to automate the whole build process, and pass in a path value to the build tool. If this behaviour happens in other projects, then I'll have no confidence in doing this.

Has anyone else noticed this, or suggest a remedy.
Thanks.
 
Ok, sorry - I think that you can more or less ignore this one. The problem that I'm seeing is not what I described above, and it does indeed pick up source files from the property value as it should.
The problem I am really seeing is this :
One of the files I install is a dll. Before I install this file, I unregister it (and a few other dlls) copy the new version in on top, and it self-registers.
For just one of the dlls, it does not copy over the old version. I can manually copy the new version in with no problem, but apparently the installer can't.
I'm kludging this at the moment by renaming the old version after unregistering it, and then the new version will copy in.
Any suggestions for this one ?? There's nothing odd about the dll, and no processes attached to it or referencing it at install time - I've checked that.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top