title: Pros/Cons of using an assembly as a license file?
body: <p>I was initially going to use a signed serialized xml file to store license details. 
  In planning, more and more has moved into this "license file" which will allow for us to distribute a single application and control available functions via the supplied license file.</p>
  
  <p>The UI and printed reports are co-branded with distributors logos, so it would be good if this could be embedded into the license. I know this could be done with the serialized xml file but I was wondering what are the pros and cons of storing this data in a compiled assembly?</p>
  
  <p>The license generation tool could compile the assembly with the appropriate properties and resources and sign it.  </p>
  
  <p><strong>Update</strong><br>
  From what I can see, using serialized xml or an assembly would be pretty similar. From my point of view, assemblies would allow me to add other resources and leaves some flexibility for the future. As soon as the resources get complicated, xml serialization is a pain.</p>
  
  <p><strong>Update2</strong><br>
  The software only works with our hardware so licence security is not a massive concern. The main aim is to stop the casual user from enabling features that they have not paid for. I would be choosing one over the other for design simplicity!</p>