Are you saying the path to your release build changes between developers?
I don't use TeamBuild so I don't know how it works but on my system with
just Visual Studio (using VSS for repository) the build path is set on the
project/solution and carried over between check-in/check-out. For
instance, the typical build path when stating a new project within VS
is 'bin\Debug'
or 'bin\Release' which is relative to your project directory (i.e.,
C:\Projects\MyProject\bin\Release\MyProject.exe).
If I change build path to something like 'binary\Debug' or
'binary\Release', this change is imbedded in the project and carried over
to others that might check-out the project.
The nice thing about this line:
<GetAssemblyIdentity AssemblyFiles="$(SolutionDir)YourProject\bin\$(
Configuration)\YourProject.dll">
is that it takes all that into account. It is all relative to
$(SolutionDir) so even if someone checks out the project to a different
location on their hard drive it won't matter. And the $(Configuration)
handles 'Debug' vs 'Release'.
If you are having an issue with the 'bin\' portion (maybe your issue is you
have 'binary\' vs 'bin\') you can simply change that in the above line like
so:
<GetAssemblyIdentity AssemblyFiles="$(SolutionDir)YourProject\binary\$(
Configuration)\YourProject.dll">
If you generate all your output to just 'bin\' regardless of build
configuration you can remove '$(Configuration)' like so:
<GetAssemblyIdentity AssemblyFiles="$(SolutionDir)YourProject\bin\
YourProject.dll">
You can also use the '..' to navigate up the directory tree if needed like
so:
<GetAssemblyIdentity AssemblyFiles="$(SolutionDir)..\
YourSecondProject\bin\$(Configuration)\YourSecondProject.dll">
which would take you up one directory from $(SolutionDir) and then back
down into 'YourSecondProject\bin...'.
HTH
Brian
If you can't explain it simply, you don't understand it well enough. -
Albert Einstein
On Mon, Dec 1, 2014 at 1:32 AM, Jan Suchotzki <jsuchot...@schueco.com>
wrote:
> Brian,
>
> thanks for the immediate response!
>
> Actually the part after SolutionDir is my problem. The binary (its
> something like \bin vs. \Binaries) paths are different. After reading a
> bit about it I'm sure I can change this in TeamBuild, but somehow this
> seems wrong to me. The next time people setting up a new solution
> (without my help) they need to adapt not only the build process, but
> also the setup projects.
> If this is the only possible way, I'll go ahead with this. However, I
> hoped there is a way which is easier to maintain in the future.
>
> As you might have guessed I'm new to wix and its workflows. So maybe
> its just that, that it seems difficult to maintain to me.
>
> Thanks and best regards
> Jan
>
>
>
> Schüco International KG
> Sitz der Gesellschaft und Registergericht: Bielefeld
> Handelsregister: HRA 8135
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
