Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There seems to be multiple possible approaches to this problem. The first and probably preferred solution would be to install a build server and only distribute builds generated there to customers. This has the advantage that you never ship uncommitted changes. By using MSBuild, NAnt or some other task-based build tool the entire process is very flexible. I was able to install TeamCity and get the first couple of builds up and running with very little effort, but there are other good build servers too. This really should be your solution.</p> <p>If you for some reason insist that it's okay to distribute developer builds to clients ;) then you'll need a local solution.</p> <p>A fairly easy solution would be to use the built-in support for auto-incrementing the build number of an assembly:</p> <pre><code>// major.minor.build.revision [assembly:AssemblyVersion("1.2.*")] </code></pre> <p>The <code>*</code> makes the build number auto-increment every time you compile (and there are changes). The revision number is a random number. From here you can either keep track of the association to the Mercurial id by saving both pieces of information, e.g. by posting it to some internal web solution or whatever fits your particular needs, or update the generated assembly. I'd suspect you could use PostSharp or Mono.Cecil do rewrite the assembly, e.g. by patching the revision number to be the id. If your assemblies are signed the rewrite needs to happen before you sign them, which is a bit bothersome if you don't have a build file. Note that VS can be configured to compile using your custom build file instead of the default build procedure.</p> <p>My final suggestion is to create a separate project just for the hg id, and use the post-build step to merge the generated assemblies into one. ILMerge supports re-signing of signed assemblies and this is therefore likely to be easier to make work. The downside is that redistribution of ILMerge is not allowed (although commercial use is).</p> <p>It's not a solution but hopefully inspiration to get you going.</p>
    singulars
    1. This table or related slice is empty.
    1. POEmbedding mercurial revision information in Visual Studio c# projects automatically
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMorten Mertner
    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. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CO@Morten Mertner, The problem with AssemblyVersion is that it tells you nothing about the source code. It gets even more complex when you have a branchy development model. If someone changes one particular library from the (stable) branch to the (experimental) branch, I want to be able to see that change in my log file. Using the 'hg id' tells me exactly what code was compiled into the library, and whether it has been modified. I can often then go back to the DVCS, update to that version, recompile and (hopefully) reproduce any problems my customer might be having.
      singulars
      1. PO
      1. USMark Booth
 

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