- This topic is empty.
- 04/24/2012 at 2:10 am #6339
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.
- 04/24/2012 at 2:19 am #6340
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.
- 04/24/2012 at 5:02 am #6341
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.
- 04/24/2012 at 11:37 am #5278
That can be done using PowerShell.
- 04/25/2012 at 5:26 am #6342
You need to deploy the solution on the newly created site collection. This link provides all the info you need to do that.
- 04/25/2012 at 9:07 am #6343
Do you have any examples of deploying a solution using just the object model, not Powershell.
- 04/25/2012 at 9:24 am #6344
I found some util links searching using google.
There are lots of related article on the internet.
- 04/25/2012 at 9:42 am #6345
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.
- 04/25/2012 at 12:28 pm #6346
If you find my answers helpful please mark them so other people can benefit of them.Thanks.
- 04/27/2012 at 4:17 am #6347
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.
- 04/30/2012 at 12:22 pm #4341
(posting on behalf of another)
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.
How do I configure the Quest Web parts for Sharepoint 2010 do that?
QWP version 5.6
- 04/30/2012 at 12:22 pm #6348
I'm glad to hear that it works now.
Richard please mark this question as answered.
You must be logged in to reply to this topic.