Dilemma publishing from local to test to production

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Our shop currently has three areas of webdevelopment. Our communications
department uses FrontPage, I do the ColdFusion which is being phased out and
our IS Applications area is using .Net.

Local development is on the individual's pc. Testa dn Production are on a
webserver at our ISP.

Communications used to develop locally and publish to Production. I'd do a
combination. Our applications people are new to web but have a routine they
follow for anything they develop. So now we're all working local to test to
production.

Communications publishes from local to test. When they try to publish from
test to production they get a list of files in conflict which are coldfusion
and .net pages.

If they are going to publish from test to production we only want them to
publish FrontPage content. Not ColdFusion and .net. Is there a way to filter
out non-FrontPage content?
 
Can you deselect entire folders or do you have to do them one at a time?

Once you select them do you have to do it each time or will it hold that
selection?

btw... read the blurb on your MVP and looked at some of your work. I'm
impressed.
 
No, you cannot mark an entire folder at once. However, there is an
addin at www.jimcoaddins.com that will do this. See "Selective
Publish" on the Software->addins page.
Once marked, the selection will hold until changed.
 
Does this get put on the users pc?

Ronx said:
No, you cannot mark an entire folder at once. However, there is an
addin at www.jimcoaddins.com that will do this. See "Selective
Publish" on the Software->addins page.
Once marked, the selection will hold until changed.
Click to expand...
 
Yes, it installed on each PC.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
 
Back
Top