I have a bunch of installer projects that depend on a custom wixlib for
common UI elements. Everything was working fine until I changed the
project structure on my hard drive, and I noticed that I had to add new
references with new absolute paths to the library file. This is a
problem if I want to have other developers on my team build setup
projects. Everything is under source control, so a certain amount of
the path can/will be hard coded, but the reference is added with a full
path name. In short, I'd like to be able to set a reference path to
..\..\..\lib\MyUI.wixlib instead of d:\projects\6.1\lib\MyUI.wixlib. I
also tried adding the library project to the same solution as a
dependency of my setup and adding a project reference, but then the
setup project didn't pick up the library. Anyone have any idea how to
get around this?
One thought I had was to have a pre-build step on the setup that copied
the library to a local dir, but this would mean that I'd have to
reference the library without a path (which appears to be impossible).
I'll see what else I can come up with in the meantime, and post if I
find a solution.
Thanks!
Chris
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
