Visual sourcesafe connection between virtual and build machine - visual-studio

I have a problem and there are no lots of documents about that.
I will use visual studio as ide.
I want to use visual source safe for sharing and logging our projects from a server.
I installed source safe.But i have some help about how to connect this machine to our programmers machine.
I need detailed help about this because this is an unusual subject for me.
If there is someone to help we can do it by remote too.
Thank you for helping.

Do you want to retrieve the files which your programmers stored in SourceSafe database? If so, you can use Open from Source Control command under File menu. More details
You can also refer to the using VS with SourceSafe tutorial here.

Related

TFS working folder

we are moving from visual studio 2013 to visual studio 2015, and it is necessery for us to work with both studio in the same folders. Is there a way to use that and how can I set the tfs to work with both visual studios
Kind regards and thank you in advance
Assuming you install both VS2013 and VS2015 on your machine. When you map a project from TFS to local path in VS2013, if you open VS2015, and select the workspace you create in VS2013, then you'll see the same local path in VS2015, you don't need to map it again (make sure your project can work in both VS2013 and VS2015):
I would highly recommend to not do that as you might end up seriously corrupting the workspaces. Can you explain a bit more on why is this so necessary? I have helped organizations migrate between various instances of TFS over the few years now and we have not faced a situation like this. If you explain your particular use case a bit more I can perhaps suggest an alternative way to do this.
Also if you are working with TFS you might find this tool useful
https://visualstudiogallery.msdn.microsoft.com/a6b04ebd-e025-4c90-b238-72b48f0dfbd2

Visual Basic - How do I share my program?

I am currently in the process of developing a program in Visual Basic. For now, I want to give the program to a few friends to test, make changes and then release it. But I don't exactly know how. I used the Publish feature in Visual Basic, but I don't exactly know what I'm supposed to do with it. It mentions things like installing from a disk and whatnot. I just plan to upload it to a file sharing website and release it that way.
EDIT: Using Visual Studio 2012
Use dropbox or any file sharing site :D

Where does one get Visual Source Safe 2005?

I would like to install VSS 2005 so I can work on a project that is stored under it. Does anyone have any idea where the VSS 2005 client can be obtained? It does not appear to be on my VS2005 install disc (although that is for Team Suite). I cannot get any help from Google. I have an MSDN license (AA edition) but it doesn't seem to be there. This is a real product right?
Just to clarify preemptively based on some of the discussions I see on Google when I search for things like "VSS 2005," I am aware of the flaws in VSS and I still need to get it working; I am not interested in converting the project to Subversion; I am not able to transfer it to TFS; I am not able to upgrade the project to VS2008.
Thanks.
Two places, both from Microsoft:
Microsoft Store ($549.00)
MSDN Subscriber Downloads (Developer Tools > SourceSafe)
So, this is an old thread but occasionally still relevant. I'm adding an answer in case anyone comes across it in a google search.
If you have a copy of VSS 2005 installed on another machine but can't find the installation media, you can just copy C:\Program Files (x86)\Microsoft Visual Source Safe to your local machine. It will run just fine. Launch ssexp.exe and have at it.
You can get it from MSDN, I just looked it is there...see screenshot below

Removing SourceSafe Integration from Visual Studio 6

