versioning

Using 2 different versions of the same dll?

由 狂风中的少年 提交于 2019-11-28 20:24:41
问题 I have been given 2 pre-compiled dlls: Common.Data, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f3b12eb6de839f43, processorArchitecture=MSIL Common.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=f3b12eb6de839f43, processorArchitecture=MSIL Example of differences in API: And I'm trying to load both into a single project to do something like this: extern alias v10; extern alias v20; private static void UpgradeUser() { // Load old user var userOld = new v10::Common.Data.UserData();

Java project: should .classpath .project file be committed into repository? [duplicate]

由 坚强是说给别人听的谎言 提交于 2019-11-28 20:03:24
This question already has an answer here: .classpath and .project - check into version control or not? 7 answers Should I check in my .project and .classpath files? My friend told me that I should only check in .java files and the build.xml to guarantee portability. He said ".classpath will cause you much less portability on different environment. .project is entirely your local eclipse setting" I agree with him, but partially. -- Not checking in .project file will make my development less efficient (I can't simply "import" a project code from a directory) -- Not checking in .classpath file

Assembly Versioning using CruiseControl.net

由 时光怂恿深爱的人放手 提交于 2019-11-28 18:27:38
I have setup CruiseControl.net for a bunch of my projects which are related. As a result a single project tag in CruiseControl has multiple SVN checkouts and then a bunch of msbuild tasks compile all the individual sln files. I need to update the assembly version of all the solutions when this build is being done. However, since i'm not using nant and not using MSBuild proj files, I am unsure on how to get this. I wonder if I'm missing something obvious. I just need a solution which can be implemented by making appropriate changes in the ccnet.config file without requiring me to make changes

Java MongoDB Object Versioning

由 允我心安 提交于 2019-11-28 18:01:16
I need to do versioning on (simple) Java object graphs stored in a document-oriented database (MongoDB). For relational databases and Hibernate, I discovered Envers and am very amazed about the possibilities. Is there something similar that can be used with Spring Data Documents? I found this post outlining the thoughts I had (and more...) about storing the object versions, and my current implementation works similar in that it stores copies of the objects in a separate history collection with a timestamp, but I would like to improve this to save storage space. Therefore, I think I need to

Maintaining both free and pro versions of an application

由 生来就可爱ヽ(ⅴ＜●) 提交于 2019-11-28 17:05:27
I want to create a PRO version of my application for Android and was wondering how to structure my repository. For know I have a trunk and feature branches. I'd like to put a pro version in another branch but maybe there is a better way? For example, maybe I should create two branches - one for free version, the other for pro? Pro version will have additional features and will be ads-free, so eg. I don't want to include AdMob libraries in the pro version. Do you have any experience or suggestions as to what would be the best way to structure the repository in this case? EDIT: I think I've

Detect application version change on a single page application

由 ▼魔方 西西 提交于 2019-11-28 16:23:57
today a question was raised here and I don't have an evident answer. Assume that we concatenate and minify all resource files (CSS and Javascript) and declare them in the "Master-Page". On a multi-page app, if a CSS file changes it will be recharged on the next full page load. On a single-page app, the user can keep working for days and never recharge the main page where the CSS files are declared. The user will never see the changes until a Ctrl-F5 is issued. I'm sure someone already thought of this and have an experience to share :) For me, using WebSockets is not an option. First because it

Best practices for assembly naming and versioning?

由 為{幸葍}努か 提交于 2019-11-28 16:14:08
问题 I am looking out for some good practices on naming assemblies and versioning them. How often do you increment the major or minor versions? In some cases, I have seen releases going straight from version 1.0 to 3.0. In other cases, it seems to be stuck at version 1.0.2.xxxx. This will be for a shared assembly used in multiple projects across the company. Looking forward to some good inputs. 回答1: Some good information from this article on Suzanne Cook's blog on MSDN (posted 2003-05-30): When to

What version numbering scheme to use?

由 我怕爱的太早我们不能终老 提交于 2019-11-28 15:41:36
问题 I'm looking for a version numbering scheme that expresses the extent of change, especially compatiblity. Apache APR, for example, use the well known version numbering scheme <major>.<minor>.<patch> example: 4.5.11 Maven suggests a similar but more detailed schema: <major>.<minor>.<patch>-<qualifier>-<build number> example: 4.5.11-RC1-3732 Where is the Maven versioning scheme defined? Are there conventions for qualifier and build number? Probably it is a bad idea to use maven but not to follow

Build numbers: major.minor.revision

由 人走茶凉 提交于 2019-11-28 13:50:50
问题 How would you write a build.xml file, using neither custom code nor external dependencies (such as a shell script), that: Generates a build number of the form major.minor.revision (e.g., 01.02.34 ). Auto-increments the revision on each compile of the source code. Auto-increments the minor version on each execution of a dist(ribution) task. Additionally: Provides an option to increment the major number. Provides an option to increment the minor number. Whenever the major number is incremented,

Which SqlServerCe DLL version do I need to reference in my project to match what's in sqlce.wce4.armv4.CAB?

由 老子叫甜甜 提交于 2019-11-28 13:48:59
问题 The "rest of the story" is told below in all its gory details, but to cut to the chase, it comes down to this: SQLCE 2.0 (contained in sqlce.wce4.armv4.CAB) seems to be installed on the device on which my app runs; the source project references SqlServerCe with a Runtime Version of v2.0.50727 and a Version of 3.5.1.0 Is this a match or a mismatch? If the latter, which version of SqlServerCe.dll do I need to reference in my project? THE REST OF THE GORY STORY My Windows CE app is failing when
订阅 versioning