Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>AssemblyVersion</strong></p> <p>Where other assemblies that reference your assembly will look. If this number changes, other assemblies have to update their references to your assembly! The <code>AssemblyVersion</code> is required.</p> <p>I use the format: <em>major.minor</em>. This would result in:</p> <pre><code>[assembly: AssemblyVersion("1.0")] </code></pre> <p><strong>AssemblyFileVersion</strong></p> <p>Used for deployment. You can increase this number for every deployment. It is used by setup programs. Use it to mark assemblies that have the same <code>AssemblyVersion</code>, but are generated from different builds.</p> <p>In Windows, it can be viewed in the file properties.</p> <p>If possible, let it be generated by MSBuild. The AssemblyFileVersion is optional. If not given, the AssemblyVersion is used.</p> <p>I use the format: <em>major.minor.revision.build</em>, where I use revision for development stage (Alpha, Beta, RC and RTM), service packs and hot fixes. This would result in:</p> <pre><code>[assembly: AssemblyFileVersion("1.0.3100.1242")] </code></pre> <p><strong>AssemblyInformationalVersion</strong></p> <p>The Product version of the assembly. This is the version you would use when talking to customers or for display on your website. This version can be a string, like '<em>1.0 Release Candidate</em>'.</p> <p>The Code Analysis will complain about it (CA2243) -- <a href="http://connect.microsoft.com/VisualStudio/feedback/details/796535/the-ca2243-rule-attribute-string-literals-should-parse-correctly-should-not-be-applied-to-assemblyinformationalversionattrubute" rel="noreferrer">reported to Microsoft</a> (not fixed in VS2013).</p> <p>The <code>AssemblyInformationalVersion</code> is optional. If not given, the AssemblyFileVersion is used.</p> <p>I use the format: <em>major.minor [revision as string]</em>. This would result in:</p> <pre><code>[assembly: AssemblyInformationalVersion("1.0 RC1")] </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POWhat are differences between AssemblyVersion, AssemblyFileVersion and AssemblyInformationalVersion?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBraiam
    1. USRémy van Duijkeren
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat are differences between AssemblyVersion, AssemblyFileVersion and AssemblyInformationalVersion?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COA situation: ASM - an assembly project (.DLL/.EXE). SETUP - a setup project. Note that if [SETUP targets ASM] AND [ASM's AssemblyFileVersion NOT updated] AND [ASM's binaries don't change (e.g. only content files updated)]; I've had issues with SETUP not taking the latest binaries (with the latest versions specified). This caused issues with `Application.ProductVersion` and when accessing `AssemblyInformationalVersion` via reflection.
      singulars
      1. PO
      1. USJake Berger
    2. COFor AssemblyFileVersion, "If possible, let it be generated by MSBuild" - Why? You just went on to explain a good reason to manually control it :)
      singulars
      1. PO
      1. USmo.
    3. COThe warning on the AssemblyInformationalVersion format still exists in VS2010 today (May 21, 2013) and your link is dead.
      singulars
      1. PO
      1. USreinierpost
 

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