Attention: We are retiring the ASP.NET Community Blogs. Learn more >

Damn CS-RCS

Yesterday, i installed CS-RCS from ComponentSoftware, i was looking for a configuration management component which we could integrate into our product which needs to support document versions. ( I still haven't found any suitable candidates) So anyways i try to open the solution today and it says that source control status is invalid. After beating my head for one hour trying to figure out what was wrong with VSS i saw that the repository selected was CS-RCS...aaargh, the least these guys could have done was provide a SCC switcher like these guys and this guy and this guy and this guy have already done.  Is that too much to ask? (Even i didn't know there were so many options before i googled)

It turns out that CS-RCS changed my SCC provider to CS-RCS now to restore it i had to execute ssint.exe from vss\win32 folder and i could access source control now. But the episode was really nasty, especially  coming from a company that makes configuration management tools. So if any guys from ComponentSoftware are listening,  please provide a SCC switcher or atleast restore the previous one on uninstallation.

No Comments