versioning

Displaying the build time-stamp in an application

由 霸气de小男生 提交于 2019-11-27 23:13:52
问题 I would like to display the time-stamp of when the application was built in an about box. This will allow me tracking different versions of the application. How can I retrieve this information in Java? 回答1: There's a much simpler maven solution which doesn't require the antrun plugin. Maven has a special variable maven.build.timestamp (since Maven 2.1.0-M1). <plugin> <artifactId>maven-war-plugin</artifactId> <!-- or maven-jar-plugin --> <version>2.2</version> <configuration> <archive>

Read AssemblyFileVersion from AssemblyInfo post-compile

由 江枫思渺然 提交于 2019-11-27 22:17:01
How can one read the AssemblyFileVersion , or its components AssemblyFileMajorVersion , AssemblyFileMinorVersion , AssemblyFileBuildNumber , AssemblyFileRevision , within the .csproj, following compilation? I have tried the following which pulls the information from the built assembly: <Target Name="AfterCompile"> <GetAssemblyIdentity AssemblyFiles="$(TargetPath)"> <Output TaskParameter="Assemblies" ItemName="MyAssemblyIdentities"/> </GetAssemblyIdentity> <Message Text="AssemblyVersion = %(MyAssemblyIdentities.Version)" /> </Target> But that retrieves the AssemblyVersion and not the

Core Data - Default Migration ( Manual )

由 坚强是说给别人听的谎言 提交于 2019-11-27 21:21:13
问题 i've read all possible blogs and SO post on the subject - but still not sure what's going on. I've also read this but still no luck - their guide to Default migration kind of clear but doesn't work in my situation . I'm relatively new to iOS development, so be gentle :) Here is the situation: on the entity called Report in my app (iOS), following changes need to happen: data attribute - deleted title attribute - added reportId attribute need to be changed from Integer 16 to String. This is

Detect application version change on a single page application

由 耗尽温柔 提交于 2019-11-27 19:58:13
问题 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

How do version numbers work for MRI Ruby?

由 元气小坏坏 提交于 2019-11-27 19:04:05
问题 A recent question, "What happened with Ruby 1.9.2?", made me wonder about version numbers for MRI Ruby mean. The scheme MRI Ruby uses differs from that of semver.org. How does versioning work in MRI Ruby, and what do the major (1), minor (9), teeny (3) and patchlevel (448) values mean in ruby 1.9.3p448 ? For example, what kind of changes are allowed in an increase in patchlevel, and what kind of changes are allowed in an increase of teeny? 回答1: They have changed to quasi-semantic versioning

What is a good free utility to create a self-extracting executable with an embedded file version? [closed]

由 雨燕双飞 提交于 2019-11-27 18:42:57
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 3 years ago . According to the answers to this question, I cannot embed a file version in my .msi file. The installer that I give the client needs to have a file version. So, what I want to do is create a self-extracting executable containing the msi file and the setup.exe generated by Visual Studio, and put the file version

ASP.NET - show application build date/info at the bottom of the screen

由 假装没事ソ 提交于 2019-11-27 18:22:23
I have a asp.net web application which has a number of versions deployed on different customer servers inside their networks. One practice that we have is to have clients email screenshots when they have issues. In the old asp.net 1.1 days, we could grab details of the build DLL, using reflection, and show info about the build date and numbering on the screen in a subtle location. With .NET 2.0 and higher, the build model changed, and this mechanism no longer works. I have heard of different build systems out there, but I'm really looking for the simplest way, on the 3.5 framework, to do what

How do AssemblyInfo attributes map to Win32 VERSIONINFO?

由 南楼画角 提交于 2019-11-27 18:12:34
问题 When you view the properties for a binary file that contains a VERSIONINFO resource, Windows adds a "Version" tab, which displays that information. Is there a list of which .NET assembly attributes map to which VERSIONINFO fields, so we can control these easily for our .NET assemblies? 回答1: Concerning the "fixed Info": PRODUCTVERSION and FILEVERSION are set from [AssemblyInformationalVersion] and [AssemblyFileVersion] respectively. FILEOS, FILETYPE are most likely set by the compiler.

Setting the version number for .NET Core projects - CSPROJ - not JSON projects

由 ε祈祈猫儿з 提交于 2019-11-27 17:36:35
This question is very similar to Setting the version number for .NET Core projects , but not the same. Using the latest stable version of .NET Core at the time of writing (1.1) and VS2017, .NET Core has switched from JSON based project files to CSPROJ files. So - what I am trying to do is set up a CI environment where I would like to be able to modify something prior to a build to stamp my builds with the correct version number. If I use the attributes like this the old (SharedAssemblyInfo.cs trick): [assembly: AssemblyFileVersion("3.3.3.3")] [assembly: AssemblyVersion("4.4.4.4")] somewhere in

What version numbering scheme do you recommend?

由 被刻印的时光 ゝ 提交于 2019-11-27 17:31:06
My question is, which version-naming scheme should be used for what type of project. Very common is major.minor.fix, but even this can lead to 4 number (i.e. Firefox 2.0.0.16). Some have a model that odd numbers indicate developer-versions and even numbers stable releases. And all sorts of additions can enter the mix, like -dev3, -rc1, SP2 etc. Exists reasons to prefer one scheme over another and should different type of projects (i.e. Open Source vs. Closed Source) have different version naming schemes? There are two good answers for this (plus a lot of personal preferences, see gizmo's
订阅 versioning