Recently, the SourceSafe integration into visual studio has started to perform badly because we have moved, and the SourceSafe "server" is located across a VPN which goes across a slow connection. This has made loading large projects in visual c++ 6 take 5+ minutes because it has to talk to the "server" for each project. Also, there are some bugs that are dangerous in the integration (the auto-checkout of certain shared projects will do a get latest on the wrong version of a branched file). This has caused me to want to disable the SourceSafe integration, however I have not found any menu option or uninstall option. Google has reported a few registry tweaks, but none of them seemed to work.
Does anyone know of an easy way to remove the SourceSafe integration from Visual C++ 6, without uninstalling SourceSafe altogether?
From http://support.microsoft.com/kb/236399:
Source code control software, such as
Microsoft Visual SourceSafe, that
integrates with the Visual C++
integrated development environment
(IDE) can be configured to connect to
a source code server during Visual C++
startup. In such cases, a loss in
network connectivity will cause Visual
C++ to start up very slowly. To
improve performance, either ensure
proper network connectivity or disable
the source code control software
integration with the Visual C++ IDE.
To do the latter, quit Visual C++, and
then use RegEdit.Exe to locate the
following registry key and set its
Disabled value to (DWORD) 0x00000001:
HKEY_CURRENT_USER\Software\Microsoft\DevStudio\6.0\Source Control\Disabled
I followed this and it seemed to work upon trying it again. I think I might've had a second copy of visual studio running when I did it the first time.
Open the .dsp and .dsw file in a text editor, and remove the respective entries from the .dsp and the .dsw file. Also, delete the .scc files.
There is a Microsoft Knowledge Base article about how to do exactly this.
The gist of it is that you must manually edit the .dsw and .dsp files in a text editor, and remove a few other files lying around. See the article for more details.
If the solutions mentioned above fail for you do this:
Rename folder: \Program Files\Microsoft\%vs%\Common7\IDE\VS SCC
VS will complain once about plug in not being there and you say "Yes" to ignore it in perpetuity.
All files “got latest,” “read only,” and edited in VS, will make VS complain and offer to “override”, which works fine for me.
What do you gain:
Open VSS-linked solutions quickly without VS matching contents to VSS server.
Open VSS-linked solutions and EDIT the files at will without being bogged down in “check out” bs.
This makes using other distributed source control system on top of project tree with VSS bindings painless.
VSS client still works by itself just fine, including diff, checkout, checkin.
HKEY_CURRENT_USER\Software\Microsoft\DevStudio\6.0\Source Control\Disabled
I followed this and it seemed to work upon trying it again. I think I might've had a second copy of visual studio running when I did it the first time.
Its working .....Thanks Ajay
What has worked for us, and is much easier, requires no registry/file editing by hand, and safer I think is this:
1) Exit Visual Studio completely.
2) Disconnect from the network (unplug the cable and turn off wireless, or disable the network adapters)
3) Open the VS6 workspace (DSW) for the project. When it starts up it will find it cannot connect with the VSS database it wants to and ask you about that...
4) Tell VS to never try to reconnect to the source control db in the future.
5) Done... VS does all the changes to THAT WORKSPACE/PROJECT setup for you. You are not disconnecting VS from source control in general (like a registry edit would do) and your not manually editing files.

Source Control in Visual Studio Isolated Shell

I am developing an Isolated Shell that caters to "designers/special content creators" performing specific tasks, using the Shell. As they operate on files, they need to be able to use TFS for source control. This is mainly due to the fact that Developers will also operate on the same files from TFS but using Visual studio 2008.
After looking and searching I still could not find Team Explorer to be available to Shell.
Asking on MSDN forums, lead me to the answer that "this is not supported yet in the Isolated Shell". Well, then the whole point of giving away a shell is not justified, if you want to use a source control system for your files. The idea is not to recreate everything and develop tool windows etc using the TFS provider API.
The Visual Studio Extensibility book by Keyven Nayyeri has an example, which only goes so far into this problem of adding a sc provider.
Has anyone worked on developing Visual Studio 2008 Isolated Shell applications/environment? Please provide comments, questions - anything that you have to share apart from the following threads, which I've already participated in.
Threads from MSDN forums:
Team Explorer for Isolated Shell
Is it possible to use Team Explorer in VS Shell Isolated?
Thanks for your answer. Yes you are right, we will acquire CALs for users without having to buy them Visual Studio, that's the direction we will be taking.
But I am yet to figure out how to make Team Explorer available to such users, inside Shell. So I am looking to find out the technical details of how that can be done.
I mean, I have a user, he installs my VS Shell application, he has no VStudio Team system on his machine. Now if I acquire CAL for TFS and install Team Explorer, do you think it will be automatically available in the VS Shell app?
Any ideas? have you worked on making this happen?
Thanks
It sounds like you are trying to allow the "special content creators" save files in TFS Source Control without having to buy them a license to a Visual Studio Team Edition -- correct me if I'm wrong.
If that's the case, unfortunately I believe that you can't quite do that. Your users still need a Client Access License ("CAL") to access TFS.
I think that you can acquire just CALs for your users without having to buy Visual Studio for them (I presume for less than a full blown Visual Studio would cost). At that point, you can just distribute to them the Team Explorer, which is a VS shell with nothing but TFS access components. That is available in your TFS server media.
I found this via Google. You might want to review it to decide your best options:
Visual Studio Team System 2008 Licensing White Paper
The only exception to the CAL rules I'm aware of is access to Work Items. Assuming properly licensed servers, anyone in your organization can create new Work Items or view and update existing ones created by them, using the Work Item Web Access component.
Just stumbled on this question, it might still be relevant to you.
You have the option of including the AnkhSVN (http://ankhsvn.open.collab.net/) packages and load it into your Isolated Shell. While there are some issues around it, with Subversion support, you could use SvnBridge to access TFS repositories. This might bring you a little bit closer to the process you are trying to achieve.

Resources