Relative Content

Tag Archive for versioning

Managing multiple versions of the same Android Library Project

I have an Android Library Project which I intensively used in a few projects. I started a new project in which I am also using this library. I want to improve some things in library (method signaturesnames, interfaces, etc.). But if I change method signaturesnames, interfaces, I should update old projects that use this library. That could be hard work.

Best practise to versioning Web Service WCF

I’ve a web service SOAP developed with WCF, there is a best practise to versioning it? when I change the contract I don’t want to update all the client’s referiments but I want simply publish a new version that coexists with the old.

Best practise to versioning Web Service WCF

I’ve a web service SOAP developed with WCF, there is a best practise to versioning it? when I change the contract I don’t want to update all the client’s referiments but I want simply publish a new version that coexists with the old.

Best practise to versioning Web Service WCF

I’ve a web service SOAP developed with WCF, there is a best practise to versioning it? when I change the contract I don’t want to update all the client’s referiments but I want simply publish a new version that coexists with the old.

Best practise to versioning Web Service WCF

I’ve a web service SOAP developed with WCF, there is a best practise to versioning it? when I change the contract I don’t want to update all the client’s referiments but I want simply publish a new version that coexists with the old.

Versioning business rules

TL;DR Storing ever-changing business rules so that an app can behave like it did at moment X in the past. Can it be done? If so, how? Long version At this very moment, this is more of a thought exercise than an actual need, though things could change in the not so distant future. The […]

Are version numbers needed

We build a system which works as software as a service. Now I am wondering if it is needed to give the version number to the clients. For example Facebook doesn’t give a version number neither does Google. My question is basically would one include version numbers in an application where the client cannot change the version themselves?

Are version numbers needed

We build a system which works as software as a service. Now I am wondering if it is needed to give the version number to the clients. For example Facebook doesn’t give a version number neither does Google. My question is basically would one include version numbers in an application where the client cannot change the version themselves?