pandahwa.blogg.se

Unable to open user login file sourcesafe
Unable to open user login file sourcesafe






The loop for keeping people in - sometimes it needs to be loopier. I've started using ProWritingAid's free editing software on my writing and I can see such a difference! They're giv… /i/web/status/1… ~ 2 years ago

unable to open user login file sourcesafe

Get a #freebook from Logos wn.nr/cNMJgG ~ 1 year ago Really, you are probably better off without them. Written permission is required if you wish to reproduce them in any way. The text, pictures and media used in this blog and its associated pages copyright Kramii, unless stated otherwise. My thanks to Marc Hoeppner for his excellent article from which I gleaned this information. You can accept the default on all subsequent prompts. You can now right-click the files you want and undo check out: Select the database you want, and enter the admin password: For me this is ‘ “C:\Program Files\Microsoft Visual Studio\VSS\win32\SSEXP.EXE” -yadmin’ (including the double-quotes). Type the command line for VSS explorer, followed by “-yadmin”. As a result, Visual Studio won’t let me make any changes to these files.įrom time-to-time, most VSS users need to check someone else’s files back in because they are not available to do so. Normally, in VSS, the option to undo check out is greyed-out on a file that someone else has checked out. However, if you run VSS as the Admin user, you can undo check out for another user. Unfortunately, he checked out these files in Visual Source Safe (VSS), but did not check them back in. Anyway, I'm back up and running.One of my colleges is off sick today. I need to edit some files that he was working with on Friday.

unable to open user login file sourcesafe

So, i think it's just the documentation that's wrong. So, i went back to sourcesafe, removed the quotes around %1 and %2 and now it works. Ok, I launched UC from UEStudio and told it to compare those same two files, checked the arguments that were passed and noticed that the arguments were not wrapped in double quotes. Seems to me that UC doesn't support command line arguments that have spaces in them? If I pull up the history of the files and diff them then the arguments passed to uc.exe are both based on temporary folders (like argument #1 above) and so it opens with 2 panes and all is well. Typing the above from a command line gives the same result actually. The result is that UC.EXE launches with 3 diff panes open and the error I mentioned in my original post. All folders have no spaces in them apart from the last folder in the second argument. I've changed some of the folder names above.

unable to open user login file sourcesafe

"C:\Users\myname\AppData\Local\temp\filename.h" "C:\Users\myname\Work\FolderA\Release\System\FolderB\FolderC\State Machine\filename.h" OK, when I right click on a file in sourcesafe and ask it to "Show differences" UC.exe launches with the following arguments:








Unable to open user login file sourcesafe