Lutz Roeder Saved my Mind
-
So, after a busy weekend coding furiously to revise an export tool for review tomorrow, religiously checking in my project after every change and good compile, I finally noticed the little head icon next to one file. That means a head is going to roll. :confused: SourceSafe in VS2005 tells me something about the file being checked out by someone else, so I open the project in SourceSafe itself and see the file still checked out, but to myself. So, I reckon what could be the harm in checking the file in and getting it again, as I must have about 20 versions today alone, so whatever this check-in overwrites, I can just revert to the previous version. So, I confirm all confirmations, and lo! I have a label from today, and a version dated 11 July. :~:~:~ No other version is found anywhere! :mad: It;s not like I was looking at the same source file in another VSS database or anything, it just ignored probably two hundred check-ins[1] since 11 July, and bang, screw you stupid user! :mad: Oh yes, the happy part. I am soo lucky I had VS closed when all this happened, which prevented a final build and test, as the last known good build before this shit was in my bin\debug. I whipped out Reflector[^] and disassembled the fallen class. I use a third party SDK, without a using statement, and all qualified type names frm the SDK were reduced to only the class name, which required some tweaking as some identical class names appear in two or three namespaces, but context and compile errors sorted that quite quickly. I also noticed that formal parameters for some methods were not of the correct type but of a previous type, something of a mystery, but about fifty initial compile errors quickly reduced by copy and paste edits, and I'm back in business. Thank you Ludz! :rose: [1] This is not on our source tree, I was using VSS here only as a change tracker.
-
So, after a busy weekend coding furiously to revise an export tool for review tomorrow, religiously checking in my project after every change and good compile, I finally noticed the little head icon next to one file. That means a head is going to roll. :confused: SourceSafe in VS2005 tells me something about the file being checked out by someone else, so I open the project in SourceSafe itself and see the file still checked out, but to myself. So, I reckon what could be the harm in checking the file in and getting it again, as I must have about 20 versions today alone, so whatever this check-in overwrites, I can just revert to the previous version. So, I confirm all confirmations, and lo! I have a label from today, and a version dated 11 July. :~:~:~ No other version is found anywhere! :mad: It;s not like I was looking at the same source file in another VSS database or anything, it just ignored probably two hundred check-ins[1] since 11 July, and bang, screw you stupid user! :mad: Oh yes, the happy part. I am soo lucky I had VS closed when all this happened, which prevented a final build and test, as the last known good build before this shit was in my bin\debug. I whipped out Reflector[^] and disassembled the fallen class. I use a third party SDK, without a using statement, and all qualified type names frm the SDK were reduced to only the class name, which required some tweaking as some identical class names appear in two or three namespaces, but context and compile errors sorted that quite quickly. I also noticed that formal parameters for some methods were not of the correct type but of a previous type, something of a mystery, but about fifty initial compile errors quickly reduced by copy and paste edits, and I'm back in business. Thank you Ludz! :rose: [1] This is not on our source tree, I was using VSS here only as a change tracker.
You have to love Reflector. Lutz really has done an amazing job and it's invaluable - especially if you want to demonstrate a VB.NET version of code to somebody and you only ever code in C#. Don't knock it - it works.:laugh:
Deja View - the feeling that you've seen this post before.
-
You have to love Reflector. Lutz really has done an amazing job and it's invaluable - especially if you want to demonstrate a VB.NET version of code to somebody and you only ever code in C#. Don't knock it - it works.:laugh:
Deja View - the feeling that you've seen this post before.
Pete O'Hanlon wrote:
You have to love Reflector
I second that. Can't begin to say how often Reflector has been a help :)
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
Pete O'Hanlon wrote:
You have to love Reflector
I second that. Can't begin to say how often Reflector has been a help :)
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
It's often been a help to me, but not like this. It redid about four days of work.
-
You have to love Reflector. Lutz really has done an amazing job and it's invaluable - especially if you want to demonstrate a VB.NET version of code to somebody and you only ever code in C#. Don't knock it - it works.:laugh:
Deja View - the feeling that you've seen this post before.
Oh my God, it does VB.NET as well. :~ I never noticed before, but I guess I'll just have to be more careful now when I disassemble.
Last modified: 12mins after originally posted --
-
Oh my God, it does VB.NET as well. :~ I never noticed before, but I guess I'll just have to be more careful now when I disassemble.
Last modified: 12mins after originally posted --
Brady Kelly wrote:
Oh my God, it does VB.NET as well
:laugh::laugh: Well, it should since it looks at the IL :)
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
Brady Kelly wrote:
Oh my God, it does VB.NET as well
:laugh::laugh: Well, it should since it looks at the IL :)
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
I'm very impressed at its abilities with local variable names. I've renamed my .pdb file, and Reflector still names locals correctly. Where else could it get this info from?
-
So, after a busy weekend coding furiously to revise an export tool for review tomorrow, religiously checking in my project after every change and good compile, I finally noticed the little head icon next to one file. That means a head is going to roll. :confused: SourceSafe in VS2005 tells me something about the file being checked out by someone else, so I open the project in SourceSafe itself and see the file still checked out, but to myself. So, I reckon what could be the harm in checking the file in and getting it again, as I must have about 20 versions today alone, so whatever this check-in overwrites, I can just revert to the previous version. So, I confirm all confirmations, and lo! I have a label from today, and a version dated 11 July. :~:~:~ No other version is found anywhere! :mad: It;s not like I was looking at the same source file in another VSS database or anything, it just ignored probably two hundred check-ins[1] since 11 July, and bang, screw you stupid user! :mad: Oh yes, the happy part. I am soo lucky I had VS closed when all this happened, which prevented a final build and test, as the last known good build before this shit was in my bin\debug. I whipped out Reflector[^] and disassembled the fallen class. I use a third party SDK, without a using statement, and all qualified type names frm the SDK were reduced to only the class name, which required some tweaking as some identical class names appear in two or three namespaces, but context and compile errors sorted that quite quickly. I also noticed that formal parameters for some methods were not of the correct type but of a previous type, something of a mystery, but about fifty initial compile errors quickly reduced by copy and paste edits, and I'm back in business. Thank you Ludz! :rose: [1] This is not on our source tree, I was using VSS here only as a change tracker.
Yup. Surely, one of the great mysteries of the Universe is whether or not Reflector's greatness is matched by VSS's suckage. Right up there with Spiderman vs. Wolverine, i tells ya...
You must be careful in the forest Broken glass and rusty nails If you're to bring back something for us I have bullets for sale...
-
So, after a busy weekend coding furiously to revise an export tool for review tomorrow, religiously checking in my project after every change and good compile, I finally noticed the little head icon next to one file. That means a head is going to roll. :confused: SourceSafe in VS2005 tells me something about the file being checked out by someone else, so I open the project in SourceSafe itself and see the file still checked out, but to myself. So, I reckon what could be the harm in checking the file in and getting it again, as I must have about 20 versions today alone, so whatever this check-in overwrites, I can just revert to the previous version. So, I confirm all confirmations, and lo! I have a label from today, and a version dated 11 July. :~:~:~ No other version is found anywhere! :mad: It;s not like I was looking at the same source file in another VSS database or anything, it just ignored probably two hundred check-ins[1] since 11 July, and bang, screw you stupid user! :mad: Oh yes, the happy part. I am soo lucky I had VS closed when all this happened, which prevented a final build and test, as the last known good build before this shit was in my bin\debug. I whipped out Reflector[^] and disassembled the fallen class. I use a third party SDK, without a using statement, and all qualified type names frm the SDK were reduced to only the class name, which required some tweaking as some identical class names appear in two or three namespaces, but context and compile errors sorted that quite quickly. I also noticed that formal parameters for some methods were not of the correct type but of a previous type, something of a mystery, but about fifty initial compile errors quickly reduced by copy and paste edits, and I'm back in business. Thank you Ludz! :rose: [1] This is not on our source tree, I was using VSS here only as a change tracker.
Brady Kelly wrote:
SourceSafe in VS2005
I will never, ever, use SourceSafe. Marc
-
Yup. Surely, one of the great mysteries of the Universe is whether or not Reflector's greatness is matched by VSS's suckage. Right up there with Spiderman vs. Wolverine, i tells ya...
You must be careful in the forest Broken glass and rusty nails If you're to bring back something for us I have bullets for sale...
Shog9 wrote:
great mysteries of the Universe is whether or not Reflector's greatness is matched by VSS's suckage. Right up there with Spiderman vs. Wolverine
:laugh: Nice analogy, there.
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
Brady Kelly wrote:
SourceSafe in VS2005
I will never, ever, use SourceSafe. Marc
Look, what happened here is ultimately my fault, but the way it happened and the fact that once I ignore one message, VSS just canned my source file, has me going to make a very serious recommendation against it at our "way forward" think tank on Tuesday. My lead is very pro open source, so I'm sure given one good reason we will seriously look at Subversion. We were looking at VSTS, but I don;t know what happened there, probably too expensive.
-
So, after a busy weekend coding furiously to revise an export tool for review tomorrow, religiously checking in my project after every change and good compile, I finally noticed the little head icon next to one file. That means a head is going to roll. :confused: SourceSafe in VS2005 tells me something about the file being checked out by someone else, so I open the project in SourceSafe itself and see the file still checked out, but to myself. So, I reckon what could be the harm in checking the file in and getting it again, as I must have about 20 versions today alone, so whatever this check-in overwrites, I can just revert to the previous version. So, I confirm all confirmations, and lo! I have a label from today, and a version dated 11 July. :~:~:~ No other version is found anywhere! :mad: It;s not like I was looking at the same source file in another VSS database or anything, it just ignored probably two hundred check-ins[1] since 11 July, and bang, screw you stupid user! :mad: Oh yes, the happy part. I am soo lucky I had VS closed when all this happened, which prevented a final build and test, as the last known good build before this shit was in my bin\debug. I whipped out Reflector[^] and disassembled the fallen class. I use a third party SDK, without a using statement, and all qualified type names frm the SDK were reduced to only the class name, which required some tweaking as some identical class names appear in two or three namespaces, but context and compile errors sorted that quite quickly. I also noticed that formal parameters for some methods were not of the correct type but of a previous type, something of a mystery, but about fifty initial compile errors quickly reduced by copy and paste edits, and I'm back in business. Thank you Ludz! :rose: [1] This is not on our source tree, I was using VSS here only as a change tracker.
This is why we stopped using SourceSafe. Personally I consider the product too dangerous to use. I'm astounded it's so crappy. Microsoft: You have billions and billions of dollars. Buy a company that has a decent source control product.
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
This is why we stopped using SourceSafe. Personally I consider the product too dangerous to use. I'm astounded it's so crappy. Microsoft: You have billions and billions of dollars. Buy a company that has a decent source control product.
cheers, Chris Maunder
CodeProject.com : C++ MVP
Thanks Chris, I'm sure coming from you this will make my motivation to move off it a little easier to get across.
-
This is why we stopped using SourceSafe. Personally I consider the product too dangerous to use. I'm astounded it's so crappy. Microsoft: You have billions and billions of dollars. Buy a company that has a decent source control product.
cheers, Chris Maunder
CodeProject.com : C++ MVP
Chris Maunder wrote:
we stopped using SourceSafe
What do you use then?
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
Chris Maunder wrote:
we stopped using SourceSafe
What do you use then?
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
What a... garish... website... :~
-
Silly question, but how does it fare for you (must be okay to great if you are using it)?
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
What a... garish... website... :~
My thoughts, too. Could be prettied up a little :)
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
So, after a busy weekend coding furiously to revise an export tool for review tomorrow, religiously checking in my project after every change and good compile, I finally noticed the little head icon next to one file. That means a head is going to roll. :confused: SourceSafe in VS2005 tells me something about the file being checked out by someone else, so I open the project in SourceSafe itself and see the file still checked out, but to myself. So, I reckon what could be the harm in checking the file in and getting it again, as I must have about 20 versions today alone, so whatever this check-in overwrites, I can just revert to the previous version. So, I confirm all confirmations, and lo! I have a label from today, and a version dated 11 July. :~:~:~ No other version is found anywhere! :mad: It;s not like I was looking at the same source file in another VSS database or anything, it just ignored probably two hundred check-ins[1] since 11 July, and bang, screw you stupid user! :mad: Oh yes, the happy part. I am soo lucky I had VS closed when all this happened, which prevented a final build and test, as the last known good build before this shit was in my bin\debug. I whipped out Reflector[^] and disassembled the fallen class. I use a third party SDK, without a using statement, and all qualified type names frm the SDK were reduced to only the class name, which required some tweaking as some identical class names appear in two or three namespaces, but context and compile errors sorted that quite quickly. I also noticed that formal parameters for some methods were not of the correct type but of a previous type, something of a mystery, but about fifty initial compile errors quickly reduced by copy and paste edits, and I'm back in business. Thank you Ludz! :rose: [1] This is not on our source tree, I was using VSS here only as a change tracker.
I had something similar a while ago although we were using Seapine Surround. After spending a week on a project and religiously checking everything in I got a working build, the heavens opened and the angels sang. The following day I open studio and it asks if I would like to do a get, thinking someone else may have made a change and knowing that my changes were all in there I said yes, if only I had known that somehow all the changes had been lost and that I was now checking out a project several revisions old, the angels had stopped singing. But coming charging over the hill to my rescue shining in the midday sun was Ludz and Reflector. Disassembling the last working build of my application I managed to get it all back and surprisingly managed to refactor some of it as well. I learnt my lesson from this affair, Studio sucks, seapine sucks, together they are a source for evil in this world. But with Ludz and Refactor out there we might just stand a chance. Thank you Ludz
-
Brady Kelly wrote:
SourceSafe in VS2005
I will never, ever, use SourceSafe. Marc
Me neither, I cannot see any point, as I take backups at key stages, and therefore do not need a backup of every change I ever make.
Steve Jowett ------------------------- Sometimes a man who deserves to be looked down upon because he is a fool, is only despised only because he is an 'I.T. Consultant'