.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
Sharon Maxwell
Post New Web Links

Deploying the feature to a site (not globally) using WSPBuilder

Posted By:      Posted Date: October 13, 2010    Points: 0   Category :SharePoint
 

Hi,

    I have developed an event handler for the task list as a feature, which overrides the ItemAdding,ItemDeleting and ItemUpdating event.
 I have even deployed the same on the server using the  WSPBuilder.

In the process of using the WSPBuilders, on creating the deployment folder I got a folder called "deploy"  in the "bin" folder.The deploy folder contains a folder, which again contains the deployment files like deploywithstsadm.bat, deploywithstsadmnocontenturls.bat, deploywithwspbuilder.bat  ......

For my project i used the deploywithstsadmnocontenturls.bat file, and deployed it. It gets deployed sucessfully.

The problem here is that the feature is getting deployed "Globally", how can i deploy it to a particular site like "ww.testsharepoint.com". ??????

 

With regards


Biju Software Engineer,MCP


View Complete Post


More Related Resource Links

Why do the aks master pages not get applied if the feature is not activated on the top site collecti

  
Hi

I installed AKS 2.0 and activated AKS feature. The problem I found was the aks master pages do not get applied if the feature is not activated on the top site collection. why is so?

example: If i activate the feature on http://<servername>/sites/<sitename> and apply the master page, I dont see any changes.

              But if i activate the same aks feature on http://<servername/ then everything started working on all sites.

              The reason i found is the CSS reference in the aks master pages.

              It reference should be given as follows:

                 for http://<servername>/sites/<sitename> ->  <link rel="stylesheet" type="text/css" href="../../Style%20Library/AKS/Aks_Band_Blueband.css"/>

                 for http://<servername>/ -><link rel="stylesheet" type="text/css" href="/Style%20Library/AKS/Aks_Band_Blueband.css"/>

So my question is, am i missing anything? am i supposed to activate the AKS feature on top level site collection at any cost? if yes, why is so? 

And after applying aks master pages, i see differnece in font sizes. Why the font size is getting changed?

Also

Why feature with event receiver doesn't activate properly after site provisioning?

  

Hi!

I have defined feature with event receivers for my document library and for users List .

I try to activate my feature in onet.xml in section <WebFeatures>. After provisioning a new site from onet.xml  all work fine and my feature is shown as activated, but event receivers doesn't fire. It fires only after reactivating my feature (deactivate, then activate it again). But I need my feature works immediately after site provisioning without deactivating and activating it again. Who knows how to solve this problem?

part of ONET.xml

 

      <WebFeatures>

        <Feature ID="00BFEA71-4EA5-48D4-A4AD-7EA5C011ABE5"/>

        <!-- TeamCollab Feature -->

        <Feature ID="F41CC668-37E5-4743-B4A8-74D1DB3FD8A4"/>

        <!-- MobilityRedirect -->

        <!--My EventReceivers Feature-->

        <Feature ID ="41178843-A6A4-47c7-9EF9-B8A432E02B88"></Feature>

      </WebFeatures>

 


Feature.xml

<

SOLUTION: Renaming the Title list column globally across the site collection

  
So, you screwed up like I did, and modified the Title display name of the Item base content type and it has renamed ows_Title across every list in your site collection? Here's how you fix it: //WARNING //If you have come this far, be aware that this tool is a blunt axe. With it, you can cause //all sorts of mayhem and chaos in your site collection. So, to use this, you must be desperate. //or possibly dumb. Apparently, I'm just as dumb as you, because I did it. This is why I wrote //this stupid thing, so stupid people like us can go right on being stupid. //Your choice of weapon in this battle amuses me. Shall we begin? using System; using System.Collections.Generic; using System.Text; using Microsoft.SharePoint;   namespace RenameField {     class Program     {         static void Main(string[] args)         {             if (args.Length < 3)             {                 Console.WriteLine("Usage: RenameField <url-to-sitecollection> <internal-field-name> <new-fieldtitle>");               &n

