visual studio 2010 - Where to put content, in Installer project (WiX) or in code project -

so see 2 solutions current problem, wondering pros , cons are, or if there defacto best practices approach.

so current project has number of configuration files, files, , other external content. need content local run , debug application. duplicate content in standard windows installer project. bad idea. moving new setup uses wix installer, , i'm setting project next code project , trying figure best way share resources. see 2 solutions.

one can put resources in wix project , add them links in code project. way know i'm debugging installer.

the other option leave content in code project , path in installer using reference variables.

right seems 6 1 way, half dozen other. persuasive arguments either method?

assuming these configuration , files going installed in same directory executables put them in code project, mark them content, , add reference code project installer project. if you're using wix 3.5 files automatically included in installer along executables, makes writing simple installers easier.

for earlier versions of wix or more complex deployment scenarios (where content files going different directories) still put them in code project you'd use file elements relative path or reference variable in source attribute include the content files code project directory.

i don't believe putting content files in wix installer project directory instead of code project directory ensure version use debug same version installed. can ensured thinking through process of how application finds these content files , making sure right versions found.

so going simple case content in code project , marked content, , installed , loaded same directory executables, matter of setting "copy output directory" "copy always" or "copy if newer" , can sure versions used in debugging , version installed match.