DazMelling
Technical User
Hi
I have a standard application running on site and have added additional functionality in several new dlls.
We have a standard machine for compilation which differs from my development pc. This is causing problems with the new dlls as the paths are added as relative within the vbp.
The new dlls will be placed in a static location.
I can amend the vbp in notepad and change the reference fo rthe new dll to the absolute path. If this is compiled it works correctly on both PCs. The problem is that if the project is saved the absolute path is changed back to a relative path.
Is there anyway to stop this one reference line being changed in the .vbp
Thanks in advance
Daz
I have a standard application running on site and have added additional functionality in several new dlls.
We have a standard machine for compilation which differs from my development pc. This is causing problems with the new dlls as the paths are added as relative within the vbp.
The new dlls will be placed in a static location.
I can amend the vbp in notepad and change the reference fo rthe new dll to the absolute path. If this is compiled it works correctly on both PCs. The problem is that if the project is saved the absolute path is changed back to a relative path.
Is there anyway to stop this one reference line being changed in the .vbp
Thanks in advance
Daz