Deploying custom 2007 site definition to 2010

  
For a customer I am upgrading their SharePoint 2007 enviroment to SharePoint 2010. After a succesfull upgrade I am stuck with one last annoying problem: when creating a publishing site collection using a custom definition the provisioning of the site definition  fails. Interesting about this is that the provisioning works from the central admin UI, but this customer has an custom webpart for creating site collections in a web application outside of Central administration. The simplified code for this is: public static bool Create(SPWebApplication webApp, string Url, string siteTitle, string siteDescription, uint lcid, string siteTemplate, string ownerLogin, string ownerName, string ownerEmail)         { SPSite site = null; try { SPSite newSiteCollection = webApp.Sites.Add(Url, siteTitle, siteDescription, lcid, siteTemplate, ownerLogin, ownerName, ownerEmail); newSiteCollection.Close(); newSiteCollection.Dispose(); site = GetRootSite(webApp); bool r = (site != null) ? true : false; return r; } catch { return false; } finally { if (site != null) site.Dispose(); }         } The exception is thrown when webApp.Sites.Add() is executed. The user we are logged in as, as wel the appID, are Farm Admin's. The ULS shows this exception: Exception thrown while fetching field by internal name 'Wiki_x0020_Page_x0020

feature stapling done against site definition breaks when saving site as a template?

  
Hi, we have a bunch of feature stapling done against some of our site definitions on a solution we are working on. This feature staple has a bunch of feature dependancies which all work in a variety of ways. One of these dependancies then uses a feature receiver class to do some post provisioning setting up of web part connections and the like. This all works very well when creating a new site from a site definition etc etc. The problem arises when a user opts to provision a site in this way, and then uses the 'save as template' function within sharepoint. (BTW this is WSS 3.0 / MOSS). The site template saves correctly, but now the feature receiver never runs. I'm assuming this is because the associated feature staple doesnt run either? I've looked around and seen some reference to feature stapling not working against templates. Is this true? 

Deploying features to a specific sub-site

  
Hi all, I have a Root Site collection, and it has various sub sites, I have a couple of lists and content types that are specific to some sub sites, and the client doesn't want these lists and content types viewable across the company so it makes sense that these are deployed to their respective sub sites only so that they are not available at the root level. I know if you go through the Site Settings for the sub sites, you can create content types and lists that are only available in that site, but I am battling to deploy these content type & lists to their specific sub-sites though Visual Studio 2010, does anyone know how to do this?

Retract custom master page feature and all site pages stop working

  
There is a requirement to apply custom branding on personal sites in a SP 2010 project. For this I have created a feature which uploads and applies the custom master page on creation of any new personal sites.   I have stapled this feature (using feature stapling concept) to the “SPSPERS” (personal site) site definition. The custom master page is displayed on the creation of new personal sites. On feature deactivation, I am looping through all the personal sites (as the feature is deployed on a team site) and pointing the master URL back to v4.master. But when I retract the solution and browse to the personal site, I am getting a “404 File not found” error.  But am able to view the settings page by typing the URL.   I activated the publishing features and looked at the master page applied to the personal site. It was pointing to v4.master.   Any help on this is appreciated. Regards, Neha

Retract custom master page feature and all site pages stop working

  
I have stapled this feature (using feature stapling concept) to the “SPSPERS” (personal site) site definition. The custom master page is displayed on the creation of new personal sites. On feature deactivation, I am looping through all the personal sites (as the feature is deployed on the root site) and pointing the master URL back to v4.master. But when I retract the solution and browse to the personal site, I am getting a “404 File not found” error.  But am able to view the settings page by typing the URL.   I activated the publishing features and looked at the master page applied to the personal site. It was pointing to v4.master. Any help on this is appreciated. Regards, Neha    

Deploying a Feature Stapler for a specific Web App

  
I'm trying to write a very simple feature stapler scoped to the web app level. I can write it. I can deploy it as a farm solution. But, I can't get it to deploy to the web app level. If I run install-SPSolution with the -WebApplication parameter, I get the error "This solution contains no resources scoped for a Web Application and cannot be deployed to a particular web application." Here's the feature.xml - which says it's scoped to the webapplication: <?xml version="1.0" encoding="utf-8"?> <Feature xmlns="http://schemas.microsoft.com/sharepoint/" Id="5603ccd0-4d95-4250-890f-318d433d3a9a" Scope="WebApplication" Title="cets_ws_master_stapler"> <ElementManifests> <ElementManifest Location="stapler\Elements.xml" /> </ElementManifests> </Feature> What am I doing wrong? The feature it should staple is only relevant to a particular web app, so I really _can't_ let it deploy to the whole farm.

