Windows Server

cata · Guest

Hello,

How can be integrated VSS and SPS?
At the following address writes that this is possible, but I didn't find any
instalation documentation.

http://msdn2.microsoft.com/en-us/library/ms181090(en-US,VS.80).aspx

Gary A. Bushey [SPS MVP] · Guest

As this was listed as to work only with SPS V1, not SPS 2003, I can only
assume it no longer exists. As least a search for the Visual SourceSafe
Integration Suite did not return any valid hits.

--
Gary A. Bushey
SPS MVP
bushey@mindspring.com
"cata" <cata@discussions.microsoft.com> wrote in message
news:B0B44387-F861-4FBF-AE97-3712469C01C0@microsoft.com...

Stokesy · Guest

Hi,

I have never really found a bullet proof way to integrate VSS and SPS.
however, I h ave had some limited success.

The key areas that you want to include in VSS are the TEMPLATE folder
and below. What I normally do is make a copy of the LAYOUTS folder and
put it somewhere else on the system, and update IIS to point to this
new location. That way the originals are left well alone, and i can
support more than one customised portal on a server.

Then, in VS.Net I create a new blank project in the LAYOUTS folder
and/or the originial TEMPLATE folder if I want to keep my site defs in
VSS. Once I have the blank project created, in VS.NET choose to show
all files and include those files in your project that you want to be
protected. Then you can simply add them to VSS throrugh the normal
VS.NET controls.

Of course, your custom web parts can and should be stored in VSS as
normal, as can any other custom ASPX projects/files you run from the
_Layouts folder.

Now, the drawbacks.

Whilst this will give you some sort of source control, it does not go
as far as to make sure only 1 user can edit a file at a time. You
basically only get the file archiving features. When you mark a
particular file as checked out, anyone with access to that folder on
the sharepoint server will be able to change it. The reason for this
is that in a normal dotnet app you run a copy of the code on your own
dev machine and with sharepoint we tend to share it. There might be
ways of running sharepoint on your own dev machine and keep the source
in VSS, but I have not tried this way.

This method kind of works, but as I said, it does fall a bit short of
the mark. Generally there is no decent method (that I am aware of) to
achieve full source control with a sharepoint deployment.

Mark Stokes.

	Windows Server Forum Index -> Portal Server Development	All times are GMT
Page 1 of 1