New answers tagged versioning
If you update item in code you can use SPListItem.SystemUpdate(incrementListItemVersion) method. False value in parameter does not increase version.
Got around this by creating a new custom column, setting it to a formula and then referencing [Version Number] in the field. It now shows on all pages alongside the other custom columns.
As mentioned by @Steven, changes to any field values are captured by a version. However, if you don't want a change in field value being reported in version history, then you can set the field property ShowInVersionHistory to false.
That's not possible. You can delete specific versions but a version always captures all changes to an item.
Using some CAML tools pointed at a local library with versioning enabled, I was able to get back the field ows__UIVersionString of a file. It correctly shows the version is 9.0 which is reflected in the UI. <Where> <Eq> <FieldRef Name='ID' /> <Value Type='Counter'>1</Value> </Eq> ...
Next time you make changes to your CSS file, create your own rev/version tag where the CSS file is being referenced (probably your Master Page). This way the browser will break the cached CSS and re-retrieve thinking it's a new file. ex. <link href="/styles/style.css?rev=03_27_2014_v1" type="text/css" rel="stylesheet" />
Top 50 recent answers are included