Application.PublishProjectPlan - how to suppress the ProjectWorkspace dialogbox

[andy.novak]

In using Application.PublishProjectPlan, how do you suppress the
dialog box in Project Pro 2007 which asks the user if they wish to
create a Project Workspace at this time?

I'd like to whip through all my projects in the database and publish
without having to press the "Publish" button each time this dialog box
pops up.

Thanks,
Andy Novak
University of North Texas

 

[Bryant Likes]

[snip]

I'd like to whip through all my projects in the database and publish
without having to press the "Publish" button each time this dialog box
pops up.

You might be better off using a server-side approach instead of VBA. Take a
look at this post which describes how to create an auto-publish program
(source included):

http://blogs.msdn.com/project_progr...s-based-off-a-project-custom-field-value.aspx

The sample only publishes based on a custom field, but you can skip that
code if you want to publish every project.

 

[andy.novak]

[snip]

I'd like to whip through all my projects in the database and publish
without having to press the "Publish" button each time this dialog box
pops up.

You might be better off using a server-side approach instead of VBA. Take a
look at this post which describes how to create an auto-publish program
(source included):

http://blogs.msdn.com/project_programmability/archive/2007/12/10/publ...

The sample only publishes based on a custom field, but you can skip that
code if you want to publish every project.

Thanks. I've got that C# program working already. I just wanted to
try to figure out how to do that in VBA.

 

[Stephen Sanderlin]

Is disabling the auto-provisioning out of the question?

--
Stephen Sanderlin
Owner/Founder - EPMFAQ
http://www.epmfaq.com/
http://forums.epmfaq.com/

EPM Solutions Architect / Principal Consultant - BT Professional
Services
http://bt.ins.com/

This electronic message, along with any information, advice, and
opinions it contains, are mine alone and are not representative of my
employer. All information is provided in "GOOD FAITH" and on an "AS IS"
basis only. I provide no presentations or warranties, express or
implied, including implied warranties of fitness for a particular
purpose, merchantability, title, and noninfringement. I strongly advise
you to extensively test any changes, workarounds, or techniques
described herein on a development system prior to implementation in a
production environment, and you are hereby notified that I bear no
responsibility whatsoever for any loss, harm, or otherwise negative
outcomes resulting from your actions, whether or not said actions were
a result of this electronic message, directly or indirectly.

 

[andy.novak]

Is disabling the auto-provisioning out of the question?

--
Stephen Sanderlin
Owner/Founder - EPMFAQhttp://www.epmfaq.com/http://forums.epmfaq.com/

EPM Solutions Architect / Principal Consultant - BT Professional
Serviceshttp://bt.ins.com/

This electronic message, along with any information, advice, and
opinions it contains, are mine alone and are not representative of my
employer. All information is provided in "GOOD FAITH" and on an "AS IS"
basis only. I provide no presentations or warranties, express or
implied, including implied warranties of fitness for a particular
purpose, merchantability, title, and noninfringement. I strongly advise
you to extensively test any changes, workarounds, or techniques
described herein on a development system prior to implementation in a
production environment, and you are hereby notified that I bear no
responsibility whatsoever for any loss, harm, or otherwise negative
outcomes resulting from your actions, whether or not said actions were
a result of this electronic message, directly or indirectly.

An option as I understand it would be to have the system automatically
create a site for each project (which I believe would result in the
workspace dialogbox not popping up each time you publish). However,
many of our projects are pretty small (2-4 weekers) that would not
require a project workspace.

 

[Stephen Sanderlin]

I'm sorry, you're right, I meant "enabling" the auto-provisioning.

The workspaces don't take up much room, so I wouldn't really worry
about them being created and not used. If it's an issue, you can always
delete them later.

--
Stephen Sanderlin
Owner/Founder - EPMFAQ
http://www.epmfaq.com/
http://forums.epmfaq.com/

EPM Solutions Architect / Principal Consultant - BT Professional
Services
http://bt.ins.com/

This electronic message, along with any information, advice, and
opinions it contains, are mine alone and are not representative of my
employer. All information is provided in "GOOD FAITH" and on an "AS IS"
basis only. I provide no presentations or warranties, express or
implied, including implied warranties of fitness for a particular
purpose, merchantability, title, and noninfringement. I strongly advise
you to extensively test any changes, workarounds, or techniques
described herein on a development system prior to implementation in a
production environment, and you are hereby notified that I bear no
responsibility whatsoever for any loss, harm, or otherwise negative
outcomes resulting from your actions, whether or not said actions were
a result of this electronic message, directly or indirectly.

 

[andy.novak]

I'm sorry, you're right, I meant "enabling" the auto-provisioning.

The workspaces don't take up much room, so I wouldn't really worry
about them being created and not used. If it's an issue, you can always
delete them later.

--
Stephen Sanderlin
Owner/Founder - EPMFAQhttp://www.epmfaq.com/http://forums.epmfaq.com/

EPM Solutions Architect / Principal Consultant - BT Professional
Serviceshttp://bt.ins.com/

This electronic message, along with any information, advice, and
opinions it contains, are mine alone and are not representative of my
employer. All information is provided in "GOOD FAITH" and on an "AS IS"
basis only. I provide no presentations or warranties, express or
implied, including implied warranties of fitness for a particular
purpose, merchantability, title, and noninfringement. I strongly advise
you to extensively test any changes, workarounds, or techniques
described herein on a development system prior to implementation in a
production environment, and you are hereby notified that I bear no
responsibility whatsoever for any loss, harm, or otherwise negative
outcomes resulting from your actions, whether or not said actions were
a result of this electronic message, directly or indirectly.

How much space do you think they take up?

 

[Stephen Sanderlin]

I can't say for sure because it depends on your template, but I think
that less than a meg or so in the Content DB for an empty workspace is
reasonable.

--
Stephen Sanderlin
Owner/Founder - EPMFAQ
http://www.epmfaq.com/
http://forums.epmfaq.com/

EPM Solutions Architect / Principal Consultant - BT Professional
Services
http://bt.ins.com/

This electronic message, along with any information, advice, and
opinions it contains, are mine alone and are not representative of my
employer. All information is provided in "GOOD FAITH" and on an "AS IS"
basis only. I provide no presentations or warranties, express or
implied, including implied warranties of fitness for a particular
purpose, merchantability, title, and noninfringement. I strongly advise
you to extensively test any changes, workarounds, or techniques
described herein on a development system prior to implementation in a
production environment, and you are hereby notified that I bear no
responsibility whatsoever for any loss, harm, or otherwise negative
outcomes resulting from your actions, whether or not said actions were
a result of this electronic message, directly or indirectly.