tag:blogger.com,1999:blog-2002996596449613715.post7040583903243877686..comments2008-05-09T04:41:24.820-04:00Comments on Mikhail Dikov: SharePoint Resources, Types, Use and Deployment (U...Mikhail Dikovhttp://www.blogger.com/profile/13980715720338179589noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-2002996596449613715.post-1416516302880869192008-05-09T04:41:00.000-04:002008-05-09T04:41:00.000-04:002008-05-09T04:41:00.000-04:00Dear MikhailI am trying to follow your example usi...Dear MikhailI am trying to follow your example using feature stapling.My stapling feature is scoped as farm, and my feature for copying the runtime resources is scoped webapplication.However the feature for copying the runtime resources does not get activated, when i create a new the site associated with it in my stapling feature.Can you give me a hint?Kind reagrdsMorten AndreasenAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-2002996596449613715.post-90058587891247534432008-01-22T08:31:00.000-05:002008-01-22T08:31:00.000-05:002008-01-22T08:31:00.000-05:00Hi Mikhail,it's me again, Matthias.We observed tha...Hi Mikhail,it's me again, Matthias.We observed that the solution you proposed using Timer job definitions works well under MOSS RTM, but doesn't work under MOSS SP1 anymore. We are not sure what the cause is. Have you tested the Timer Job Definition Solution on SP1 yet?On the other hand, you say that when you use a web or site scoped feature that is stapled to a site definition, the feature eventAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-2002996596449613715.post-62122290329195231592008-01-09T22:38:00.000-05:002008-01-09T22:38:00.000-05:002008-01-09T22:38:00.000-05:00The key to make this work is to use Feature Stapli...The key to make this work is to use Feature Stapling! Otherwise you'll get exactly the results you are observing.In this post I give an alternative solution, which many people found better:http://www.mikhaildikov.com/2007/03/sharepoint-resources-types-use-and_2163.html MikhailMikhail Dikovhttp://www.blogger.com/profile/13980715720338179589noreply@blogger.comtag:blogger.com,1999:blog-2002996596449613715.post-80113335979602857592007-12-20T11:11:00.000-05:002007-12-20T11:11:00.000-05:002007-12-20T11:11:00.000-05:00Interesting that it worked for you.In one of my ex...Interesting that it worked for you.In one of my experiments, it didn't matter which server the code was activated on, it still only copied my solution's ascx files (it was similar to this resource issue) to the webroot of the server the solution was INSTALLED/DEPLOYED on. I remember how was strange it was to see an activation on server B cause files to appear on server A.AAron nAAshttp://www.blogger.com/profile/14454730466252170198noreply@blogger.comtag:blogger.com,1999:blog-2002996596449613715.post-4514952794393374912007-12-19T07:39:00.000-05:002007-12-19T07:39:00.000-05:002007-12-19T07:39:00.000-05:00i had the same experience. I had to deactivate / a...i had the same experience. I had to deactivate / activate on each server to copy the resources over to each node.Roel Hanshttp://www.blogger.com/profile/03287243977914023062noreply@blogger.comtag:blogger.com,1999:blog-2002996596449613715.post-52797961363890458902007-12-01T10:54:00.000-05:002007-12-01T10:54:00.000-05:002007-12-01T10:54:00.000-05:00Does that work across all servers in a farm?I was ...Does that work across all servers in a farm?I was copying files during FeatureActivation, and found that it only did the activation copy on the server the feature was installed on.AAron nAAshttp://www.blogger.com/profile/14454730466252170198noreply@blogger.com