Why do you want to copy your content to the obj directory? Are you
modifying the content in some way as it goes to the obj directory?  If not,
I would just add the content folder as a BindPath and let WiX do all the
heavy lifting grabbing the content and including it into the MSI
appropriately.

On Thu, Sep 20, 2012 at 7:51 PM, Cristian Prieto <kement...@gmail.com>wrote:

> So, in this moment my only options would be:
>
> 1. Copy manually the bitmap files to the temporary directory where wix is
> compiling the msi file, probably in the BeforeBuild Target of the wixproj
> file.
>
> 2. Modify the wxs or wxi file where the dialog specify the images and pass
> a $(var.artdirectory) property (as a DefineConstants) in the MSBuild file.
>
> ==
>
> 3. (This is the ideal way but it will take time), Modify wix.targets, find
> the way where I could specify <Content /> and allow the option to copy
> those Content to the temporary compile directory (obj/longnamehere)... If
> this is not needed maybe it could be using another property like
> <OtherFiles />
>
>
> Am I right or missing something?
>
>
> Cristian Prieto
>
>
> On Fri, Sep 21, 2012 at 1:21 AM, Rob Mensching <r...@robmensching.com>
> wrote:
>
> > Not sure Content items are supported by the wix.targets.
> >
> > On Wed, Sep 19, 2012 at 10:19 PM, Cristian Prieto <kement...@gmail.com
> > >wrote:
> >
> > > Hi Wix user list!
> > >
> > > I've been trying to solve a very small issue with a manually created
> Wix
> > > proj file and resource files...
> > >
> > > My wixproj file (done without Visual Studio but by hand) looks like
> this:
> > >
> > > <?xml version="1.0" encoding="utf-8"?>
> > > <Project DefaultTargets="Build" xmlns="
> > > http://schemas.microsoft.com/developer/msbuild/2003";
> ToolsVersion="4.0">
> > >   <PropertyGroup>
> > >
> > >
> > >
> >
> <ParentDirectory>$([System.IO.Directory]::GetParent('$(MSBuildProjectDirectory)'))</ParentDirectory>
> > >     <ParentDirectory
> > >
> > >
> >
> Condition="!HasTrailingSlash('$(ParentDirectory)')">$(ParentDirectory)\</ParentDirectory>
> > >
> > >     <ArtDirectory Condition="$(ArtDirectory) ==
> > > ''">$(ParentDirectory)art</ArtDirectory>
> > >     <ArtDirectory
> > >
> > >
> >
> Condition="!HasTrailingSlash('$(ArtDirectory)')">$(ArtDirectory)\</ArtDirectory>
> > >   </PropertyGroup>
> > >
> > >   <Import Project="$(WixTargets)" />
> > >
> > >   <!-- blah blah blah, common Wix properties  -->
> > >
> > >   <!-- Art file is here -->
> > >   <ItemGroup>
> > >     <Content Include="$(ArtDirectory)SetupSplash.bmp">
> > >       <Link>SetupSplash.bmp</Link>
> > >     </Content>
> > >   </ItemGroup>
> > >
> > >   <ItemGroup>
> > >     <Compile Include="$(SourcePath)setup.wxs" />
> > >     <Compile Include="$(SourcePath)SetupDialogs.wxs" />
> > >   </ItemGroup>
> > > </Project>
> > >
> > > Ok, I just removed a few lines that were too verbose... but as you may
> > see
> > > it looks ok...
> > >
> > > Now, The problem is with the art... my project structure looks like
> this:
> > >
> > > src
> > >  * setup (the wixproj is here)
> > >  * art (banners and images are here)
> > >
> > > So, in build time the art stuff should be copied to the temporary build
> > > directory for the wix package, I know that I could use a "copy" task
> but
> > I
> > > want to void it.
> > >
> > > I was expecting that using the Content tag the art bmp file would be
> > copied
> > > to the temporary wix build directory, but it is not... I already tried
> > with
> > > OtherFiles tag...
> > >
> > > Is there any way to specify resource files like this without doing the
> > Copy
> > > task manually in MSBuild? am I missing something?
> > >
> > > I know that I could solve all of this just creating the wixproj in
> Visual
> > > Studio and linking manually the files, but I really wanted to avoid it
> > (for
> > > learning purposes).
> > >
> > >
> > > Thanks for any help!
> > >
> > >
> > > Cristian Prieto
> > >
> > >
> >
> ------------------------------------------------------------------------------
> > > Everyone hates slow websites. So do we.
> > > Make your web apps faster with AppDynamics
> > > Download AppDynamics Lite for free today:
> > > http://ad.doubleclick.net/clk;258768047;13503038;j?
> > > http://info.appdynamics.com/FreeJavaPerformanceDownload.html
> > > _______________________________________________
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> >
> >
> >
> > --
> > virtually,
> >
> >    Rob Mensching
> >    http://RobMensching.com LLC
> >
> >
> ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> > http://ad.doubleclick.net/clk;258768047;13503038;j?
> > http://info.appdynamics.com/FreeJavaPerformanceDownload.html
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
> ------------------------------------------------------------------------------
> Got visibility?
> Most devs has no idea what their production app looks like.
> Find out how fast your code is with AppDynamics Lite.
> http://ad.doubleclick.net/clk;262219671;13503038;y?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
virtually,

   Rob Mensching
   http://RobMensching.com LLC
------------------------------------------------------------------------------
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to