08-16-04 10:56 PM
Mark many thanks for your advice,
Forgive my ignorance. When you say "connect up directly" do you mean using
it as a "Remote Web site"? I can see your logic, however I'm on the learning
curve here with web publishing so if you've got time a little more detail
would be helpful.
Equally I would of thought there would be a resource out there saying
"deslect x, y and z" and then things should work!! Okay you'd expect the odd
problem with this approach, but these days I like to frontload my learning
with the obvious ones rather than create a complete mess later.
By the way my hosting company said to avoid FP 2003 and particularly
'themes' present a problem for them today with the people attempting to use
FP 2003 with their server setup. I know I can always dump my provider, but I
like them in other ways (this does not mean they are cheap). I figure they
are just a bit risk averse in upgrading which in my experience is no bad
thing.
Séamus
"Mark Fitzpatrick" wrote:
> Luckily, there aren't so many parts of FP 2003 that won't work. Mostly the
> changes that evolved in the FP 2002 Server Extensions and Windows SharePoi
nt
> Services 2.0 are in regards to how the sharepoint features are organized a
nd
> referred to. One of the things I like to do is to connect up to the server
> that is running the extensions directly and seeing what features FP
> disables. FP 2003 is able to adapt to the extension features that are
> available to the current extensions. If you're running IIS locally make su
re
> that you have the 2002 extensions installed to work against and FP should
> match the featureset properly.
>
> Hope this helps,
> Mark Fitzpatrick
> Microsoft MVP - FrontPage
>
> "Seamus" <Seamus@discussions.microsoft.com> wrote in message
> news:A212EAA0-0F98-49A2-928D-850181876ECA@microsoft.com...
>
>
>
[ Post a follow-up to this message ]
|