Another crazy piece of the (even crazier) licensing puzzle: licenses.licx files and lc.exe.
lc.exe is a tool written in .NET by Microsoft, which is used transparently by msbuild when your Visual Studio projects are compiling. Looking inside the assembly's resource strings, we discover it:
Generates a .NET Licenses file and adds it to the manifest of the given assembly
lc /target:TargetAssembly /complist:filename [/outdir:path] [/i:modules] [/v] [/nologo]
/v Verbose output
/nologo Suppress the display of the startup banner
The entry point into this assembly is the Main method of the System.Tools.LicenseCompiler class. Of (arguably) most importance is the /target: switch. This is the name of the assembly into which the compiled resource will be added. In Elsie.Target.exe this would be a resource named "Elsie.Target.exe.licenses", containing a binary stream representation of a serialized .NET object. More to come...
If you add a an empty text file named "licenses.licx" to your project, Visual Studio automatically sets its BuildAction:EmbeddedResource and CopyToOutput:DoNotCopy. It also calls lc.exe before calling csc.exe (yes, I'm a C#-a-holic). It makes the decision based on the .licx extension and you can have as many .licx files as you want in a single project (ok, that may not be true, but why would you want that many? Anyway, it will generate one /complist:[filename.licx] for each licx file in your project)
So what do you type in this/these text file(s)? If you really care, we'll have to make a 3rd installment.