By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,483 Members | 3,312 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,483 IT Pros & Developers. It's quick & easy.

Visual Studio/SourceSafe Get Latest Version

P: n/a

Visual Studio .NET 2003
Visual SourceSafe 6 (6.0d)

I'm working in a three person team on a reasonably complex Solution -
it currently consists of 9 separate projects (3 of them are plain class
libraries, the others are ASP.NET websites), and we're getting some odd
behaviour when we "Get Latest Version" from within Visual Studio

The structure of the websites is basically:

c:\inetpub\wwwroot\WebsiteServices (this contains the basic, shared
functionality of the sites)
c:\inetpub\wwwroot\WebsiteServices\<Name of subsite> (This contains the
specialised sites)

By default, when each subsite is first created, it is created as a
virtual directory within IIS and set up as an application. However, we
wanted to be able to share session between the various subsites, and so
we turn off this behaviour (through ISM), and delete the web.config
that is created in each of these subdirectories.

What we discovered recently, when we added a new class library to the
solution, was that when the other developers "Get Latest Version" from
within Visual Studio, Visual Studio turns on the "Application" setting
for each subsite. Closing Studio, Getting latest version, and reopening
Studio does not cause this fault.

Is this a know fault? I tried searching here, a general Google search
and on the MSDN website without luck. At least, we believe this is the
fault, but with is only numbering three, and with the new project being
added on one machine, and the problem exhibiting itself on a second, we
only had one machine to attempt to reproduce...

Thanks for reading to the bottom :-)


Nov 19 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.