the future of fpse

Ive been using FPSE to deploy my asp-sites through VS2005 for some time now.
But my web hosting provider has now decided to discontinue using it since MS
has stopped supporting it... ? I dont get it. And I dont really understand
why it is called FrontPage 2002 SE. Im not using FrontPage for anything in
perticular, except the SE-part. Shouldnt this feature (direct deploy through
VS) be standard in some way? I mean it is quite useful ... or is there a
better (new) way I have missed?

Re: the future of fpse

Frontpage Server Extensions were owned by the Office team. Visual Studio is
merely an FPSE client (that can talk to an FPSE enabled server), but can
also use other methods of publishing content (e.g. file shares etc). The
Office team decided to stop supporting FPSE when the relevant Office product
ended supportability.

That all said, the IIS PG has outsourced maintenance of FPSE to a company
called "Ready to Run". There will be a version of FPSE available for Windows
Server 2008 / IIS 7.0 from www.iis.net.

Additionally, FPSE on Windows Server 2003 will be supported as long as
Windows Server 2003 is.

The only supportability issue comes if your hosting company is using Windows
Server 2000, or FPSE for UNIX. Those two options are no longer supported.

Cheers
Ken

"Maximilian" wrote in message
news:F73009D1-0F76-4EA3-83EB-863A58E3E59A@microsoft.com...
> Ive been using FPSE to deploy my asp-sites through VS2005 for some time
> now.
> But my web hosting provider has now decided to discontinue using it since
> MS
> has stopped supporting it... ? I dont get it. And I dont really understand
> why it is called FrontPage 2002 SE. Im not using FrontPage for anything in
> perticular, except the SE-part. Shouldnt this feature (direct deploy
> through
> VS) be standard in some way? I mean it is quite useful ... or is there a
> better (new) way I have missed?

Re: the future of fpse

I never heard of this going out of support... its a feature of Win2k3 so i
highly doubt that...

The reason its called FPSE is because it was originally desiged to work with
FP but, thats really no longer the case.. the FPSE is basically just an
extension to the HTTP protocol to allow certain commands that will allow you
to manipulate files and IIS to some extent.

Also, more proof that its still supported is that the new Sharepoint system
has its own designer application (Sharepoint Designer, which is much like
FP, but specifically for sharepoint) which was only just recently released,
uses FPSE to work as well.

There are some security issues with using FPSE and perhaps thats why they
stopped using it.. but as far as i know its still supported and standard.

Justin

"Maximilian" wrote in message
news:F73009D1-0F76-4EA3-83EB-863A58E3E59A@microsoft.com...
> Ive been using FPSE to deploy my asp-sites through VS2005 for some time
> now.
> But my web hosting provider has now decided to discontinue using it since
> MS
> has stopped supporting it... ? I dont get it. And I dont really understand
> why it is called FrontPage 2002 SE. Im not using FrontPage for anything in
> perticular, except the SE-part. Shouldnt this feature (direct deploy
> through
> VS) be standard in some way? I mean it is quite useful ... or is there a
> better (new) way I have missed?

Re: the future of fpse

Thanks for your replies Ken and Justin!

I will try to convince them to install FPSE again ... since they are running
win server 2003/IIS6 it shouldnt be a support-issue, as you say. Maybee they
have missunderstood it when the office-team ended their support ...

But yes it could be a security-issue also ...

But ... is there any other way to administer/create/deploy/update a remote
web hosting account similar to FPSE, but not nessessarily from Visual
Studio/FrontPage? I mean if the hosting provider doesnt have a tool for this
which they almost never have... I often need to set write permissions to some
folder, create new application-folders in IIS etc but since I dont have
direct access to the remote IIS this becomes a problem. I know/think its a
common problem which apparently has been done using FPSE for some time now...
Hmmm. I think its a little odd that we are still using technology from 2002
for this purpose, should there have emerged any newer and better ways for
this ... more secure .. more flexible etc ... ?

Re: the future of fpse

i was actually just thinking that the other day... maybe they'll have
something soon, but i havent heard of anything yet... i think maybe your
best option is to create locally and then publish via FTP with VS

other than that i dont know of any products which sit on top of IIS and
allow you to dev and just deploy to a server.. probably something out there
though..

