120
8
When attempting to check in code through TFS in visual studio 2012 or 2013 sometimes results in displaying an error message "Value was either too large or too small for a UINT32" error message. What is causing this, and how can I fix this?
Martijn
Posted 2014-02-17T10:47:16.773
Reputation: 3 362
200
This seems to be a bug in the dialog. This seems to consistently happen when you try to check in code that hasn't been saved, confusing the feature to a sufficient degree to throw up its hands in the air with this error.
The solution is simple: save your files before committing them.
Martijn
Posted 2014-02-17T10:47:16.773
Reputation: 3 362
0
Another possible Scenario: this happens after reverting to older file versions from TFS and then changing a file and trying to checkin.
Solution : update to latest version before checkin
Sam
Posted 2014-02-17T10:47:16.773
Reputation: 1
This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. You can also add a bounty to draw more attention to this question once you have enough reputation. - From Review
– Ramhound – 2016-02-23T18:40:55.917updated the solution , to be clearer – Sam – 2016-02-24T10:21:01.377
1You was right, I just edited my file during review and get this error. Saving helps for me. – RredCat – 2014-11-24T12:23:32.373
Worked for me as well, I had a T-SQL editor window open which, unsaved, caused me to not be able to check in my pending changes. – PeterL – 2015-02-17T22:33:09.297
7File > Save All – Danny Bullis – 2015-03-10T23:48:37.690
In my case I was actually just trying to queue a new build without any checking-in going on. Never would've thought of this, thanks. – makhdumi – 2015-09-23T20:22:47.053
@ardave What different solution was that? – Konrad Viltersten – 2015-10-23T10:21:54.210
1@KonradViltersten not using TFS – Martijn – 2015-10-23T10:39:55.833
@ardave Hehe, that answers my follow-up question on the pointy-hairness of the decision. – Konrad Viltersten – 2015-10-23T11:54:44.707
This happens also when checking in files different from those that were'nt saved. – Shahar – 2015-11-10T10:32:28.437
FYI: Error still happens in VS2015 Update 1. – Steve – 2016-02-08T20:17:17.280
Funny thing is this error still happens in VS 2015 Update 2 with the Git tooling. Anyway, saving all my files before checking in does the job. Thanks! – ajawad987 – 2016-04-12T05:50:34.120
Get this when shelving in VS2017 with TFS 2015 – Andez – 2017-09-25T09:47:46.483
1I can think of a different solution. :-) – ardave – 2014-03-24T20:12:56.663
3So can I, but that was pointy hairishly rejected – Martijn – 2014-03-25T00:04:26.277
12Thanks for that one, it appears the same occurs for an unsaved file that is not even part of the solution... I just had to close it and everything went fine. – Marcel Gosselin – 2014-06-04T15:09:14.237