versioning

If I want to serialize an object I have to use [Serializable] attribute and all member variables will be written to the file. What I don't know how to do versioning e.g. if I add a new member variable (rename a variable or just remove a variable) and then I open (deserialize) the file how can I determine the object/file version so I can correctly set the new member or take some kind of migration? How can I determine that the variable was initialized during the load or not (ignored by deserializer). I know that there are version tolerant approaches and I can mark variables with [OptionalField

Today I've faced with a strange behavior of NuGet when installing a package. A brief description: as a result of my build script there's a NuGet package. I don't change the version each time, so each and every build produces MyPackage.1.0.0.nupkg . As the final step of the build, I push the package to the NuGet server deployed inside the local network. Now, on a different machine, I run nuget install MyPackage -Source http://myserver/nuget , which obviously installs the NuGet package. The problem comes into play when I push another update of MyPackage - still of version 1.0.0 . When I try to

I've read threads here about the Assembly, File and Assembly Informational versions. I'd like to know where the Publish version fits in. The result of... string thisAppsVersion = System.Reflection.Assembly.GetExecutingAssembly().GetName().Version.ToString(); ...appears to be the AssemblyVersion. Up until now I've been using the publish version with the deployment class: ApplicationDeployment deployment = ApplicationDeployment.CurrentDeployment; Version thisAppsVersion = deployment.CurrentVersion; ...but this isn't available unless the app is installed. I like how it has the option to

I have a RESTful web service deployed at http://example.com/v1/SomeResource . One day, a new protocol version ( that is not backwards compatible ) is deployed to http://example.com/v2/SomeResource . From the client of view, this upgrade could occur at any time between two HTTP requests. How does the server indicate to the client that it no longer supports v1 calls and the client is expected to upgrade to v2? Is there an appropriate response code I can use? I would want to provide the client with the following information: An incompatible upgrade has taken place. There is no way for the client

I am using JQuery Mobile and there are two available versions: A stable version and a legacy version. I am not familiar with the latter one. What is a legacy version? or what is the difference with the stable version? Which one is recommended to use in a production site? Many thanks A legacy version is an old stable release that is still available (and probably supported) because someone might need it (e.g. plugin dependencies that don't work with the newest release), whereas the stable version is the most recent stable release (which will eventually become a legacy version). So if there is no

Firstly, I think this forum is not appropriate for my question, so if it is in wrong place, kindly forgive and place wherever appropriate. I didn't find proper forum for my question. I have developed a C# application (Win Forms). Now I need to handle its version numbering. I can't make out what is the best way to do. I want the version number to be simple something like 1.2 or 1.2.1. I read about SVN Version, but that also seems little confusing at this stage. There are different version types for the application - 1 with the installer , and 1 without installer. I think the release version and

There's probably multiple questions here all related. I'm trying to come up with a simple version number update scheme for our 3 mobile apps built from a single xamarin solution. What I'm looking for is a simple way to keep all these values in sync with one another without having to go around and update them all individually. Windows Phone Version should get set to the AssemblyVersion or FileVersion Automatically IOS Version Number should be set to same. (not sure what the build number should be) Android Version Name should be set to same. Android Version Number should auto increment for each