Virtual disk

[Alessandro Fagioli]

In our company several people works on the same projects.
Since everyone has the source code in a different position, we have chosen
to create a vitual disk (P:) using the SUBST command.
This way references are always toward this disk and are the same for
everyone.
We develop using both VB6 and .NET and never had problems.

Now that we'are starting to develop using ASP.NET we're experiencing a
problem; we are not able to publish an ASP application from a virtual disk
P: (we have IIS5 and Windows XP Professional in every computers)
We are forced to open our project without to pass from virtual disc and then
we can publish them.
This operation breaks our organizations and also our source code integration
(using Perforce)
Any suggestion?

Thanks in advance

Regards

Alessandro Fagioli

[Karl Seguin]

Alessandro:
If you are doing team development and you are running into this kind of
problems, you should, without a doubt, read:
http://msdn.microsoft.com/library/de...asp?frame=true

while it deals with visual source safe, we've achieved success with
ClearCase using this approach. It just totally works (pay particularly
close attention to chapters 3 and 4).

Hope this helps,
Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"Alessandro Fagioli"
<NO_SPAM_alessandro.fagioli_NO_SPAM@NO_SPAM_engine ering.it> wrote in message
news:u4**************@TK2MSFTNGP14.phx.gbl...

In our company several people works on the same projects.
Since everyone has the source code in a different position, we have chosen
to create a vitual disk (P:) using the SUBST command.
This way references are always toward this disk and are the same for
everyone.
We develop using both VB6 and .NET and never had problems.

Now that we'are starting to develop using ASP.NET we're experiencing a
problem; we are not able to publish an ASP application from a virtual disk
P: (we have IIS5 and Windows XP Professional in every computers)
We are forced to open our project without to pass from virtual disc and then we can publish them.
This operation breaks our organizations and also our source code integration (using Perforce)
Any suggestion?

Thanks in advance

Regards

Alessandro Fagioli