versioning

Is there a way to read value for the WiX variable from a text file? What I am trying to do is to include a version-specific information into instlal package. This version information extracted into the text file on the pre-build step, the question is how to propages this text file content into a build process. One of the possible solution is to update whole .wxs file on the pre-build step too, but it feel a bit sloppy. Is there any other, less-intrusive way? Thank you. Create a separate file 'includes.wxi', for example like this: <?xml version="1.0" encoding="utf-8"?> <Include Id=

In Kevin Goldsmith's 2015 talk about microservices at Spotify (from 15:25 - 17:43), he mentions that when they create a new version of an API they just create a new server, and keep the old server running with the old version for as long as there are still clients calling it (in this case, a smart lamp with Spotify embedded on it). I am confused about how they would be able to maintain and offer older versions for potentially years, when surely there would be database schema changes during that timeframe? I can see a few possible solutions, but none of them seem very reasonable: Using the same

I need to serialize some data to string. The string is then stored in DB in a special column SerializeData. I have created special classes that are used for serialization. [Serializable] public class SerializableContingentOrder { public Guid SomeGuidData { get; set; } public decimal SomeDecimalData { get; set; } public MyEnumerationType1 EnumData1 { get; set; } } Serialization: protected override string Serialize() { SerializableContingentOrder sco = new SerializableContingentOrder(this); MemoryStream ms = new MemoryStream(); SoapFormatter sf = new SoapFormatter(); sf.Serialize(ms, sco);

Here's a rather unpleasant pickle that we got into on a client site. The client has about 100 workstations, on which we deployed version 1.0.0 of our product "MyApp". Now, one of the things the product does is it loads up an add-in (call it "MyPlugIn", which it first looks for on a central server to see if there's a newer version, and if it is then it copies that file locally, then it loads up the add-in using Assembly.Load and invokes a certain known interface. This has been working well for several months. Then the client wanted to install v1.0.1 of our product on some machines (but not all)

I have application which uploaded into Subversion/SVN repo. Is it possible to use script to somehow change application version code stored in AndroidManifest ? I mean during/after checkout/update? <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="mypackage" android:versionCode="100000" android:versionName="1.0"> SVN has keyword substitution which you can use to put the revision number in a file. However, this will result in the revision when the manifest file itself was last changed, which is not what you want. The best way to achieve what you want is to call

I would like to have a git repository that consists mainly of binary files. I need to keep track of the changed, added and removed files to the repository, but I don't want for git to version the content of the files themselves. In other words, I just need for git to keep track of changes (change log), but not the content. Is this even possible with git? Should I be using something else for this? git is a content tracker, so if you don't want to track content it sounds like it's the wrong tool for the job. I'm not sure exactly how you would track changes to files without tracking their content