"Maximilian" wrote in message
news:0C9CA0A4-6AC0-4C75-93AE-8612F0223118@microsoft.com...
> Thanks for your replies Ken and Justin!
>
> I will try to convince them to install FPSE again ... since they are
> running
> win server 2003/IIS6 it shouldnt be a support-issue, as you say. Maybee
> they
> have missunderstood it when the office-team ended their support ...
>
> But yes it could be a security-issue also ...
>
> But ... is there any other way to administer/create/deploy/update a remote
> web hosting account similar to FPSE, but not nessessarily from Visual
> Studio/FrontPage? I mean if the hosting provider doesnt have a tool for
> this
> which they almost never have... I often need to set write permissions to
> some
> folder, create new application-folders in IIS etc but since I dont have
> direct access to the remote IIS this becomes a problem. I know/think its a
> common problem which apparently has been done using FPSE for some time
> now...
> Hmmm. I think its a little odd that we are still using technology from
> 2002
> for this purpose, should there have emerged any newer and better ways for
> this ... more secure .. more flexible etc ... ?

Re: the future of fpse

As I understand VS - later versions support WebDAV as well.

FTP in IIS 7.0 will support FTPS, so that will be more secure than
traditional FTP.

Cheers
Ken

"Justin Rich" wrote in message
news:uyABt%23HHIHA.4296@TK2MSFTNGP04.phx.gbl...
>i was actually just thinking that the other day... maybe they'll have
>something soon, but i havent heard of anything yet... i think maybe your
>best option is to create locally and then publish via FTP with VS
>
> other than that i dont know of any products which sit on top of IIS and
> allow you to dev and just deploy to a server.. probably something out
> there though..
>
> "Maximilian" wrote in message
> news:0C9CA0A4-6AC0-4C75-93AE-8612F0223118@microsoft.com...
>> Thanks for your replies Ken and Justin!
>>
>> I will try to convince them to install FPSE again ... since they are
>> running
>> win server 2003/IIS6 it shouldnt be a support-issue, as you say. Maybee
>> they
>> have missunderstood it when the office-team ended their support ...
>>
>> But yes it could be a security-issue also ...
>>
>> But ... is there any other way to administer/create/deploy/update a
>> remote
>> web hosting account similar to FPSE, but not nessessarily from Visual
>> Studio/FrontPage? I mean if the hosting provider doesnt have a tool for
>> this
>> which they almost never have... I often need to set write permissions to
>> some
>> folder, create new application-folders in IIS etc but since I dont have
>> direct access to the remote IIS this becomes a problem. I know/think its
>> a
>> common problem which apparently has been done using FPSE for some time
>> now...
>> Hmmm. I think its a little odd that we are still using technology from
>> 2002
>> for this purpose, should there have emerged any newer and better ways for
>> this ... more secure .. more flexible etc ... ?
>
>

Re: the future of fpse

FPSE is really legacy code that needs to die a quick and painless
death, but unfortunately there are so many legacy clients out there
that IIS needs to support some form of it for years to come EVEN
THOUGH Microsoft has no desire to progress that codebase. Believe me,
no one in Microsoft wants to own or have anything to do with FPSE
(hence the outsourcing).

The idea with IIS7 and its distributed configuration system is that
you can use any means to UPLOAD / MODIFY web.config files to manage
your application's IIS-related configuration. No more custom and buggy
FPSE Client and ServerExtension code to maintain -- you just send
web.config files back and forth -- which can be done via standard
protocols like FTP/FTPS, WebDAV.

And it fits with the remote UI delegated admin story in IIS7 as well.
No coincidence.
:-)

And ultimately, this is a cleaner and more maintainable delegation/
publication story than the current mess.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//






On Nov 1, 5:06 am, "Justin Rich" wrote:
> i was actually just thinking that the other day... maybe they'll have
> something soon, but i havent heard of anything yet... i think maybe your
> best option is to create locally and then publish via FTP with VS
>
> other than that i dont know of any products which sit on top of IIS and
> allow you to dev and just deploy to a server.. probably something out there
> though..
>
> "Maximilian" wrote in message
>
> news:0C9CA0A4-6AC0-4C75-93AE-8612F0223118@microsoft.com...
>
>
>
> > Thanks for your replies Ken and Justin!
>
> > I will try to convince them to install FPSE again ... since they are
> > running
> > win server 2003/IIS6 it shouldnt be a support-issue, as you say. Maybee
> > they
> > have missunderstood it when the office-team ended their support ...
>
> > But yes it could be a security-issue also ...
>
> > But ... is there any other way to administer/create/deploy/update a remote
> > web hosting account similar to FPSE, but not nessessarily from Visual
> > Studio/FrontPage? I mean if the hosting provider doesnt have a tool for
> > this
> > which they almost never have... I often need to set write permissions to
> > some
> > folder, create new application-folders in IIS etc but since I dont have
> > direct access to the remote IIS this becomes a problem. I know/think its a
> > common problem which apparently has been done using FPSE for some time
> > now...
> > Hmmm. I think its a little odd that we are still using technology from
> > 2002
> > for this purpose, should there have emerged any newer and better ways for
> > this ... more secure .. more flexible etc ... ?- Hide quoted text -
>
> - Show quoted text -