problem deploying report model to wss3 site

  
hi, im having trouble deploying my report model. when i click on deploy i have to enter a user name and password (i asume that it is the username and password i use to enter my wss 3 site) after that it begin to deploy then i get these 2 errors: Error 1 The required field UserName is missing from the input structure. c:\documents and settings\administrator\my documents\visual studio 2005\projects\essreportproject\essreportproject\ESSP.ds 0 0  Error 2 The path of the item '/Data Sources/ESSP' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. c:\documents and settings\administrator\my documents\visual studio 2005\projects\essreportproject\essreportproject\ESSP.smdl 0 0  when i go to my page in wss3 i can see the datasource and model directory, but i cant use them can someone help me with this and explain it for me.  

Office Sharepoint Server Publishing Infrastructure is missing in site collection feature SharePoint

  
I was trying to activate the Office Sharepoint Server Publishing Infrastructure feature in the site collection features but the feature is simply not there. Is this option not available in SharePoint Foundation 2010?

content Type at site collection level using feature.

  
I m planning to create a feature to install the content type and site colomun at site collection level. Now my doubt is? 1. what will happen when i de activate a feature with documents already there? 2. what will happen when i de activate a feature without documents? What are points i need to take care? 

Running code after site definition site creation in a event receiver or feature receiver

  
Hi guys I've got a site definition which is pretty much based on STS.This is it's own sharepoint project. Let's call this project SiteDefProj. Next in another SharePoint project (same solution though). Let's call this CustomListProject. In this project I've got a feature which provisions a bunch of lists based on custom content types - this feature is a site scoped. Let's call this feature: CustomListInstances. I have added a feature receiver to this feature to execute some custom code on the lists themselves (under feature activated) In my ONET.XML (part of the SiteDefProj) I have CustomListInstances feature ID as part of my <sitefeatures>. When I do a create site I can actually step through the code and see it actually being executed but after the site is created the list instances are created but it's like the code never run or did anything. The weird part is that stepping through the code while creating a site collection using my SiteDefProj the code runs great with no errors. All lists are there and the code runs smooth. If I manually create a STS site and activate my feature everything works and the code does actually run and the effects are visible after the feature is created. Again I can actually step through it in debug. My suspicion is that there's some sort of a race condition in the CREATE SITE functionality where maybe the web or site collection hol

SharePoint how does it know to use a feature default.aspx deployed instead of site definition defaul

  
I have created a feature which deploys a custom default.aspx page. The deployed file goes to the template\features{featureName} directory. How does SharePoint know to use this default.aspx page instead of the one that is located in SiteTemplates{Site Def name} directory?dave

Site Collection Reporting Feature?

  
Hi I'm wondering if anyone knows or has seen Microsoft documentation on what activating the "Reporting" feature within the Site Collection Features page will do?  The reason I ask is I thought that activating it at the site collection level was required in order to use site collection usage and site usage reports.  That's what MS's site says here:  http://technet.microsoft.com/en-us/library/cc262541(office.12).aspx  However I have one farm where those usage reports are available, but this site collection feature has not been activated.  Usage logging was enabled through CA for the farm and usage reporting was enabled through CA for the SSP). This is a MOSS 2007 environment.  

Feature with wsp for creating specific groups on any site creation

  
hi, i need to create a sharepoint feature for wss 3.0 with .wsp (wsp for easy deployment) which do folowing funtionality: Ability to run some custom code for creating specific custom groups on every site creation. Feature needs to be activated when deployed so when user create new site it creates groups based on our custom code( i have custom code for creating gorups just need to know how to attached it to feature which works on every site creation event) Any workable example is very helpful for me because i am very confuse and already did reasearch on that. i guess feature stapling is not the solution in my case. Thanks in advanced shaheen

programatically add link in site settings page through feature

  

Hi folks,

          Im newbie in SharePoint, we have created an Application  Page for Managing the WebPart Permissions. We need to add one link called "ManageWebParts"  in the site settings Page so that  the admin can go the site settings and  Navigate to the ManageWebpart.aspx Page using this link. How we can  add the link  through programatically using feature???

 

Your thoughts??

 

 

Thanks & regards

Pulikkan


Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend