Problem updating IIS 6.0 legacy ASP sites via Interdev, VSS2005
intre...@hotmail.com
We are presently migrating to Visual Sourcesafe 2005 as we are staging
our rollout of Visual Studio 2005. In the process, we've come across a
problem. We have several critical legacy ASP sites that will not be
migrated to .NET, and as such must be maintained via InterDev.
Interdev, SS2005, and FPSE don't seem to be working well together.
Our problem is that when a file is checked out from the webserver,
modifed, and checked back in, the content is not changed on the
website. The updated content is reflected in SourceSafe, and the file
is correctly shown to be in the proper checkout folder on the webserver
immediately following checkout via Interdev. The FrontPage "shadow" for
the file shows the correct update time/date/author, so it knows an
update has been made, but the right version isn't published.
Recalculating links from Interdev has no effect.
Our server environment is Windows Server 2003 with SP1, with FP
Extensions version 5.0.2.6738 (which in and of itself bothers me,
because that's the version supposedly suitable only for x64, and our
servers are *not* 64-bit). Clients are Windows XP SP2. The site has had
external source control enabled, and it points to the correct
SourceSafe project path. We suspect at least the possibility of this
problem being related to SP1 on the server side, but also realize this
might be a fundamental problem with the behavior of SS2005 used against
a legacy ASP environment site with older tools.
This is a critical roadblock for us in our deployment/migration to
VS2005. IF SourceSafe is the problem, we obviously can't support having
both versions available simultaneously from the clients that support
both our ASP and our .NET sites. I realize InterDev is a dinosaur, but
there simply isn't an option to migrate these sites to .NET. As a
result, we would greatly appreciate any assistance or ideas anyone
might have to offer regarding why this problem is occurring, and how to
fix it.
Thanks,
dew