Can anyone direct me to documentation on publishing a 2008 created ad in to office for distribution via CD?

I am using VS 2008, VSTO, a third party obfuscator, and a signing certificate.

Everything I have read is related to publishing applications as opposed to ad ins, and they all speak of doing it on local machines I have control over.  I want to publish to CD for distribution to unknown users/machines.

Hello AustinMyers,

Welcome to MSDN forums!

I think you are going to deploy your VSTO solution by ClickOnce, right?

To deploy your solution via CD the most parts of the process are the same as the standard ClickOnce deployment, the only thing we need to notice is leave the Install Location blank and set Updates to Never, you could refer to this link for detailed steps:
http://msdn.microsoft.com/en-us/library/bb386179.aspx#Deploying

And as you mentioned in your post, you may need to deploy some additional files during your deployment, to achieve this goal please refer to this document for detailed steps:
http://msdn.microsoft.com/en-us/library/cc837214.aspx

If you have any further questions please feel free to ask me.

Thanks.
 

Tim Li

MSDN Subscriber Support in Forum

If you have any feedback on our support, please contact EMAIL GONE

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Hi,

 

I am writing to check the status of the issue on your side. Could you please let me know if the suggestion works for you or not? If you have any questions or concerns, please feel free to let me know. I will be more than happy to be of assistance.

 

Tim Li

MSDN Subscriber Support in Forum

If you have any feedback on our support, please contact EMAIL GONE

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Hi Tim,

I did what ever you said and it works for my current user, but What should I do if I like to do it for all users who are using same server ( many users on same machine)?
I googled it and I found some stuff but they don't work , I just wonder you may know the solution.

Thanks,
Farzad

Tim,

Sorry I tokk so long gettign back to you but I was called out of town.  I will go through the information (links) and let you know how it turns out in the morning.

Thanks,

Austin

Tim,

I tried to read the links and like a lot of MS "documentation" it links to other links, that link to more links that link to...  Well, you get the idea.  Perhaps it is just me buy I find it all very confusing and still do not have a clear step by step idea of what I need to do.  Is there any document that actually walks through publishing an app level ad in that is laid out in a single document I could follow?

Hey Austin,

As your request, please follow this link in which included a video on this topic, and hope this will make you more clear.
http://msdn.microsoft.com/en-us/library/bb386095.aspx

Besides, in the very top of this forum there's a thread convers all aspects of deploy Office solutions, you could refer to :
Deploying Office Solutions to End User Computers

Thanks.
 

Tim Li

MSDN Subscriber Support in Forum

If you have any feedback on our support, please contact EMAIL GONE

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Hi Farzad,

Welcome to MSDN forums!

As I mentioned above, you could also find the resource you need in Deploying Office Solutions to End User Computers.

To be clear, the link you need is:
 To deploy to all users for Office 2007 and ClickOnce, see http://blogs.msdn.com/mshneer/archive/2008/04/24/deploying-your-vsto-add-in-to-all-users-part-iii.aspx demonstrates how.

If you have any further questions, please start a new thread, therefore, more members will be involved, and things will get done more quickly.

Thanks.

Tim Li

MSDN Subscriber Support in Forum

If you have any feedback on our support, please contact EMAIL GONE

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Thanks  Tim,

I tried the below link:
To deploy to all users for Office 2007 and ClickOnce, see http://blogs.msdn.com/mshneer/archive/2008/04/24/deploying-your-vsto-add-in-to-all-users-part-iii.aspx demonstrates how.

But it didn't work. by the way I'm going to take your advise and start new thread.

Thanks again,
Farzad

Hey Tim,

Not trying to be dense here but I read everything and watched the video but there wasn't really anyting that discussed using an obfuscator or about code signing.  That is where I seem to be having a problem.

Hey Austin,

As your request, please follow this link in which included a video on this topic, and hope this will make you more clear.
http://msdn.microsoft.com/en-us/library/bb386095.aspx

Besides, in the very top of this forum there's a thread convers all aspects of deploy Office solutions, you could refer to :
Deploying Office Solutions to End User Computers

Thanks.
 

Tim Li

MSDN Subscriber Support in Forum

If you have any feedback on our support, please contact EMAIL GONE

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Tim,

I am more confused than ever.  Am I to understand I need to write multiple additional projects for "FullTrust", "Gaspoll", and some sort of project to set security up?  Good gawd someone tell me that is not needed to put out a simple ad in!!!!!!!!!  I will spend more time farting around with this garbage than writing the ad in.

Am I to understand I need to write multiple additional projects for "FullTrust", "Gaspoll", and some sort of project to set security up? 

No, this action is needed in VSTO 2005 SE, not VSTO 3.0&ClickOnce.

If we create a blank add-in project, and check the solution explorer you'll find there's no .pfx file exist in the project at that moment, this means the project has not been signed by a certificate, next you press F5 to run this project, you'll find a .pfx file is generated to sign the project, the generated certificate is temporary and for development only you could replace it to your own certificate in Project property page.

Can you now perform a ClickOnce deployment without an obfuscator?

I suggest you first have a try, follow the document/Video to perform a ClickOnce deployment step by step, and then make some change to fit your own requirement.

Thanks.

Tim Li

MSDN Subscriber Support in Forum

If you have any feedback on our support, please contact EMAIL GONE

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Am I to understand I need to write multiple additional projects for "FullTrust", "Gaspoll", and some sort of project to set security up? 

No, this action is needed in VSTO 2005 SE, not VSTO 3.0&ClickOnce.

If we create a blank add-in project, and check the solution explorer you'll find there's no .pfx file exist in the project at that moment, this means the project has not been signed by a certificate, next you press F5 to run this project, you'll find a .pfx file is generated to sign the project, the generated certificate is temporary and for development only you could replace it to your own certificate in Project property page.

Can you now perform a ClickOnce deployment without an obfuscator?

I suggest you first have a try, follow the document/Video to perform a ClickOnce deployment step by step, and then make some change to fit your own requirement.

Thanks.

Tim Li

MSDN Subscriber Support in Forum

If you have any feedback on our support, please contact EMAIL GONE

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Tim,

Please forgive me if I sound irritated.  Its only because I am.  :-(   This is over the top and a complete watse of coding time.  Publishing an ad in after weeks of work and coding should be a simple mouse click and its ANYTHING but that.  When I think that I paid good money for VS (05 and 08) and this is what I get for it the entire idea makes me feel ill.  Good grief, it was easier to build/complie and publish machine code than this stuff is.

I've gotten it to publish (sort of) and obfucicated the components, now I have to try and figure out what to do to make a setup.exe for it.  I foolishly thought that was what publish did but I was wrong on that too.  Guess I have to go waste another three of four days trying to understand the Microsoft stupidity woven into all this.

Hi,

Deployment is a pain of VSTO deployment, plese be patient, you mentioned you've gotten the solution to publish I'm really glad to hear that.

Here's a Video of deploy Office Solution via Windows Installer, please refer to :
http://msdn.microsoft.com/en-us/vcsharp/cc998443.aspx

And this one for document-level solutions:
http://msdn.microsoft.com/en-us/vcsharp/cc998641.aspx

Hope this helps you.

If you have any further questions, please feel free to follow up.

Thanks.

Tim Li

MSDN Subscriber Support in Forum

If you have any feedback on our support, please contact EMAIL GONE

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Hi Austin,

I am writing to check the status of the issue on your side. Could you please let me know if the suggestion works for you or not? If you have any questions or concerns, please feel free to let me know. I will be more than happy to be of assistance.

Tim Li

MSDN Subscriber Support in Forum

If you have any feedback on our support, please contact msdnmg@microsoft.com

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.