[Anonymous]

Hello ,

Can you provide the Powershell commands for this.   I could also do this using the object model if you have some commands for this.   Ideally though, I would be able to set up the environment to automatically deploy the web parts as part of the new site creation.

Thanks,

Will Shea

[Anonymous]

Hi Will,

  The idea here is to create the site collection then activate Quest Web Parts feature using PS commands.

Check this link http://technet.microsoft.com/en-us/library/cc263094.aspx

Check this link to activate a feature.

http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2011/01/04/activating-and-deactivating-features-with-powershell-in-sharepoint-2010.aspx

[Anonymous]

Actually, I have created a site creation workflow that provisions the site collection and activates features on that site collection.  That all works fine.  My problem is that the Quest Web Parts are not deployed to the newly created site collection, so I have no Quest Web Parts feature to activate. 

[Anonymous]

Hi Richard,

  That can be done using PowerShell.

[Anonymous]

Hi Will,

You need to deploy the solution on the newly created site collection. This link provides all the info you need to do that.

http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2009/12/02/adding-and-deploying-solutions-with-powershell-in-sharepoint-2010.aspx

[Anonymous]

Thanks ,

Do you have any examples of deploying a solution using just the object model, not Powershell.

Will

[Anonymous]

Hi Will,

  I found some util links searching using google.

http://msdn.microsoft.com/en-us/library/bb530301(v=office.12).aspx

http://msdn.microsoft.com/en-us/library/ee256698.aspx

There are lots of related article on the internet.

[Anonymous]

Hello ,

I must have put something weird in my google search because I did not get these references.   Thanks for your help,   I'll give these a try.

Will

[Anonymous]

You're welcome.

PS

If you find my answers helpful please mark them so other people can benefit of them.Thanks.

[Anonymous]

Thanks,  it turns out that my issues were being caused by a mismatch of versions.  I was using a template that was created with Quest Web Parts 5.6 while I was trying to deploy the template to a environment that was using Quest Web Parts 5.5.   In 5.5 Quest web parts are scoped at the Web Level, in 5.6 at the Site level (which is much better).  Also the associated guid for the QWP feature is different.   Once I upgraded, my template deployed fine using my auto site creation workflow.   Thanks for all your help.

[Anonymous]

Hello Community,

(posting on behalf of another)

Scenario:

When I create a new site collection in Sharepoint 2010 I want the Quest Web Parts to be deployed and activated in that new site collection automatically.  

Question:

How do I configure the Quest Web parts for Sharepoint 2010 do that?

QWP version 5.6

Thank you,

[Anonymous]

Hi Will,

  I'm glad to hear that it works now.

PS

Richard please mark this question as answered.

[Author]

Posts