"Ken Carter" <KenCarter@discussions.microsoft.com> wrote in message
news:C65E92A3-FFB4-4BEF-BFA0-46E6D16FBB0A@microsoft.com...
> Well... the solution was right on but only allowed us to get to the next
> problem. Looks like remote debugging is not supported though a firewall.
> Our
> internal network design has a firewall between the development workstaions
> and the web server we are working on.
>
> We are going to have to try and get a port on the network where the web
> server lives to resolve the issue by the looks of it.
>
> I'm looking at other options on MSDN now to try and possibly debug locally
> on the web server though a remote desktop connection.
>
> "Ken Carter" wrote:
>
>> This was right on target! Thanks... you put an end to hours upon hourse
>> of
>> frustration.
>>
>> "Sylvain Lafontaine" wrote:
>>
>> > It's the folder "/test2" that is set to executable, not the default web
>> > site. Change the setting for this folder to Script only.
>> >
>> > FrontPage 2002 can also give you a similar problem if the folder is
>> > marked
>> > as Write. Uncheck this too if necessary.
>> >
>> > If you still have trouble with the FP 2002 extensions, then use FTP
>> > instead.
>> > In my opinion, FP 2002 extensions should have been scrapped a long time
>> > ago.
>> >
>> > --
>> > Sylvain Lafontaine, ing.
>> > MVP - Technologies Virtual-PC
>> > E-mail: http://cerbermail.com/?QugbLEWINF
>> >
>> >
>> > "Ken Carter" <KenCarter@discussions.microsoft.com> wrote in message
>> > news:4696D399-EF95-4626-B838-03FA0F3EF277@microsoft.com...
>> > > Okay we are pushing out one of our first real web projects with VS
>> > > 2005.
>> > > Setup is as follows:
>> > >
>> > > We have a Windows 2003 Server with IIS 6.0 running on it. FrontPage
>> > > 2002
>> > > server extensions are installed. Framework 2.0 is installed. We have
>> > > a
>> > > default web with a virtual directory that is pointing to another
>> > > drive
>> > > path
>> > > appart from the default wwwroot where the default web is based.
>> > >
>> > > I have created the virtual directory added front page support to the
>> > > web
>> > > and
>> > > then made sure that the FW was set to 2.0.
>> > >
>> > > The problem is that when you try to add a new item from the VS 2005
>> > > IDE
>> > > you
>> > > get the following error returned in a pop up from the IDE.
>> > >
>> > > Unable to add 'C:\Documen ts and Settings\carterk\Local
>> > > Settings\Temp\pbqslcbk.0fa\Default.aspx' to the web. Server error:
>> > > The
>> > > folder
>> > > "/test2" is marked executable. You are not allowed to put files into
>> > > an
>> > > executable folder on this server.
>> > >
>> > > Did a search for this on MSDN and found only one reference.
>> > >
>> > > *** Visual Basic Reference: Error Messages
>> > > Unable to put files in an executable folder
>> > > Your Internet Information Services (IIS) settings for your default
>> > > Web
>> > > server need to be set to Scripts and Executables or you will not be
>> > > able
>> > > to
>> > > complete your Web project creation.
>> > > For a complete description of these settings and instructions, see
>> > > "Setting
>> > > Web Server Permissions" in the IIS documentation.
>> > > ***
>> > >
>> > > I checked the defualt web and it was not set to scripts and
>> > > executables.
>> > > Changed that and had the same results even after restarting the web
>> > > server.
>> > >
>> > > Does anyone have a clue what might be wrong here. User has
>> > > adminstrative
>> > > rights on the server and workstation. Everything looks fine from
>> > > what I
>> > > can
>> > > tell but this is killing this projects dead in its tracks!
>> > >
>> > > HELP!!!
>> >
>> >
>> >

"Sylvain Lafontaine" wrote:

> Maybe:
>
> http://blogs.msdn.com/greggm/archive/2005/02/27/381348.aspx
>
> http://www.kbalertz.com/908099/remote.debugging.Visual.Studio.Windows.Service.aspx
>
> http://www.kbalertz.com/Feedback.aspx?kbNumber=318041
>
> http://msdn2.microsoft.com/en-us/library/bt727f1t.aspx
>
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: http://cerbermail.com/?QugbLEWINF
>
>
> "Ken Carter" <KenCarter@discussions.microsoft.com> wrote in message
> news:F8E18DC7-C2B9-43D7-A888-96F1E2DC562F@microsoft.com...
> > The only reason we are doing the development for this web application from
> > the dev workstation with IIS or PWS is the very firewall that stops remote
> > debug. The data store for this web application exists on the other
> > network.
> > Therefore we thought that by doing the developement on a web server on
> > that
> > network we would be able to work unrestricted.
> >
> > The development team is forced to work around issues such as this because
> > the deadlines for the projects are shorter than the time required to open
> > up
> > access.
> >
> > "Sylvain Lafontaine" wrote:
> >
> >> Install PWS on your local machine and work locally. You can also use the
> >> mini-web server that comes with VS.NET 2005 instead of using PWS or IIS
> >> (but
> >> for some kinds of application only, like applications without uploading).
> >>
> >> You should never
> >>
> >> --
> >> Sylvain Lafontaine, ing.
> >> MVP - Technologies Virtual-PC
> >> E-mail: http://cerbermail.com/?QugbLEWINF
> >>
> >>
> >> "Ken Carter" <KenCarter@discussions.microsoft.com> wrote in message
> >> news:C65E92A3-FFB4-4BEF-BFA0-46E6D16FBB0A@microsoft.com...
> >> > Well... the solution was right on but only allowed us to get to the
> >> > next
> >> > problem. Looks like remote debugging is not supported though a
> >> > firewall.
> >> > Our
> >> > internal network design has a firewall between the development
> >> > workstaions
> >> > and the web server we are working on.
> >> >
> >> > We are going to have to try and get a port on the network where the web
> >> > server lives to resolve the issue by the looks of it.
> >> >
> >> > I'm looking at other options on MSDN now to try and possibly debug
> >> > locally
> >> > on the web server though a remote desktop connection.
> >> >
> >> > "Ken Carter" wrote:
> >> >
> >> >> This was right on target! Thanks... you put an end to hours upon
> >> >> hourse
> >> >> of
> >> >> frustration.
> >> >>
> >> >> "Sylvain Lafontaine" wrote:
> >> >>
> >> >> > It's the folder "/test2" that is set to executable, not the default
> >> >> > web
> >> >> > site. Change the setting for this folder to Script only.
> >> >> >
> >> >> > FrontPage 2002 can also give you a similar problem if the folder is
> >> >> > marked
> >> >> > as Write. Uncheck this too if necessary.
> >> >> >
> >> >> > If you still have trouble with the FP 2002 extensions, then use FTP
> >> >> > instead.
> >> >> > In my opinion, FP 2002 extensions should have been scrapped a long
> >> >> > time
> >> >> > ago.
> >> >> >
> >> >> > --
> >> >> > Sylvain Lafontaine, ing.
> >> >> > MVP - Technologies Virtual-PC
> >> >> > E-mail: http://cerbermail.com/?QugbLEWINF
> >> >> >
> >> >> >
> >> >> > "Ken Carter" <KenCarter@discussions.microsoft.com> wrote in message
> >> >> > news:4696D399-EF95-4626-B838-03FA0F3EF277@microsoft.com...
> >> >> > > Okay we are pushing out one of our first real web projects with VS
> >> >> > > 2005.
> >> >> > > Setup is as follows:
> >> >> > >
> >> >> > > We have a Windows 2003 Server with IIS 6.0 running on it.
> >> >> > > FrontPage
> >> >> > > 2002
> >> >> > > server extensions are installed. Framework 2.0 is installed. We
> >> >> > > have
> >> >> > > a
> >> >> > > default web with a virtual directory that is pointing to another
> >> >> > > drive
> >> >> > > path
> >> >> > > appart from the default wwwroot where the default web is based.
> >> >> > >
> >> >> > > I have created the virtual directory added front page support to
> >> >> > > the
> >> >> > > web
> >> >> > > and
> >> >> > > then made sure that the FW was set to 2.0.
> >> >> > >
> >> >> > > The problem is that when you try to add a new item from the VS
> >> >> > > 2005
> >> >> > > IDE
> >> >> > > you
> >> >> > > get the following error returned in a pop up from the IDE.
> >> >> > >
> >> >> > > Unable to add 'C:\Documen ts and Settings\carterk\Local
> >> >> > > Settings\Temp\pbqslcbk.0fa\Default.aspx' to the web. Server error:
> >> >> > > The
> >> >> > > folder
> >> >> > > "/test2" is marked executable. You are not allowed to put files
> >> >> > > into
> >> >> > > an
> >> >> > > executable folder on this server.
> >> >> > >
> >> >> > > Did a search for this on MSDN and found only one reference.
> >> >> > >
> >> >> > > *** Visual Basic Reference: Error Messages
> >> >> > > Unable to put files in an executable folder
> >> >> > > Your Internet Information Services (IIS) settings for your default
> >> >> > > Web
> >> >> > > server need to be set to Scripts and Executables or you will not
> >> >> > > be
> >> >> > > able
> >> >> > > to
> >> >> > > complete your Web project creation.
> >> >> > > For a complete description of these settings and instructions, see
> >> >> > > "Setting
> >> >> > > Web Server Permissions" in the IIS documentation.
> >> >> > > ***
> >> >> > >
> >> >> > > I checked the defualt web and it was not set to scripts and
> >> >> > > executables.
> >> >> > > Changed that and had the same results even after restarting the
> >> >> > > web
> >> >> > > server.
> >> >> > >
> >> >> > > Does anyone have a clue what might be wrong here. User has
> >> >> > > adminstrative
> >> >> > > rights on the server and workstation. Everything looks fine from
> >> >> > > what I
> >> >> > > can
> >> >> > > tell but this is killing this projects dead in its tracks!
> >> >> > >
> >> >> > > HELP!!!
> >> >> >
> >> >> >
> >> >> >
> >>
> >>
> >>
>
>