InfoWorker Solutions This post is a how-to guide for customizing the ootb SharePoint 2010 content approval workflow to automatically pick a user from the current list item such as the 'content resposible' field, and assign that user as the approver of the content, using SharePoint Designer. The customization of the content approval using SPD is quite straightforwards except for some less intuitive and misleading options for editing the workflow task process. It also involves publishing and editing the XML config of the workflow to enable using the "Start this workflow to approve publishing a major version of an item" option for automatically starting the approval workflow when the author check-in (submits) the page or document for approval.
Every Web Part should have a .webpart file, which is an XML file that describes the Web Part. The .webpart file also makes your Web Part appear in the Web Part gallery. This topic explains the easiest way to create a .webpart file. Step 5: Create a .webpart File for your Web Part
Using Custom ASP.NET Controls in SharePoint 2007 - Vedant Kulshreshtha Like ASP.NET Web Parts you can also use ASP.NET Controls in SharePoint 2007. I have put together a comparison between them in context of their use in SharePoint: Similarities Custom Properties are supported Can exist inside as well as outside a web part zone Can be used in a master page or page layout Needs a SafeControl entry in web.config file Runs under SharePoint and current user context Advantage of Web Parts Web Part Gallery is available to manage them at site collection level Can be added/removed using web browser or SharePoint Designer or even a C# code When inside a Web Part Zone, Web Parts can be moved around and also personalized by end-users using a web browser Default/Custom Editor Part can be used to manage properties through web browser Audience targeting can be used Can be used in a content/site page
SharePoint: How to display blog feed using XML Web Part? - Gunnar Peipman's ASP.NET blog
Installing MOSS 2007 on Windows Server 2008 and SQL Server 2008 - Part 7: Configuring MOSS 2007 This article is a part of a series describing the installation of Microsoft Office SharePoint Server 2007 (MOSS) on a Windows Server 2008 with the newly released SQL Server 2008. The successful creation of a Shared Service Provider wasn't an easy task for me and included a lot of trial and error until I figured out how to do it right and what I have to think about during the configuration process. After that the creation is an easy task. If you remember the domain accounts from the previous posts there are a lot of them which haven't been used right now. And here it's important that these account are domain accounts.
Application pool crash on win2008
MSDN Library Design Tools Development Tools and Languages Mobile and Embedded Development Walkthrough: Creating a Basic SharePoint Web Part
This is one of those occasions where I wished I had multiple categories enabled on my blog :-). Anyway, I wrote this blog engine, and I have limited time to enhance this, so I'll live with what I have for now, and categorize this under SharePoint. So the 20cent question is - Can SharePoint 2007 host WCF services? The answer is - Yes! But it takes some findiggling. SharePoint as a WCF Host
Recommended Reading: SharePoint as a WCF host. Specifically there are 4 easy steps - 1. Create a WCF Home. This is the virtual directory that will host all your WCF endpoints.2. Create a WCF Service Library, and throw it in the GAC.3. Winsmarts SharePoint WCF Support
With ASP.NET AJAX Extensions being baked into the .NET Framework 3.5 and the improvements to WCF to support JSON, it seems tempting to write WCF services and host the in Windows Sharepoint Services 3.0 Unfortunately, if you create a WCF service and drop it under a WSS controlled vroot like _layouts or _vti_bin, your service will fail to activate with the following message in the event log: WebHost failed to process a request. Exception: System.ArgumentException: virtualPath at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result) If you attach a debugger to w3wp.exe and enable break on first CLR change exceptions, the stack trace at the time of the failure will look like: Hosting a WCF service in Windows Sharepoint Services v3.0 - Gilles' WebLog
Custom Site Theme for SharePoint 2007 (MOSS 2007) and WSS 3.0 « SharePoint Solutions….by HG
Kurt Shintaku's Blog We are pleased to announce the general availability of version 9.0 of the Microsoft Assessment and Planning (MAP) Toolkit. This release of the MAP Toolkit helps increase the agility and cost effectiveness of deploying the latest Microsoft technologies. It also enhances usage tracking to include accounting for Remote Desktop Services as well as Server and Cloud Enrollment licensed deployments. MAP 9.0 additionally helps organizations assess their environment for Office 2013 and Office 365, track usage of Windows Server 2012, Lync Server 2013, SharePoint Server 2013, Exchange Server 2013, System Center Configuration Manager 2012, and SQL Server 2012.
Preface: I wrote this post after spending a month digging deeply into SharePoint, attempting to customize and brand the site as well as migrate all my help content to it. If you’re totally unfamiliar with SharePoint, this post will not get you up to speed. But for those embarking on a SharePoint customization challenge, most likely you’re already familiar with SharePoint. Reading these ten concepts and gotchas will help you avoid some of the pitfalls I encountered when customizing my site. Note: When I say “SharePoint,” I’m really referring to MOSS 2007. Customizing Your SharePoint Site? Read These 10 Concepts/Gotchas First
We’ve seen a serious increase in migration to SharePoint 2013 compare with last year but SharePoint 2013 adoption lags behind SharePoint 2010 mostly due to the fact that many companies invested significantly in SharePoint 2010 customizations and staff training. According to Forrester’s research, SharePoint is still gaining notable traction in the smaller markets as well as organizations with less than 500 employees. More… Following many requests to convert our popular responsive Avicia Office365 theme to SharePoint 2013, I have finally found the time to do it. Not an easy ride, since I had to go through the painful SharePoint 2013 installation on a virtual machine. But now that SP2013 is perfectly rolling I started to actually enjoy it.
Steps required to add an icon to Sharepoint's (WSS3.0) file type icon repository: Copy your icon image file to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images Locate and edit C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Xml\DOCICON.XML Add an entry for the new/unknown file extension - mapping key="xxx" value="myimage.gif" (where XXX = Filename extension) Perform an IISRESET. Adding Icons For Unknown File Types in WSS3.0
SharePoint 2007 CSS Reference Chart by Heather Solomon and the sharepoint experience See also: » SharePoint 2007 Design Articles and Info The following CSS reference guide highlights the major styles used in MOSS and WSS v3 sites. The guide is organized by area of the page and include the style name, function, CSS file name and approximate line number and a sample screenshot of the style location on the screen. Additionally, there is a "Copy to Clipboard" function that will copy the source code for the style to your client machine's clipboard for use in your own CSS file. Use these guides to identify styles that can be overridden for your custom branding and installation or to quickly reference style name and CSS information for customization.
I have a WSS 3.0 server that needs to be moved into ourMOSS 2007 Farm. The WSS server will not be able to be added to the farm since it is off-site and we also don't have anotherMOSS 2007 License available (nor will our budget allow us to purchase one). This WSS 3.0 server has only 3 sites but over 200 users are accessing the data on the server. Also the server is not a member of a Domain (contained within a DMZ) , so all users have been given local user accounts. One reason I'm asking what sound like I should be able to answer myself is that I do not have access to the WSS 3.0 server at this time. Move WSS 3.0 content to MOSS 2007
Introduction Microsoft Office is very tightly integrated with SharePoint by utilizing its web services. Windows SharePoint Services comes with sixteen different web services. Talk to SharePoint Through its Web Services [Archive] | SharePoint Monitor
Microsoft® SharePoint® Designer 2010 Step by Step - O'Reilly Media
SharePoint 2010 Security
Creating a Page Layout in SharePoint 2010 using Visual Studio 2010 - Becky Bertram's Blog
A SharePoint server is not installed on this computer.
Managing SharePoint Designer 2010
Whats New in SharePoint 2010