ASP.NET projects, VSS & IIS 6

[Ben]

My company is using VS.Net 2003 to create and maintain asp.net projects on a
windows 2003 webserver. The projects are created as applications and
subwebs, then via FPE 2002 extensions are added to source control ->
External version control, $/path/to/site.

We can open the projects no problem, we can check in / out no problem. We
don't however receive file history options, compare versions or anything
other than check in / out. Is this because of VSS, IIS, VS.Net or what?
Are we hitting a limitation, improper configuration or something else?

Thanks!
Ben

 

[Scott M.]

Please dont cross-post.

 

[Ben]

Why not? A) you did, B) I'm not sure which group the question belongs in.
Would you have prefered the same question three different times where
answers in group a weren't seen in group b?

 

[Weston Weems]

Frontpage has its own builtin "source control"... to be
honest, I dont think it works anything like SourceSafe at
all. I've never seen it keep revisions of anything.

 

[Scott M.]

I cross-posted my answer to be sure that you found it no matter which group
you checked back on.

It is considered bad etiquette to cross-post a question. How about posting
the question in one NG and waiting to see if you get an answer instead of
flooding several groups with a question that is not relevant to that group.

http://www.wjh.harvard.edu/wjh/newsgrp.shtml

5th paragraph down after "Keep in mind" might be useful to read.

 

[DellaCroce]

Are you able to answer his question or not? etiquette is good to know, but
if you can answer the person's question is much better.

 

[Cor Ligthert]

Scott,



Why did you think it was invented to do that?



I agree that multipost is bad (sending to every newsgroup a question which
takes the effort from more people in every newsgroup).



Crossposting is very good when the question can go over the borders of a
newsgroup.



You are the first one in the dotNet newsgroups who says something about
crossposting; it is completely inside the netiquette from the dotNet
newsgroups in my opinion.



Although it should not be done useless of course. However this is a sample
where it is very good done conform for what is was invented.



Cor





"> Please dont cross-post.

 

[Scott M.]

I agree that multipost is bad (sending to every newsgroup a question which

takes the effort from more people in every newsgroup).

Crossposting is very good when the question can go over the borders of a
newsgroup.

But that is not the case here.

You are the first one in the dotNet newsgroups who says something about
crossposting; it is completely inside the netiquette from the dotNet
newsgroups in my opinion.

Come on Cor, you must not have had your coffee yet this morning. I'm am
possibly the millionth person in the .NET NG's to warn others against
cross-posting.

Although it should not be done useless of course. However this is a sample
where it is very good done conform for what is was invented.

This question is not relevant to all the NG's it was posted to.

 

[Ben]

When you say frontpage do you mean the visual studio .net 2003
implementation of VSS for web applications?

 

[Lewis Moten]

Ben, you may not have a local copy of the file to compare against.
When you check the file out, then a local copy is retrieved from the
website and you can compare versions. You could also do a "Get
Latest" and then see if the "compare versions" option becomes enabled.