This link has been bookmarked by 44 people and liked by 2 people. It was first bookmarked on 01 Oct 2007, by mj mein.
-
23 Aug 13
-
29 Jul 12
-
06 Mar 12
-
16 Sep 10
-
20 Jul 10
-
07 Mar 10
-
25 Sep 09
tresingIncludes sample code download which deploys a feature with a site page.
sharepoint development .net programming asp.net deployment moss howto tutorial sharepoint2007
-
03 Jun 09
-
27 Apr 09
-
28 Feb 09
-
09 Dec 08
-
08 Aug 08
-
08 Jul 08
-
02 Jul 08
-
02 Jun 08
-
12 May 08
-
07 Apr 08
-
02 Apr 08
-
22 Jan 08
-
19 Dec 07
-
04 Dec 07
-
22 Oct 07
-
01 Oct 07
-
-
I like to create all my Features that contain some sort of compiled code using a Class Library project template. Then I setup the project to be signed to generate a strong named assembly and create the folders necessary for a Feature. Next, add a reference to System.Web. Nope... no reference to Microsoft.SharePoint is necessary! See... SharePoint development IS ASP.NET 2.0 development at the core! Last setup bit is to add a custom MSBuild targets file and stuff necessary to automatically build and package the Feature into a WSS Solution Package (*.WSP) using the technique I wrote about here.
-
- This page implements two ContentPlaceHolders defined in SharePoint master pages.
-
The meta:progid attribute on the Page directive is necessary if the page will ever be opened in SharePoint Designer.
-
Notice the markup in Figure 7 is adding a safe control entry to the web.config for the destination Web application. This is because SharePoint must be aware that the types within the assembly we are deploying are safe and ok to execute. At this point, here's what my Visual Studio project looks like:
-
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.