FP 2003 and sharepoint services

  • Thread starter Thread starter Steve
  • Start date Start date
S

Steve

Anyone get this to work as a viable replacement to FP
extensions 2002 with Win 2003 server? I keep getting a
login prompt on my default site I set up
 
My concern is no the login process it is the inability to
set up a outside site that allows anonymous browsing. It
seems to me the is a bug that does not allow anonymous
access to even be set. Also why is it that asp and aspx
pages can no longer be published to a sharepoint enabled
site? How exactly would I use web bots now that FP
extensions are gone and why cant php be enabled on a
sharepoint enabled web even though it is enabled in the
appropriate places?

I am feeling that Microsoft is trying to force users away
from public site publishing and into enterprise only
development. If this is the case I know a lot of us will
be upset.
 
My concern is no the login process it is the inability to
set up a outside site that allows anonymous browsing.
Click to expand...

A SharePoint web site is almost always used within an Intranet or other
private context, as the purpose of a SharePoint web site is chiefly
collaboration and sharing of documents and files of various types. You can
set one up as a public anonymous web site if you want to, but this would
have to be done through IIS Admin, not FrontPage.
Also why is it that asp and aspx
pages can no longer be published to a sharepoint enabled
site? How exactly would I use web bots now that FP
Click to expand...

ASP and ASPX pages can be used in a SharePoint web site. In fact, SharePoint
pages are primarily ASPX pages. What you cannot do is to use the FrontPage
wizards to create ASP.Net web applications (or anything else which requires
FrontPage server extensions to create) on a SharePoint web site. This is
because SharePoint web sites can not have FrontPage server extensions, which
are necessary to use in order to create ASP.Net and ASP applications using
the FrontPage Database Results components. If, for example, you use Visual
Studio.Net or Web Matrix to create ASP.Net pages, and put them into a
SharePoint site, they will certainly work.
I am feeling that Microsoft is trying to force users away
from public site publishing and into enterprise only
development. If this is the case I know a lot of us will
be upset.
Click to expand...

It is a free market. Microsoft can't force anyone to do anything. As I
mentioned, SharePoint web sites are a special kind of site for a special
purpose (collaboration and sharing within a team). FrontPage has ADDED
functionality for working with SharePoint sites. It has taken away nothing.
If you want to use FrontPage server extensions, just don't use them in a
SharePoint web site.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
Big Things are made up of
Lots of Little Things.
 
I think you miss my point. Microsoft came out with Front
Page 2003. They announce the end of Front Page
Extensions. Sharepoint Services are the replacement for
them. They however do not operate in the same way. You
can not build and publish a site to a sharepoint enabled
web as you were able to publish to a Front Page Extension
enabled web. You can not publish asp or asp.net pages to
a site that is sharepoint enabled. You can not allow the
home directory in a sharepoint enabled web to be
anonymous. You can not enable anonymous access through
the IIS administration snap in on the web that is
sharepoint enabled. You can not publish or even create a
data driven page in front page 2003 that is not a
sharepoint enabled web. You can not use php in a
sharepoint enabled web. I spent the past three days
testing and proving this. If you know of other
inforamtion then I would love to hear it.
 
There's the problem, and it will likely be a very common one. Windows
SharePoint Services is absolutely NOT a replacement for the FrontPage Server
Extensions. It is a completely separate technology. If you had to point to
a technology that is "replacing" Server Extensions, it would have to be
WebDAV, not WSS.

FrontPage Server Extensions will still be used in the majority of the public
Web sites using FrontPage.

--
Jim Cheshire
Jimco Add-ins
http://www.jimcoaddins.com
===================================
Co-author of Special Edition
Using Microsoft FrontPage 2003
Order it today!
http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?userid=2UELLO8CHO&isbn=0789729547&itm=7
 
Steve said:
My concern is no the login process it is the inability to
set up a outside site that allows anonymous browsing. It
seems to me the is a bug that does not allow anonymous
access to even be set.
Click to expand...

I haven't tried it, but I suppose you could just grant access to the
ASPNET or IUSR_ said:
Also why is it that asp and aspx pages can no longer be published to a
sharepoint enabled site?
Click to expand...

They wouldn't conform to the architecture of a SharePoint portal site.

In many cases, SharePoint can do a lot more than FrontPage without the
need to write code. However, if you *do* need to write code, you need
to do it by writing a new Web Part. Browse:

http://msdn.microsoft.com/library/library/en-us/spptsdk/html/CreateABasicWP.asp
How exactly would I use web bots now that FP extensions are gone
Click to expand...

Some Web Bots still work if you install the FP Server Extensions on
the WSS site, but most of the browse-time bots don't. Among those that
don't work are Save Results To Database, Database Results Wizard, and
Web Search. As compensation, SharePoint Team Sites provides more
powerful facilities in each of these areas.
and why cant php be enabled on a sharepoint enabled web even though it is
enabled in the appropriate places?
Click to expand...

The pages wouldn't conform to the architecture of a SharePoint portal
site.
I am feeling that Microsoft is trying to force users away
from public site publishing and into enterprise only
development. If this is the case I know a lot of us will
be upset.
Click to expand...

No. With Windows SharePoint Services, Microsoft is trying to deliver a
great tool for developers, users, and administrators who want an
enterprise-level portal solution.

