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
I wanted to show our company's blog feed on our intranet first page. There some empty space I wanted to fill somehow. I found a good solution, so there was no need for some third-party Web Parts. Also there was no need to write any additional code.
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.
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:
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.
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.
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.
Introduction Microsoft Office is very tightly integrated with SharePoint by utilizing its web services. Windows SharePoint Services comes with sixteen different web services.
The smart way to build applications with Microsoft® SharePoint® Designer 2010 -- one step at a time! Experience learning made easy -- and quickly teach yourself how to create SharePoint 2010 applications and workflows with Microsoft® SharePoint® Designer 2010. With Step by Step , you set the pace -- building and practicing the skills you need, just when you need them! Design solutions to meet your business scenario -- without code Customize lists, libraries, and SharePoint site pages Use Web Parts to display, edit, and modify list item data Access data from a variety of external sources Create workflows to automate business processes Use master pages and CSS to control how sites work Your Step by Step digital content includes: All the books practice files -- ready to download and put to work.
Creating a custom Page Layout in SharePoint 2010 is not too different than creating a custom Page Layout in SharePoint 2007. However, the process of creating a SharePoint Solution Package has changed in Visual Studio 2010. This article will walk you through the steps. First, open Visual Studio and create a new C# project, using the "Empty SharePoint Project" template, listed under the SharePoint 2010 project templates. For this example, we'll name our project "MyCustomPageLayout".
Just confirmed .. was able to attach to the remote debugger on the SP2010 virtual machine from a host running VS2010. If your interested in developing locally and remote debugging read on, otherwise follow Corey's advice :) Once the plumbing is set up, it's pretty easy to remote debug. I'm using VS2010 RC1 and SP2010 Beta. Here are the steps to remotely build sharepoint components and remotely debug: Create, build, and deploy your code