sunny123

Hello!

One of our teams does all their development in SAS. They are planning to migrate their source control to Team Foundation Server. Since all their development is unix based, if a file is opened in windows by mistake, the file gets corrupted. To avoid this situation,

1. Is there a way to lock the file in Source Control such that when someone double-clicks on a file in Source Control Exploer after checking it out, it doesn't open in the VS2005 IDE

2. Is there a way to open the file directly in the unix editor Any settings that have to modified\any plug-ins required.

Thanks!



Re: Team Foundation Server - Version Control Open Unix Editor Source Control Explorer

eugene.z

I do not quite follow you. Do you mean that you perform development at Unix but want to limit access to source code on Windows

1. I do not think you can "lock" access in Visual Studio to checked out file. But that will be a problem only if the workspace in whcih file was checked out accessible and after file is opened and changed, it is saved. To me it seems like a case of user education and proper procedure rather than something you could expect from tool.

2. I believe that if the file extension is asscoiated in Windows shell with custom editor, when you double click on it in Source Control Explorer the file will be opened in your editor and not in VS.

Hope that helps,

Eugene






Re: Team Foundation Server - Version Control Open Unix Editor Source Control Explorer

Richard Berg MSFT

Unfortunately, if it's one of VS's supported file types, it will always open in VS.




Re: Team Foundation Server - Version Control Open Unix Editor Source Control Explorer

Ben Ryan - MSFT

If you don't want a particular file extension to open using its associated VS editor window, you can modify VS settings to have a different default editor.

1) Load a solution that has a file with the designated extension

2) In Solution Explorer, right-click that file and perform "Open With"

3) In the Open With dialog, click Add and add the external editor you want to associate with this file extension

4) Then in the Open With dialog, select your new editor in the list view and click "Set as Default". Click OK

Now whenever you open a file with the designated extension (including via double-click in Source Control Explorer), VS will open your external editor.

--Ben Ryan






Re: Team Foundation Server - Version Control Open Unix Editor Source Control Explorer

Martin Woodward

Just checking does your SAS team want to work inside Visual Studio

I hate plugging my own company on the MSDN forums but...

I know that SAS are a member of the Eclipse consortium and there is a plug-in to Eclipse that will allow you to work on your TFS stored files from with-in Eclipse (running on Windows, Linux, Unix etc). See http://www.teamprise.com to find out more about the Eclipse / Unix integration with TFS. Not sure if this is what you are after, but it might help.

Cheers,

Martin.