Databases
StackOverflow2013
Postsdbo
POGeneration and Compilation of .resources files with MsBuild
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGeneration and Compilation of .resources files with MsBuild
    primarykey
    data
    text
    <p>I have a process where I need to automate the process of generating the satellite assemblies. Specifically this is for WPF and combining Resx and BAML resources.</p> <p>I've got a build script that works, but it requires manual adding of the .resources files I want to combine with the BAML resources. IOW, I have to add to the build script each time I add a .Resx resource. Not cool!</p> <p>Currently I'm running the assembly linker manually and the script looks like this:</p> <pre><code>&lt;Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003"&gt; &lt;!-- Adds the build action 'LocBamlCsv' --&gt; &lt;ItemGroup&gt; &lt;AvailableItemName Include="LocBamlCsv" /&gt; &lt;/ItemGroup&gt; &lt;Target Name="CreateSatelliteAssemblies" DependsOnTargets="$(CreateSatelliteAssembliesDependsOn)"&gt; &lt;!-- Locbaml needs the runtime assemblies in the intermediate dir --&gt; &lt;Copy SourceFiles="$(ProjectDir)..\Tools\LocBaml.exe" DestinationFolder="$(OutputPath)" /&gt; &lt;!-- generate a .resources file for .csv merged output --&gt; &lt;Exec Command="LocBaml /generate ..\..\$(IntermediateOutputPath)$(TargetName).g.$(UICulture).resources /trans:%(LocBamlCsv.FullPath) /out:../../$(IntermediateOutputPath) /cul:%(LocBamlCsv.Culture)" WorkingDirectory="$(OutputPath)" Outputs="$(OutputPath)%(LocBamlCsv.Culture)\$(TargetName).$(UICulture).dll" /&gt; &lt;!-- Generate the resource assembly by merging all .resources files --&gt; &lt;!-- NOTE: Explicitly add any resource files here --&gt; &lt;Exec Command="al /template:$(TargetName).exe /culture:%(LocBamlCsv.Culture) /out:%(LocBamlCsv.Culture)\$(TargetName).resources.dll /embed:$(TargetName).g.%(LocBamlCsv.Culture).resources /embed:$(TargetName).Properties.Resources.%(LocBamlCsv.Culture).resources" WorkingDirectory="$(InterMediateOutputPath)" /&gt; &lt;/Target&gt; &lt;/Project&gt; </code></pre> <p>As mentioned it works. but the last command that calls al would be much easier to work with if there was some way to use wild cards (ie. $(TargetName).*s.%(LocBamlCsv.Culture).resources.</p> <p>I've tried a number of things. Using the build process apparently fires at the wrong time and it ends up failing to find files. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRick Strahl
    1. USRick Strahl
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGeneration and Compilation of .resources files with MsBuild
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou can always write a script that scans the directory for *.res or whatever and generates the build script.
      singulars
      1. POGeneration and Compilation of .resources files with MsBuild
      1. USi_am_jorf
    2. COJeff any links on how to do that? I'm not up to speed on msbuild and I'm not sure how I can get the files and pipe them into the linker path. The other issue is that the <AL> section doesn't work (even with hardcoded filenames - presumably because the timing in the build process where these files are available is wrong) where the explicit command does.
      singulars
      1. POGeneration and Compilation of .resources files with MsBuild
      1. USRick Strahl
    3. COSorry, no. That's why its a comment instead of an answer. :) But you know, perl or python and just add your files to the build script instead of doing it by hand.
      singulars
      1. POGeneration and Compilation of .resources files with MsBuild
      1. USi_am_jorf
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload