Definitions for fpWebPublishFlags

I've googled all about, but haven't found a good reference to what the
fpWebPublishFlags actually mean. Can anyone point me to such definitions?
Specifically, I'm wondering about how to force an overwrite of remote files in the
case of "conflict."

Thanks... Karl
--
.NET: It's About Trust!
http://vfred.mvps.org

Steve
Thu Feb 28 18:14:51 CST 2008

Karl,
Did you see these:
http://msdn2.microsoft.com/en-us/library/aa223232(office.10).aspx

http://msdn2.microsoft.com/en-us/library/aa156163(office.10).aspx
--
Steve Easton
Microsoft MVP FrontPage
FP Cleaner
http://www.95isalive.com/fixes/fpclean.htm
Hit Me FP
http://www.95isalive.com/fixes/HitMeFP.htm


"Karl E. Peterson" <karl@mvps.org> wrote in message news:ez4VUNleIHA.748@TK2MSFTNGP04.phx.gbl...
> I've googled all about, but haven't found a good reference to what the fpWebPublishFlags actually mean. Can
> anyone point me to such definitions? Specifically, I'm wondering about how to force an overwrite of remote
> files in the case of "conflict."
>
> Thanks... Karl
> --
> .NET: It's About Trust!
> http://vfred.mvps.org
>

Karl
Thu Feb 28 19:03:23 CST 2008

Hi Steve --

>> I've googled all about, but haven't found a good reference to what the
>> fpWebPublishFlags actually mean. Can anyone point me to such definitions?
>> Specifically, I'm wondering about how to force an overwrite of remote files in
>> the case of "conflict."
>
> Did you see these:
> http://msdn2.microsoft.com/en-us/library/aa223232(office.10).aspx
>
> http://msdn2.microsoft.com/en-us/library/aa156163(office.10).aspx

Yep, that's the extent of what I've found so far. Pretty much just an enumeration.
I'm after a little deeper explanation of exactly how each of those flags affects
which files are published, and how they may interact with one another. And, there
are apparently even more than what's there. Like fpPublishSynchonrize,
fpPublishUseLastPublishTime, and so on. This is the complete list I see in my
Object Browser:

fpPublishAddToExistingWeb
fpPublishCopyAllFiles
fpPublishCopySubwebs
fpPublishIncremental
fpPublishLoginTempDir
fpPublishNoDeleteUnmatched
fpPublishNone
fpPublishRemoteToLocal
fpPublishSynchronize
fpPublishUsingDav
fpPublishUsingPassiveFtp

I think I pretty much 'get' UsingDav and UsingPassiveFtp, but what praytell would be
the purpose of None? RemoteToLocal seems to make sense, and I can probably guess
some of the others, but it'd sure be nice to see a definitive outline of their
purpose and interaction. For instance, I saw somewhere that AddToExistingWeb should
be used on existing webs, but that if you used it on a new web nothing would be
published. Not the sort of thing you'd intuitively come up with.

But, bottom line, what I *need* to determine is what combo of flags to use to force
the overwrite of remote files, without deleting anything, no matter what? :-)

Thanks... Karl
--
.NET: It's About Trust!
http://vfred.mvps.org

Steve
Fri Feb 29 07:40:53 CST 2008


"Karl E. Peterson" <karl@mvps.org> wrote in message news:Ox1Ej7meIHA.5208@TK2MSFTNGP04.phx.gbl...
> Hi Steve --
>
>>> I've googled all about, but haven't found a good reference to what the
>>> fpWebPublishFlags actually mean. Can anyone point me to such definitions?
>>> Specifically, I'm wondering about how to force an overwrite of remote files in
>>> the case of "conflict."
>>
>> Did you see these:
>> http://msdn2.microsoft.com/en-us/library/aa223232(office.10).aspx
>>
>> http://msdn2.microsoft.com/en-us/library/aa156163(office.10).aspx
>
> Yep, that's the extent of what I've found so far. Pretty much just an enumeration. I'm after a little
> deeper explanation of exactly how each of those flags affects which files are published, and how they may
> interact with one another. And, there are apparently even more than what's there. Like
> fpPublishSynchonrize, fpPublishUseLastPublishTime, and so on. This is the complete list I see in my Object
> Browser:
>
> fpPublishAddToExistingWeb
> fpPublishCopyAllFiles
> fpPublishCopySubwebs
> fpPublishIncremental
> fpPublishLoginTempDir
> fpPublishNoDeleteUnmatched
> fpPublishNone
> fpPublishRemoteToLocal
> fpPublishSynchronize
> fpPublishUsingDav
> fpPublishUsingPassiveFtp
>
> I think I pretty much 'get' UsingDav and UsingPassiveFtp, but what praytell would be the purpose of None?
> RemoteToLocal seems to make sense, and I can probably guess some of the others, but it'd sure be nice to see
> a definitive outline of their purpose and interaction. For instance, I saw somewhere that AddToExistingWeb
> should be used on existing webs, but that if you used it on a new web nothing would be published. Not the
> sort of thing you'd intuitively come up with.
>
> But, bottom line, what I *need* to determine is what combo of flags to use to force the overwrite of remote
> files, without deleting anything, no matter what? :-)
>
> Thanks... Karl
> --
> .NET: It's About Trust!
> http://vfred.mvps.org
Karl,
My "guess" would be:

fpPublishCopyAllFiles _
fpPublishNoDeleteUnmatched

But I'm going to email the PM for SharePoint Designer and see if he can / or will give a better answer.



--

Steve Easton
Microsoft MVP FrontPage
FP Cleaner
http://www.95isalive.com/fixes/fpclean.htm
Hit Me FP
http://www.95isalive.com/fixes/HitMeFP.htm

Steve
Sat Mar 01 14:37:54 CST 2008

Karl,
got an answer from a MSFT programmer who says to use:

WebPublishAddToExistingWeb
WebPublishNoDeleteUnmatched
WebPublishCopyAllFiles

and who also found me a link for the enumeration info
http://msdn2.microsoft.com:80/en-us/library/bb258297.aspx

--

Steve Easton
Microsoft MVP FrontPage
FP Cleaner
http://www.95isalive.com/fixes/fpclean.htm
Hit Me FP
http://www.95isalive.com/fixes/HitMeFP.htm


"Karl E. Peterson" <karl@mvps.org> wrote in message news:ez4VUNleIHA.748@TK2MSFTNGP04.phx.gbl...
> I've googled all about, but haven't found a good reference to what the fpWebPublishFlags actually mean. Can
> anyone point me to such definitions? Specifically, I'm wondering about how to force an overwrite of remote
> files in the case of "conflict."
>
> Thanks... Karl
> --
> .NET: It's About Trust!
> http://vfred.mvps.org
>

Karl
Mon Mar 03 13:48:25 CST 2008

Steve Easton wrote:
>> But, bottom line, what I *need* to determine is what combo of flags to use to
>> force the overwrite of remote files, without deleting anything, no matter what?
>> :-)
>
> My "guess" would be:
>
> fpPublishCopyAllFiles _
> fpPublishNoDeleteUnmatched
>
> But I'm going to email the PM for SharePoint Designer and see if he can / or will
> give a better answer.

I had a similar thought, but my concern was this would also push every file, whether
it was the same or not. Thought, there's gotta be some middle ground. Push all the
different and all the conflicting files, but leave the ones that are the "same"?
--
.NET: It's About Trust!
http://vfred.mvps.org

Karl
Mon Mar 03 13:57:32 CST 2008

Hi Steve --

>> I've googled all about, but haven't found a good reference to what the
>> fpWebPublishFlags actually mean. Can anyone point me to such definitions?
>> Specifically, I'm wondering about how to force an overwrite of remote files in
>> the case of "conflict."
>
> got an answer from a MSFT programmer who says to use:
>
> WebPublishAddToExistingWeb
> WebPublishNoDeleteUnmatched
> WebPublishCopyAllFiles

