.net – compile the resx files from outside the visual studio

asp.netembedded-resourcenetresx

i have a few resource files (.resx) in a dll.

this dll is referenced from my website, and compiling creates a 'admin.UserControlResource.dll' dll in my \bin\language folder from my 'UserControlResource.de.resx'

now i have some new resource files (the .resx text file), and i want to compile them into new dll's, outside my project, so i will able to just copy those dll's to my production server.

i tried resgen.exe, but that won't allow me to specify the .dll extension for the generated file.

i tried another extension and rename it to .dll, but that didn't work.

this is what i tried:

resgen UserControlResource.de.resx
     al.exe /t:lib /culture:de /embed:"UserControlResource.de.resources" /out:"Dwight.UserControl.resources.dll"

i've seen (in examples) al.exe been executed with and without /t:lib, but both don't work.

what do i mean with 'dont work'?

resgen creates a .resources file

al.exe creates a dll and shows no warnings

but when i copy the dll to the server the default english resources are used, and not the german (de) ones.

Best Answer

Sounds like you want to create satellite assemblies and deploy those satellite assemblies. Theres a good explanation of the process and what you need to consider on MSDN: http://msdn.microsoft.com/en-us/library/sb6a8618%28v=vs.80%29.aspx

Hope that helps :)

Related Solutions

Visual-studio – How to force Visual Studio to regenerate the .designer files for aspx/ascx files

If you open the .aspx file and switch between design view and html view and back it will prompt VS to check the controls and add any that are missing to the designer file.

In VS2013-15 there is a Convert to Web Application command under the Project menu. Prior to VS2013 this option was available in the right-click context menu for as(c/p)x files. When this is done you should see that you now have a *.Designer.cs file available and your controls within the Design HTML will be available for your control.

PS: This should not be done in debug mode, as not everything is "recompiled" when debugging.

Some people have also reported success by (making a backup copy of your .designer.cs file and then) deleting the .designer.cs file. Re-create an empty file with the same name.

There are many comments to this answer that add tips on how best to re-create the designer.cs file.

C# – Embedding DLLs in a compiled executable

I highly recommend to use Costura.Fody - by far the best and easiest way to embed resources in your assembly. It's available as NuGet package.

Install-Package Costura.Fody

After adding it to the project, it will automatically embed all references that are copied to the output directory into your main assembly. You might want to clean the embedded files by adding a target to your project:

Install-CleanReferencesTarget

You'll also be able to specify whether to include the pdb's, exclude certain assemblies, or extracting the assemblies on the fly. As far as I know, also unmanaged assemblies are supported.

Update

Currently, some people are trying to add support for DNX.

Update 2

For the lastest Fody version, you will need to have MSBuild 16 (so Visual Studio 2019). Fody version 4.2.1 will do MSBuild 15. (reference: Fody is only supported on MSBuild 16 and above. Current version: 15)

Related Topic