If you're not developing, using, or administering an enterprise
portal, then Windows SharePoint Services is probably the wrong
environment for you. Keep using the FrontPage 2002 Server Extensions.

WSS is decidedly *not* the next release of (or a replacement for) the
FrontPage Server Extensions.

Jim Buyens
Microsoft FrontPage MVP
(e-mail address removed)
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*
 
Oh my! Microsoft is going to have a bit of trouble then.
THey are advertizing sharepoint services as the
replacement for Front page extensions. I hope it gets
cleared up soon
 
I agree. I'm not sure where the impression that SharePoint was a replacement
for FrontPage server extensions came from, but it is certainly not true.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
Big Things are made up of
Lots of Little Things.
 
Steve said:
I think you miss my point. Microsoft came out with Front Page 2003.
Yes.

They announce the end of Front Page Extensions. Sharepoint Services are
the replacement for them.
Click to expand...

No and no.
They however do not operate in the same way. You
can not build and publish a site to a sharepoint enabled
web as you were able to publish to a Front Page Extension
enabled web. You can not publish asp or asp.net pages to
a site that is sharepoint enabled. You can not allow the
home directory in a sharepoint enabled web to be
anonymous. You can not enable anonymous access through
the IIS administration snap in on the web that is
sharepoint enabled. You can not publish or even create a
data driven page in front page 2003 that is not a
sharepoint enabled web. You can not use php in a
sharepoint enabled web. I spent the past three days
testing and proving this. If you know of other
inforamtion then I would love to hear it.
Click to expand...

All true. If you need any of these things, you should stay on
the FrontPage 2002 Server Extensions platform.

What's the matter with that?

If Microsoft had released FrontPage 2003 Server Extensions, an
upgrade in name only, would you feel any better?

Anyway, since you're an ASP, ASP.NET, and/or PHP programmer, I bet
you hardly ever use Save Results, Discussions, Hit Counter, or any
of the other browse-time bots. So publishing is really the only
feature of the server extensions you use. And if FTP or WebDAV
publishing worked perfectly, you wouldn't even need the server
extensions for that.

And that, most likely, is the reason for any discussion you might
hear about the FrontPage Server Extensions fading away.

Jim Buyens
Microsoft FrontPage MVP
(e-mail address removed)
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*
 
Sorry but this is a direct quote from the FAQ for front
page 2003:
<http://www.microsoft.com/office/preview/frontpage/faq.asp
Microsoft has continued to make investments in FrontPage
2003 to enhance the overall customer experience, based on
customer feedback and the changing role of server
extensions in our overall product offerings. As we
examined our options, it became clear that the best
solution was to create a new and radically more powerful
server story-Windows SharePointT Services-and eliminate
the need for server extensions beginning with FrontPage
2003. Today, the optimal combination for FrontPage is to
use FrontPage 2003 in combination with Windows SharePoint
Services. This allows you to access the entire set of new
functionality in FrontPage 2003, along with improvement
to the way you did things in FrontPage 2002 and other
previous versions of FrontPage. For more information
about these changes, see FrontPage server configuration
options and features.

here is a quote from the server configuration options for
frontpage:

When combined, FrontPage 2003 and Windows SharePoint
Services eliminate the need for Server Extensions.

<http://www.microsoft.com/office/preview/frontpage/servers
..asp>

These are directly telling the user that extensions are
no longer needed when in fact they are very much needed
for front page "bot" usage and asp page coding.
 
You are basing your conclusion on only one small piece of information. Note
the last sentence in that quote:

"For more information about these changes, see FrontPage server
configuration options and features."

That is a link to a chart that shows you what features are offered by each
server configuration option. It is pretty clear that if you want to use
FrontPage webbots, you must use the Server Extensions and not Windows
SharePoint Services.

With that said, I think what you are experiencing is the frustration of
having read information from marketing instead of people who understand the
technology. It's an understandable conclusion that you have drawn.
However, I would strongly disagree that WSS is a replacement for FPSE.
Those who work on the technology at Microsoft would likely agree.

--
Jim Cheshire
Jimco Add-ins
http://www.jimcoaddins.com
===================================
Co-author of Special Edition
Using Microsoft FrontPage 2003
Order it today!
http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?userid=2UELLO8CHO&isbn=0789729547&itm=7
 
Thank you Jim you have been most helpful. I drew these
conclusions from setting up a test box and beating up the
sharepoint services. I do still believe they meaning
Microsoft's web team and marketing need to reword this
information for Frontpage 2003. There is little detailed
info on the technical side of this (at the moment) and
what little is there is rather confusing and gives a
false sence of hope that extensions can be replaced by a
more robust solution.
 
Steve said:
My main problem is misinformation. I was lead to believe
sharepoint services would replace extensions and
eliminate the need to have them on my server. In truth
they are still needed to give funcionality to FP
developers who utilize the need for said extensions.
Microsoft needs to clear this up in my opinion.
Click to expand...

Yes, Windows SharePoint Services is new and therefore receiving all
the hype. It's a great platform for building corporate portal sites,
and other Microsoft products are going to have tie-ins to WSS. But
it's certainly not all things to all people.

Jim Buyens
Microsoft FrontPage MVP
(e-mail address removed)
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*
 
Back
Top