versioning

Question in short: How tot do this in MVC.NET? Question in long version: Im trying to use a DateTime column in a SQL Table for version tracking (this in itself is proposed as a solution to re-attaching a Linq2Sql data class after being passedback by a editview for the table) But now i get 'row not found or changed'-exception. on the ctx.submit: ctx.appointments.Attach(appointment,true); ctx.SubmitChanges(); where ctx is my Linq datacontext, appointments my table, and appointment the appointment object i try to attach.. Ive setup the appointments table as sugested here This problem was also

I have converted my web service to wcf service which has some datacontracts. As a best practice it is mentioned and advisable that the DataContracts should inherit from IExtensibleDataObject. I get the point that in case of addition or removal of datamembers, IExtensibleDataObject is helpful. But i am not able to get how will the clients access removed datamembers. Here is my code: [ServiceContract(Namespace = "http://mycompany.com/2010/08/")] public class MyWebService { [OperationContract] public Employee Add(Employee emp) { // Some Processing } } [DataContract(Name = "Employee", Namespace =

As developer, I am often interested in new language feature that can make your life easier. For example, java 5 brought generics and annotations to the language, features that can definitely boost your productivity. However, when I look back at close to a decade working on java platform, I find that the versioning related problems are the biggest culprit of unproductive and needlessly spent effort. Hours and hours of looking for the correct version of the jar, trying to reconcile some versioning conflict, upgrading dependent libraries etc. When I started working in java, things were not that

In large Libre Source software projects, versioned with Mercurial or similar DVCS tools, which of the following is considered to be more conventional: Keeping the latest "stable" version of the software in the default branch. Tagging each release in default so you know which revision got packaged up as a download. Merging patches into default as soon as they are tested. Keeping new features, etc. in named branches to be merged into default on the next release. Keeping each release in a named branch, or similar. Using default to keep bleeding-edge code that's only intended to be run by

Problem description: In our project we have one "production database" and many "devs". We want to know how we can manage and install the changes. We already have some procedures but it takes a lot of time and sometimes causes errors. We can't lose data - so we can't use "drop table". We can only use "alter table". Our actual "db versioning procedure" is like this: We have a table named [actual_version] that contains the actual version of the installed db schema We have a file named "changes_script.sql" that contains all database changes - this file is stored on SVN When a developer wants to

I have an application that communicates with the firmware of a device. As there are changes to the firmware, it is versioned with the format {major}.{minor}.{revision}[beta[{beta}]] . To give you a few examples, the current version is 0.4.7beta which will be followed by 0.4.7beta2 and occasionally 0.4.7 , followed by 0.4.8beta . The versioning format of the firmware is unfortunately not under my control, so I can not change it. I need a way of comparing firmwares with each other. Basically, I need a function boolean isFirmwareNewer(String testFW, String baseFW); What I did so far was to