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" <be*@online.nos pam> wrote in message
news:UG******** *******@fe37.us enetserver.com. ..

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

[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?

"Scott M." <s-***@nospam.nosp am> wrote in message
news:%2******** *******@TK2MSFT NGP11.phx.gbl.. .

Please dont cross-post.
"Ben" <be*@online.nos pam> wrote in message
news:UG******** *******@fe37.us enetserver.com. ..

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.]

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.
"Ben" <be*@online.nos pam> wrote in message
news:8i******** *******@fe37.us enetserver.com. ..

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?

"Scott M." <s-***@nospam.nosp am> wrote in message
news:%2******** *******@TK2MSFT NGP11.phx.gbl.. .

Please dont cross-post.
"Ben" <be*@online.nos pam> wrote in message
news:UG******** *******@fe37.us enetserver.com. ..

> 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
>
>
>

[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.

"Scott M." <s-***@nospam.nosp am> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. ..

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.
"Ben" <be*@online.nos pam> wrote in message
news:8i******** *******@fe37.us enetserver.com. ..

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?

"Scott M." <s-***@nospam.nosp am> wrote in message
news:%2******** *******@TK2MSFT NGP11.phx.gbl.. .

Please dont cross-post.
"Ben" <be*@online.nos pam> wrote in message
news:UG******** *******@fe37.us enetserver.com. ..
> 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
>
>
>

[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.

"Ben" <be*@online.nos pam> wrote in message
news:UG******** *******@fe37.us enetserver.com. ..

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.]

> 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.

[Kevin Yu [MSFT]]

Hi Ben,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you cannot compare versions and
historys when your ASP.NET project is checked into VSS. If there is any
misunderstandin g, please feel free to let me know.

Could you let me know how you're using the history option? Are you using it
from VSS explorer or compare versions in VS.NET IDE? Or you're using a
command line? How did you see that the option doesn't function? Is it
disabled or it just return error?

I think most probably, this is a configuration issue. Please provide us
with more information, so that we can deliver our assistance more quickly.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[Kevin Yu [MSFT]]

Hi Ben,

There might be some tool issue here that I didn't see your reply message.
Could you re-paste them here so that we can continue working on this issue?

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[Ben]

I'm trying to look at versions from VS .Net 2003. I go to the solution
explorer right click a file and compare versions is greyed out. If I select
a file from the solution explorer and go to File -> Source Control
everything is grey except for check out / in, undo checkout and refresh
status. Right now from the VS .Net 2003 IDE I have no way to compare
versions or view file history. In fact I have to logon to the machine with
VSS and look at it from there...

Ben

"Kevin Yu [MSFT]" <v-****@online.mic rosoft.com> wrote in message
news:7t******** ******@cpmsftng xa10.phx.gbl...

Hi Ben,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you cannot compare versions and
historys when your ASP.NET project is checked into VSS. If there is any
misunderstandin g, please feel free to let me know.

Could you let me know how you're using the history option? Are you using it from VSS explorer or compare versions in VS.NET IDE? Or you're using a
command line? How did you see that the option doesn't function? Is it
disabled or it just return error?

I think most probably, this is a configuration issue. Please provide us
with more information, so that we can deliver our assistance more quickly.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."