That just doesn't seem to be "it", or I'm not doing a good job of communicating what
I'm after. For some reason, I have a web where if I publish manually (in FrontPage
2003), it tells me that some files are "in conflict" and asks me what to do. In
this case, my response is to "overwrite remote" files. That's what I'm after. It
doesn't send every file, just those that are in conflict. But when I do it in code,
I try like this:

.ActiveWeb.Publish m_PublicUrl, fpPublishIncremental Or
fpPublishAddToExistingWeb, user, pass

And those files that FrontPage finds "in conflict" are left unchanged on the remote
system. I'd hoped there was a combination short of pushing *every* file that would
still send these trouble files. I really, truly only want to publish the changed
files. But it's not happening. Actually, I suppose I could test the idea with the
CopyAll flag, but I'm almost betting that's not going to override the "in conflict"
detection either, given the Incremental flag isn't.

> and who also found me a link for the enumeration info
> http://msdn2.microsoft.com:80/en-us/library/bb258297.aspx

That's the list I was looking for! :-)

Sure as heck is a confusing set of flags, isn't it? I've yet to decipher the
twisted "logic" behind that WebPublishAddToExistingWeb flag!

Thanks... Karl
--
.NET: It's About Trust!
http://vfred.mvps.org

Steve
Mon Mar 03 15:24:35 CST 2008


"Karl E. Peterson" <karl@mvps.org> wrote in message news:OWUSSjWfIHA.4056@TK2MSFTNGP06.phx.gbl...
> Hi Steve --
>
>>> I've googled all about, but haven't found a good reference to what the
>>> fpWebPublishFlags actually mean. Can anyone point me to such definitions?
>>> Specifically, I'm wondering about how to force an overwrite of remote files in
>>> the case of "conflict."
>>
>> got an answer from a MSFT programmer who says to use:
>>
>> WebPublishAddToExistingWeb
>> WebPublishNoDeleteUnmatched
>> WebPublishCopyAllFiles
>
> That just doesn't seem to be "it", or I'm not doing a good job of communicating what I'm after. For some
> reason, I have a web where if I publish manually (in FrontPage 2003), it tells me that some files are "in
> conflict" and asks me what to do. In this case, my response is to "overwrite remote" files. That's what
> I'm after. It doesn't send every file, just those that are in conflict. But when I do it in code, I try
> like this:
>
> .ActiveWeb.Publish m_PublicUrl, fpPublishIncremental Or fpPublishAddToExistingWeb, user, pass
>
> And those files that FrontPage finds "in conflict" are left unchanged on the remote system. I'd hoped there
> was a combination short of pushing *every* file that would still send these trouble files. I really, truly
> only want to publish the changed files. But it's not happening. Actually, I suppose I could test the idea
> with the CopyAll flag, but I'm almost betting that's not going to override the "in conflict" detection
> either, given the Incremental flag isn't.
>
>> and who also found me a link for the enumeration info
>> http://msdn2.microsoft.com:80/en-us/library/bb258297.aspx
>
> That's the list I was looking for! :-)
>
> Sure as heck is a confusing set of flags, isn't it? I've yet to decipher the twisted "logic" behind that
> WebPublishAddToExistingWeb flag!
>
> Thanks... Karl
>
Karl,
The way I usually resolve conflicts is to open the local and then in folder view click "Remote web site,"
So I have them both open.
I then Ctrl + click the local file(s) for each remote file that shows a conflict and then right click and
select "Publish selected files."


--

Steve Easton

Karl
Mon Mar 03 16:29:50 CST 2008

Steve Easton wrote:
> The way I usually resolve conflicts is to open the local and then in folder view
> click "Remote web site," So I have them both open.
> I then Ctrl + click the local file(s) for each remote file that shows a conflict
> and then right click and select "Publish selected files."

I can certainly do that, but for some reason I seem to keep generating this conflict
situation. I guess I'll need to pay more attention to how that's happening. In all
cases, I want to push out the local files, and overwrite the remote.
--
.NET: It's About Trust!
http://vfred.mvps.org