Please help frontpage server and IIS

Hi .. please forgive me if this is the wrong forum.. I have created a new dev
web server and am trying to set it up as a dev server for classic asp sites.

I have loaded sourcesafe on the server, and added frontpage server
extensions. I used sourcesafe to create the web app which i can browse fine.

When I connect through interdev I can create the solution no problem

However, when I try to add the solution to sourcesafe, the solution file
itself is added but not the rest of the files and it gives me the errors that
either the server does not have sourcesafe loaded (it does) or the username
cannot be found..

This is baffling, how can it create the solution file? Also the VSS
integration must be working because the first time you try it opens
sourcesafe to ask you where you want to store the project..

Only possible clue is that when I open IIS on the server and right click the
project and say "check server extentsions" it asks me to authenticate.

Also the sourcesafe.ini is on a DFS share if that makes any odds?

Sorry if this is the wrong forum .. friendly redirection to the correct
group will be accepted but please if you have a clue about my issue please
help

"Robert" <Robert@discussions.microsoft.com> wrote in message
news:03918FE8-1B9A-493F-81FF-E98107D1555F@microsoft.com...
> Hi .. please forgive me if this is the wrong forum.. I have created a new
> dev
> web server and am trying to set it up as a dev server for classic asp
> sites.
>
> I have loaded sourcesafe on the server, and added frontpage server
> extensions. I used sourcesafe to create the web app which i can browse
> fine.
>
> When I connect through interdev I can create the solution no problem
>
> However, when I try to add the solution to sourcesafe, the solution file
> itself is added but not the rest of the files and it gives me the errors
> that
> either the server does not have sourcesafe loaded (it does) or the
> username
> cannot be found..
>
> This is baffling, how can it create the solution file? Also the VSS
> integration must be working because the first time you try it opens
> sourcesafe to ask you where you want to store the project..
>
> Only possible clue is that when I open IIS on the server and right click
> the
> project and say "check server extentsions" it asks me to authenticate.
>
> Also the sourcesafe.ini is on a DFS share if that makes any odds?
>
> Sorry if this is the wrong forum .. friendly redirection to the correct
> group will be accepted but please if you have a clue about my issue please
> help

There are some visual studio groups but frankly what you are trying to do is
(in computing terms) ancient history. I remember grappling with FP
extenstions and source safe in older versions of VS but its just not how its
done these days.

Must you use interdev?


--
Anthony Jones - MVP ASP/ASP.NET

"Anthony Jones" wrote:


> There are some visual studio groups but frankly what you are trying to do is
> (in computing terms) ancient history. I remember grappling with FP
> extenstions and source safe in older versions of VS but its just not how its
> done these days.
>
> Must you use interdev?
>
>
> --
> Anthony Jones - MVP ASP/ASP.NET
>
>

Hi Anthony,

It is a legacy classic asp site that i need to support for at least another
few years. I have tried using visual studio 2005 but it seems to want me to
use my local machine as host and then deploy from there and becuase of third
party components and the fact that the site isnt the default site on the
server there are all sorts of depdendencies on include file locations etc..

It seems I have real problems supporting a legacy site in VS these days..
What would be your reccomendation? other than rewriting the site?

Robert

"Anthony Jones" wrote:
> There are some visual studio groups but frankly what you are trying to do is
> (in computing terms) ancient history. I remember grappling with FP
> extenstions and source safe in older versions of VS but its just not how its
> done these days.
>
> Must you use interdev?
>
>
> --
> Anthony Jones - MVP ASP/ASP.NET

I found a blog article which solved part of the problem I was describing but
did not resolve the whole problem. I have compromised instead.

It seems you must co locate VSS with the website or inrterdev does not work
so the root cause was the location of sourcesafe.ini

The frontpage authentication issues was because i was using host headers and
the loopback security check was failing.. this article explains

http://blog.crowe.co.nz/archive/2005/11/09/318.aspx

Thanks



>
>

"Robert" <Robert@discussions.microsoft.com> wrote in message
news:15AF10EA-4BEB-48D1-AF4D-028E6CBA050C@microsoft.com...
>
>
> "Anthony Jones" wrote:
>
>
>> There are some visual studio groups but frankly what you are trying to do
>> is
>> (in computing terms) ancient history. I remember grappling with FP
>> extenstions and source safe in older versions of VS but its just not how
>> its
>> done these days.
>>
>> Must you use interdev?
>>
>>
>> --
>> Anthony Jones - MVP ASP/ASP.NET
>>
>>
>
> Hi Anthony,
>
> It is a legacy classic asp site that i need to support for at least
> another
> few years. I have tried using visual studio 2005 but it seems to want me
> to
> use my local machine as host and then deploy from there and becuase of
> third
> party components and the fact that the site isnt the default site on the
> server there are all sorts of depdendencies on include file locations
> etc..
>
> It seems I have real problems supporting a legacy site in VS these days..
> What would be your reccomendation? other than rewriting the site?
>

Here is one approach I have used.

VS 2005 is very simple in that a Web site doesn't even have a project file
it just folder. A local machine runs IIS (if XP the site is the default web
site). The site points to this folder. The VSS database is on a file share
somewhere and VS binds to a project in the sourcesafe for the web site.

Developers checkout files and test locally checking in when done.

In sourcesafe admin create a shadow folder for the website project pointing
at a folder being used as the root of a website running on an IIS server.
When developers check in their code is automatically added to the shadow
which forms an integrated image of the currently checked in state of the
website. If you're brave this could be the live site although I would
recommend it merely be another test site that is used to make sure the
integration is good. I have used WinMerge to compare a live site with a
test site and update the live site.

--
Anthony Jones - MVP ASP/ASP.NET