Navigation. Taxonomy. Provider. Creating Custom Service Applications | Services Architecture | SharePoint 2010 Developer Training Course | Learn | Channel 9. Installing SharePoint Foundation 2010 on Windows 7 « Lasse Wikmark. Home > DevNotes, English, SharePoint, TechNotes > Installing SharePoint Foundation 2010 on Windows 7 Please note that Microsoft does not support this configuration for production environments. Windows 7 installations should only be used for development, testing and demo purposes! Prerequisites The following components and additions has to be installed on the computer running Windows 7 64-bit edition: Installation procedure Use the following procedure to install SharePoint Foundation: Make sure all prerequisites are met and no critical error is present in the event logs.Download SharePoint Foundation from Microsoft’s web site. Editing the config.xml file As described in step 4 in the installation procedure above, the config.xml file has to be edited to allow installation on Windows 7.
The entire config.xml file should look similar to this: IIS Features and Components The follow screen shots shows required IIS components as described in the prerequisites section: N’Joy! Like this: Like Loading... SPSF SharePoint Software Factory. Imtech - Release: Imtech StsAdm Commands v1.0.0.0. How to reuse your list definition in a SharePoint feature. In my case I often create SharePoint sites and lists in a development environment or on a demo server, just to set up and verify the architecture and design.
From that point I often have to sit down and start writing the actual feature, which involves some heavy Xml coding most of the times – now I have found a shortcut that will save me an awful amount of time. Let’s say that you have created a list in your demo environment, with columns, views and everything. This list is then the target of your feature you are about to develop. Creating the manifests, list templates and instances are pretty easy, but creating the schema can be troublesome and/or time consuming. Today I found a sweet little custom STSADM command called OCDExportList . This custom command exports the list schema from a list in a SharePoint site to an .xml file.
Similar functionality can be found in other SharePoint solution generators , but I prefer using STSDEV and for this situation the custom command is great! . Form: Camlex.NET. Camlex.NET 2.0 for Sharepoint released. I’m glad to announce that next version of Camlex.NET project is released. About 2 months ago I introduced release of Camlex.NET on codeplex. During this time we received feedback from community and took into account applied developers needs when worked over 2.0 version. Yesterday we published Camlex.NET 2.0. In this post I will describe new features and differences from previous version. 1. Dynamic filtering conditions This is the most excited feature added in 2.0 version. 1: public interface IQuery 3: IQuery Where(Expression<Func<SPListItem, bool>> expr); 4: IQuery WhereAll(IEnumerable<Expression<Func<SPListItem, bool>>> expressions); 5: IQuery WhereAny(IEnumerable<Expression<Func<SPListItem, bool>>> expressions); Method Where exists from 1.0 version.
So what these methods do? Lets see examples. 1: <Where> 2: <Or> 3: <Or> 4: <Contains> 5: <FieldRef Name="Title" /> 6: <Value Type="Text">hello</Value> 7: </Contains> 8: <Contains> 9: <FieldRef Name="Title" /> 10: <Value Type="Text">greeting</Value> 2. How to: Develop SharePoint solutions using VSeWSS and move into WSPBuilder. Hi all, The development and deploying SharePoint solutions, I always use WSPBuilder. WSPBuilder is BEST TOOL for building and deploying WSP packages. I have dealt with both the tools and I preferred of following reasons: 1) Its highly stable and have higher performance. 2) Provides default templates such as Blank feature, Feature with eceiver, Event Handler, Sequential and state based workflows, Web part features etc. 3) Mimics 12 Hive structure. 1) List instance, List Templates, Field Controls, List Definition from content type are NOT defined although they can defined with some efforts. 2) Can not reverse engineer the objects such as lists, templates, content types etc. 1) Ability to get intellisense within all SharePoint framework files 2) Ability for a range of code snippets when within SharePoint framework files such as list instances, list templates, field controls etc. 3) Ability to reverse engineer objects in a SharePoint Site instance to Feature using SharePoint Solutions Generator.
SPSource: Reverse engineering tool for SharePoint. The first thing needed is to set up two site collections - one for design, and one for development. The design site is where changes are made via SPD and the UI, and the dev site is where the WSP is deployed. design site dev site To illustrate a simple example, I'll create a new publishing layout page in the design site based on the Welcome Page content type. The new page has now been added to the master page gallery as seen in SPD. I'll add some markup, web part zones, and content placeholders to the page, and save it.
When I create a page in the SharePoint UI, the new page template is now available. As shown in the UI: In my Visual Studio project, which is based on STSDev, I'll add a new Feature (STSDev, WSP Builder, and WSPProjectTemplate all have been tested and work) Now I'll add a new file named PublishingPages.spsource to the feature. This file is nothing more than a stripped-down version of the file provisioning module that was needed before. Creating a SharePoint Solution Package (.wsp) in 5 steps. For those who are new to the SharePoint solutions and features I would recommend to try the SharePoint Solutions Generator, which is a part of the Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions.
It is a windows stand-alone application that converts your existing SharePoint web site into the solution package and creates a Visual Studio project for you to use. Nice isn’t it? What I personally don’t like in the automatic tools is that they always hide some part of the job they are doing behind the scenes. In this scenario you can’t really control and sometimes understand of that is going on. So, today I would like to blog about of how to manually create the SharePoint feature containing the list, how pack it into the solution package and finally deploy it to the production server. Everything will be done without any use of Visual Studio or other tools (only Notepad++). So, let’s start! Step 1. First, create the folder structure for the solution.
Step 2. Feature.xml. Long operations on a SharePoint 2007 page - Jevgeni Borozna's blog. Sometimes you would like to accomplish some task on a Page which takes more time than is set as “timeout” and you are seeing Request timed out in your browser. This type of error is not so informative for end-user and is not beautiful for a complete solution. SharePoint default solutions solving this kind of problems with “Operation in Progress” page: SharePoint API proposes SPLongOperation named class to solve this problem the same way in your custom solutions.
MSDN documentation: This class provides you two main methods: Begin() and End(); and to properties: LeadingHTML and TrailingHTML, which can be set to show custom text. Between calling Begin and End methods you can complete long operations. // "this" is a Page using (SPLongOperation longOperation = new SPLongOperation(this)) longOperation.LeadingHTML = "Your operation is in progress longOperation.TrailingHTML = "Your operation is currently.
SmartTools for SharePoint. SharePoint Developer Blog. Nearly every SharePoint project that involves some type of content management, whether it be using document libraries, custom lists, or published web content, we generally find ourselves needing to create one or more content types to deliver the designed solution to a client. Up until this point, most often we have taken the most basic approach to creating content types in the past – performing the task through the built-in SharePoint UI. While this methodology works, it can almost be thought of as the brute-force approach. I make this comparison because while the built-in UI offers a working method for creating content types, and the underlying site columns that they are made up of, it lacks in providing any means to take those site columns and content types and move them elsewhere, or apply them to multiple site collections.
Another approach to building content types and site columns to leverage the built-in Features framework within SharePoint 2007. MOSS Feature Generator. Bend Sharepoint without bending the rules : Custom Site Definition for collaboration portal template SharePoint 2007 !! Wow MOSS !! Hey I knew how to create custom site definition and created custom site definitions for a top level team site and a custom site definitions for Custom Serach Centre and the documents centre. Hurray !!! But how can i integrate all these three definitions into a single portal template so that one can choose the template and create a top level site along with the custom search centre and the documents centre as a sub site. Oh yeah !! This feature has been given as collaboration portal template in the OOb sharepoint site definition. This blog post will walk you through creating custom site definition and creating custom site definition for collaboration portal template.
What is Site Definition? A set of predefined components needs to be included when a site was created in the SharePoint server. OOB Site Definition: By default SharePoint comes with several OOB site definitions which you can select to create your site. How to create custom site definition: 1. 2. 3. 4. 5. 1. 2. 3. 1. 2. 3. 4. 5. Plan browser support (Office SharePoint Server) Published: July 16, 2012 Summary: Learn about how SharePoint 2013 supports Internet Explorer, Google Chrome, Mozilla Firefox, and Apple Safari. Applies to: SharePoint Foundation 2013 | SharePoint Server 2013 Standard | SharePoint Server 2013 Enterprise SharePoint 2013 supports several commonly used web browsers, such as Internet Explorer, Google Chrome, Mozilla Firefox, and Apple Safari.
As you plan your deployment of SharePoint 2013, we recommend that you review the browsers used in your organization to guarantee optimal performance with SharePoint 2013. In this article: Browser support is an important part of your SharePoint 2013 implementation. Browser support matrix Browser details Browser support matrix The following table summarizes the support levels of typically used web browsers. Browser details Review the details of the web browser that you have or plan to use in your organization to make sure that the web browser works with SharePoint 2013 and according to your business needs.
Download details: Productivity Hub. Community Kit for SharePoint. SharePoint World Clock and Weather Web Part. A Matter Of Degree: Differences between a MOSS 2007 / SharePoint Publishing Site and a System Site (or Team Site) Accessing user profile information in WSS 3.0 with javascript « SharePoint JavaScript's. 18.09.2011 I have posted a new solution which makes this one obsolete. You find the new one here 09.09.2010 Updated the function “getUserInfo”. It no longer requires the list GUID for the user list to be specified in the script. 31.10.2009: Small update for default picture in the example CEWP. This article describes how to access the “user profile” under WSS 3.0 via javascript. The method used is a query trough the webservice lists.asmx.
I use some code (“interaction.js” and stringBuffer.js”) created by Erucy and published on codeplex. The jQuery-library is found here. As always we begin like this: Create a document library to hold your scripts (or a folder on the root created in SharePoint Designer). You can call this script from any page. Refer these scripts: interaction.js // Erucy – stringBuffer.js // Erucy – jQuery // You call the script from a standard CEWP like this: document.write(str); </script> [/javascript] SharePoint People Search – Lessons learned. Part 2: Programmatically running search queries.
In the first part of the SharePoint People Search – Lessons learned article we’ve discussed the basics of configuring SharePoint People Search. We have also looked at how it could be used for a facebook solution and what the shortcomings are. In this part we will explore different aspects you are very likely to face while creating a custom facebook solution based on SharePoint People Search. Introduction If the standard search functionality provided by SharePoint is insufficient for your requirements, you are very likely to develop your own Web Parts. SharePoint supports such scenario by providing two mechanisms for communicating with the Search Service.
Searching using the SharePoint Search Object Model If the custom search solution that you’re creating is going to be deployed on the same server that contains the information you want to present, you are very likely to use the SharePoint Search Object Model. Firing search queries using the Search Web Service Presenting the Search Results. Search. STSADM Commands. Erwin van der Valk's blog: Practicing patterns : p&p Sharepoint guidance v2.
Since the Prism project is done, I’ll be working on a different project for the next couple of months. Sharepoint guidance on Codeplex The goal of this project is to provide guidance on how to build Sharepoint applications in a professional way. V1 of the Sharepoint guidance project focused mainly around the following aspects: How to work with development, testing and production environments. How to build sharepoint solutions in a Test Driven fashion. How to set up a Continious Integration environment, that does our Builds, and runs our Unit and Acceptance Tests How to build Sharepoint applications that can be versioned. To do this, we’ve built a reference implementation that demonstrates all of these concepts. We are now well on our way with the Sharepoint Guidance and are already in iteration 6 (we have two week interations). In V2, we have the following goals: Last Friday, we’ve released drop 5 to codeplex.
Web.config changes Conclusion. Twitter Search WebPart | Sharing The Point. Posted by mjimisonon March 04, 2009ASP.Net, C#, Linq, SharePoint, Twitter, WebPart Download now: WSP Solution | Source Code (zip) I used to play in a punk rock band, and we often joked that with only so many bar chords to play, we often copied our own songs unintentionally. When you are writing a blog, it can be difficult to know when someone else has already written on the subject you’ve chosen, or if you’ve just coincidentally stumbled upon something already out there.
I am positive there are other Twitter-related SharePoint posts written, but I haven’t seen any offer a configurable webpart like I’m about to do. Finished Product Screenshots: (Click for larger images) Here are the inspirations for my post, including some of the source code for querying the Twitter Search API via Linq: Here is how I made this project my own: The source code and wsp file are both available for download. Installation Instructions: Closing Thoughts: This was a fun project to create. Cheers. Matt. SharePoint Toolbox - Home. Differences between WSS 3.0 and MOSS 2007 - Sha... Huddle API: Facebook Meets Sharepoint. SharePoint: Creating HttpHandler for user profi... I have custom authentication and user profiles solution where user profiles are stored in list. This list is directly accessible only to administrators. Users can register to site and modify their profiles through special pages that run profile operations under elevated privileges.
Users have three versions of their avatar: 64x64, 32x32 and 16x16. These avatars are saved as user profile attachments when user uploads his or her avatar. Here is shortened draft version of my code (I removed some complex guard checks that use custom extensions methods for SharePoint objects). public class ProfileImageHandler : IHttpHandler public bool IsReusable get { return true; } public void ProcessRequest(HttpContext context) var request = context.Request; var response = context.Response; var idString = request.QueryString["id"]; var sizeString = request.QueryString["size"]; var id = 0; int.TryParse(idString, out id); var siteId = SPContext.Current.Site.ID; var sec = new SPSecurity.CodeToRunElevated(delegate()
Community Kit for SharePoint - Home. Determine hardware and software requirements (Office SharePoint Server) Alex Tcherniakhovski - Security : Adding workfl... MIIS Workflow Extensibility. Microsoft Enterprise Content Management (ECM) T... Hierarchical object store vs Property bag. Web Parts » Andy Burns SharePoint Blog.