we have this problem for certain projects as well.
 
we have apps in a couple of places
1). in the root of the website
2). in a folder on same drive
 
we are able to connect to projects in the root of the website through
VS.
for the other apps in the seperate folder we cannot connect.
 
we are still in the process of figuring out why this is, however after
talking to MS they said that remote access through VS is only possible
to the root of the website ... kinda wierd.
 
our solution to this point has been to develop locally for apps that
are not in the root, then move the code to seperate folder on the dev
server, then create the virtual directories,etc,  then go throught the
testing process.
for apps in the root we can connect through VS.
 
we are all members of the VSDevelopers group and the Debuggers group on
the server.
one guess for us is that our Domain Controller manages the permissions
on that segment of the network, so something could be goofy there.
 
it is a problem though.
i have been watching this thread hoping to get a solution.
 
 
 


>>> [EMAIL PROTECTED] 02/03/2005 1:39:04 PM >>>


The boss says when I add pages go physically to the the server and 
use the MMC to recalculate web and check server extensions.  I am 
not quite sure what is going on. I thought ISAPI or whatever was 
smart enough to figure out that new pages had been added.
Anyway, something did go wrong when I added a page yesterday so I 
will do what he says, hopefully it will correct the problem.  
  

--- In [email protected], "Peter Brunone" 
<[EMAIL PROTECTED]> wrote:
> 
>    What sort of problems?  I don't know of any, but then again, I 
rarely develop pages in VS.NET (only when supporting a customer 
who's using ELB in a project).
> 
>  From: "scaevola637" [EMAIL PROTECTED]
> 
> Does opening it with FPSE cause in problems when I make changes or 
> add aspx pages? You are correct in saying it is not available via 
> network drive.
> 
> --- In [email protected], "Peter Brunone" 
> wrote:
> > 
> >    Oh.  If your server isn't accessible by network drive, then 
I'm 
> afraid you're going to have to use FPSE (or just run a copy on 
your 
> local web server and upload it when ready).
> > 
> > From: "scaevola637" [EMAIL PROTECTED]
> > 
> > The trouble is I am trying to Open a project on the web server 
and 
> > it only lets me open with Front Page Server Extensions. Is that 
> the 
> > normal sequence of events? Does it tell me anything about the 
> > project that it can only be opened with Front Page Server 
> Extensions?
> > 
> > --- In [email protected], "Peter Brunone" 
> > wrote:
> > > 
> > >    Ah, good old VS.NET.  Basically, it offers FPSE 
integration, 
> > which I always decline in favor of using the file system.  If 
you 
> > don't have the extensions installed/enabled (I avoid them 
whenever 
> > possible), you'll want to say no to that.
> > > 
> > > From: "scaevola637" [EMAIL PROTECTED]
> > > 
> > > What does
> > > 
> > > "Do you want to open using Front Page Server Extensions?" mean 
> on 
> > > Vs.NET? Have you ever seen that message?
> > > 
> > > --- In [email protected], "Peter Brunone" 
> > > wrote:
> > > > In a nutshell:
> > > > 
> > > > http://tinyurl.com/6kvo4
> > > > 
> > > > From: "scaevola637" [EMAIL PROTECTED]
> > > > 
> > > > What are FRont page server extensions?
> > 
> > 
> > [Non-text portions of this message have been removed]
> 
> Yahoo! Groups Links
> 
> 
> 
> 
> 
> 
> 
> [Non-text portions of this message have been removed]




Yahoo! Groups Links
To visit your group on the web, go to:
http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/
  To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.




[Non-text portions of this message have been removed]



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to