VB.Net, ASP.Net, SourceSafe and IIS

  • Thread starter Thread starter Mythran
  • Start date Start date
M

Mythran

I have an ASP.Net application that I have been developing on my local machine for
some time now. At this time, I need to deploy it to a development server since
it has now become a multi-developer project and we need to integrate SourceSafe
with IIS to allow for the source control for it.

I know how to set up the Source Control (SS) to do this, but what I need to know
before hand is:

The ss admin does not want to turn on individual permissions for the files (Read,
Write, Delete, blah). Only allows us to check-out/in. No adds, deletes, et
cetera. So, we can't create the project, add files to the project, etc. Which
stinks! But hey, gotta adapt. So, what do I need to do on my end to make sure
this project gets added correctly to the SS db, which is a remote db btw?

thanks a bunch!

Mythran the disgruntled programmer analyst.
 
Mythran said:
I have an ASP.Net application that I have been developing on my local machine for
some time now. At this time, I need to deploy it to a development server since
it has now become a multi-developer project and we need to integrate SourceSafe
with IIS to allow for the source control for it.

I know how to set up the Source Control (SS) to do this, but what I need to know
before hand is:

The ss admin does not want to turn on individual permissions for the files (Read,
Write, Delete, blah). Only allows us to check-out/in. No adds, deletes, et
cetera. So, we can't create the project, add files to the project, etc. Which
stinks! But hey, gotta adapt. So, what do I need to do on my end to make sure
this project gets added correctly to the SS db, which is a remote db btw?

thanks a bunch!

Mythran the disgruntled programmer analyst.
Click to expand...

Moving to ASP.NET we no longer integrate SourceSafe with IIS.

In VS.NET the VS on your local machine does all of the interaction with
SourceSafe.

Now for your SS admin. Adding items to source control happens very
frequently for projects in development. He won't be able to keep up with
all of the items to add, and should relent here.

Delete is also frequent, and he can give you permission to delete items, but
not "Destroy Permanently". They are still there in SS, but gone from the
project. Without the ability to delete, your projects will fill up with
dead items, and without the ability to Destroy Permanently, there is no real
danger.

David
 
Is it actually Microsfot VSS? If so, are you located in the same building
on the same subnet?

VSS doesn't do internet. =)

Also, when you say you can't add, you mean, he won't let you add new files
to a SS database? If not, your kinda screwed. You can check out your
..vbproj and add files, but if I can't add the actual file to the database,
its kinda dumb. =)

Maybe some clarification would help.

thanks,
CJ
 
My experiene with VSS is that it is best to let Visual Studio handle the
creation of the new project in VSS. In other words, add the project
through Visual Studio. Then delete the source code from your machine
and use the Open from Source Control menu option to recreate the
project. A lot of work? Yes. But it saves me from trying to figure
out exactly what VSS needs and where.

HTH

Bruce Johnson
http://www.ObjectSharp.com/Bruce
 
Hi Mytrhan,

Put it on a CD and give it to your Source Safe Admin,

And than every hour a floppy with a little unreadable note what he has to
do.

Cor

Did you know that the characters SS give a bad memory for a lot of people in
my country and from a big part of the EU from 2004.
 
Moving to ASP.NET we no longer integrate SourceSafe with IIS.

In VS.NET the VS on your local machine does all of the interaction with
SourceSafe.

Now for your SS admin. Adding items to source control happens very
frequently for projects in development. He won't be able to keep up with
all of the items to add, and should relent here.

Delete is also frequent, and he can give you permission to delete items, but
not "Destroy Permanently". They are still there in SS, but gone from the
project. Without the ability to delete, your projects will fill up with
dead items, and without the ability to Destroy Permanently, there is no real
danger.

David
Click to expand...

Ok, everyone took this a little further than what I intended to mean....so...here
it oes again...

VS.Net afaik can not add web projects to VSS. If I'm wrong, good :)

VS.Net can add normal projects, console, windows, et cetera no problem and it is
nice.

VS.Net interacts through IIS to handle version control through VSS....If I'm
wrong, good again, but that's how I'm currently doing it...

1.) Intranet, not Internet ... Project on remote server on the Intranet.
2.) VSS is on a DIFFERENT remote server on the Intranet.
3.) My machine is neither of those two servers.
4.) I am not allowed to ADD, DELETE, DESTROY.
5.) None of the above can be altered.
6.) Anything that needs to be added, deleted, or destroyed must be done so by
going through our VSS admin.
7.) The admin doesn't know how to do what I'm asking here (the setup part).
8.) Miss anything?

Thanks again :)

Mythran
 
I've never had a problem adding a web project to VSS through VS.NET.

I don't know what you mean about 'interacts through IIS'. I don't think
that IIS is involved with the VS.NET/VSS interaction.

What it sounds like should happen is to have the VSS admin open up the
web project using VS.NET and add it. Heck, he can probably log into VSS
using his id on your system so that he doesn't have to install VS.NET
anyplace new.

HTH

Bruce Johnson
http://www.ObjectSharp.com/Bruce
 
Mythran said:
Ok, everyone took this a little further than what I intended to mean....so...here
it oes again...

VS.Net afaik can not add web projects to VSS. If I'm wrong, good :)
Click to expand...

You are wrong.
VS.Net interacts through IIS to handle version control through VSS....If I'm
wrong, good again, but that's how I'm currently doing it...
Click to expand...

Again, wrong. It can work that way, but it's IIS and FrontPage extensions
doing it then, and that's more of the "old" way of doing it.
1.) Intranet, not Internet ... Project on remote server on the Intranet.
Click to expand...

You can use either FrontPage server extension or file shares to manage your
web projects from VS.NET. I use file shares.
2.) VSS is on a DIFFERENT remote server on the Intranet.
3.) My machine is neither of those two servers.
Click to expand...

Of course.
4.) I am not allowed to ADD, DELETE, DESTROY.
Click to expand...

You should be.
5.) None of the above can be altered.
6.) Anything that needs to be added, deleted, or destroyed must be done
Click to expand...
so by going through our VSS admin.

He'll be busy.
7.) The admin doesn't know how to do what I'm asking here (the setup
Click to expand...
part).

Set him up with VS.NET, or have him sit at your desk when you need something
added. He'll get tired of that eventually.


David
 
Visual Studio.Net certainly CAN add web projects to Visual SourceSafe
database, as well as fetching them out of VSS. We do it all the time.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
 
Back
Top