Having usable and accurate navigation is essential to the success of your SharePoint site. SharePoint’s default navigation can be used to create concise main navigation menus, and can even support taxonomy via Managed Navigation. Visually & functionally, however, you’re limited to a simple 4-level deep flyout/dropdown menu for the main navigation. In the side Quick Launch menus, hierarchy can be implied with simple indenting of the text links.
In both of those main navigation areas of SharePoint, the out-of-the-box experience does have some definite UI and UX constraints.
The Mega menus concept
Now, mega menus are probably well familiar to anyone and everyone by now- it was an up and coming design trend back in the late 2000’s. Old hat – but let’s review the fundamentals of this design pattern first:
Typically, a mega menu:
- is a single drop-down that appears on hover
- shows all the options in one large panel
- groups options into related categories
- uses icons or other graphics to help the user.
They can succeed because:
- They offer a good compromise between simple and expanding menus.
- They are easy to use and should suffer fewer accessibility problems.
- They can condense a lot of information architecture artifacts into a small amount of screen real estate
Mega menus done right
Mega menus gone WRONG
Mega menu best practices
Mega menus in Ecommerce – design Trends from 2011 vs 2014
Now, in the SharePoint world, there arose a number of solutions to be able to implement mega menu-style navigation systems in response to the growing demand. Some examples:
SharePoint Mega Menu from a DVWP and a List
BindTuning – How to use BindTuning’s Mega Menu
Mega Menu for SharePoint
Finally, here’s a gallery of some SharePoint sites using mega menus, which are either custom coded or leveraging commercial mega menus:
SharePoint sites using mega menus
The Archetonomy Solution
The Archetonomy Mega Menu system is a farm solution for on-premise SharePoint 2010, 2013 & 2016, and has the broadest feature set of any 3rd party solution that I know of in this vein for SharePoint. After positive experiences with the product, I figure it’s time to give it a review.
- Comprehensive What-You-See-Is-What-You-Get administration/design interface
- Styles can be applied ad-hoc, with inline or formalized CSS, or a combination of both
- Import/Export of menu configuration as an XML file eases transitioning to different environments
- Design workflow flexibility: Power users & less technical stakeholders can do initial mock-ups with the visual designer directly in the GUI, and then hand it over to a front-end developer to formalize CSS later
- While the drag and drop and visual design surface (which shows real-time X/Y coordinates of menu elements) increases efficiency and overall ease of use, it’s tedious to get everything to line up pixel-perfect when doing manual designs. What would really help is the ability to select multiple elements and align them left/right/top with one click, as can be done in programs like Visio, Photoshop etc.
- Archetonomy Megamenus are currently only for on-premise SharePoint. Office 365 SharePoint Online is not currently supported. I did hear that a SharePoint Online version might be in the works but have not seen an update about that.
- Links & content in the menu can be displayed dynamically, either individually or in sections, based on:
- Content search queries, for example:
- query selects the top 10 most downloaded documents from the HR department
- selects results based on what logged In user is currently viewing the page (e.g. the last 10 documents I personally accessed)
- Managed Metadata tagged content: the hierarchy of words that reflects organizational structure, business units & concepts can be reflected in the menu
- Managed Navigation (TermStore): The specialized portion of Managed Metadata that is focused on site navigation, can be used. This gives special advantages like being able to use “friendly” URL’s.
- SharePoint list managed navigation (with folder grouping): Standard SharePoint Lists can be used as the place where links are added. This gives the special advantage that the admin can assign certain user permissions to edit that list, allowing isolation of edit rights for the overall menu:
- For example, the admin could add a section of links in the Marketing Department section of the main menu, which draws its data from a SharePoint list in the Marketing Departments site collection. A user in Marketing with basic training on how to work with SharePoint Lists, could be delegated access to be able to add/edit/remove links from that SharePoint List. This user would not be able to edit anything else in the main menu system other than the links generated by their specific SP List.
- Three-level hierarchy (List Panels): It’s possible to maximize “screen real estate” and offer a richer selection of content, by adding an interactive Panel bar section. When a user clicks on a horizontal link section, the related content area displays in the same dropdown. In this way we can multiply the amount of content that can be displayed in single, fixed size menu dropdown area:
- Publishing Pages: When this section is added to menu, it will automatically display all pages in the current Sites Publishing Pages Library, which is the standard place where SharePoint Publishing Pages are created. This makes it simple to render the most typical type of SharePoint CMS content.
- Audiences, which are predefined groups that users can be added into, for example a typical use case could be “New Hires”, whereby any user in that group is shown menu content & links focused on onboarding topics.
- Search input boxes can be added anywhere inside the dropdown menu, with the search boxes optionally sending users to specialized search results pages. For example, a search input box inside a HR Department menu dropdown, could send the user to a search results page focused only on HR-related content
Design & Ease of Use
- Standardized CSS can be used, for example as part of a Branding Solution. In this way, when one adds a new links or content, it can already by default inherit the overall corporate branding styles.
- Content and site designers can design and create menus directly in the browser without needing to write HTML or CSS
- Although designing and building menus with Mega Drop Down for SharePoint is not difficult, building highly functional menus requires several skillsets. While the same person can represent many of these skillsets, identifying these roles upfront will further increase your menu’s adoption rate:
- Information Architect – Responsible for understanding what content exists within your site and defining what options are available for accessing content.
- UI Designer – Responsible for designing an intuitive and effective interface.
- UI Developer – Responsible for implementing the design. This person is typically responsible for building the HTML and CSS.
- Menu Administrator – Responsible for managing the links and updating navigation content.
- Menu Sub-Administrators– Users in the organization who are granted selective access to add or edit only certain portions of the menu, such as a user in the Marketing Department given access to edit just links & content in that section of the menu
License Manager Installation Guide
Mega Drop Down Installation and User Guide
Product Release Notes
Although it’s a shame there’s not a SharePoint Online version of this, it’s still a powerful menu system for those with on-premise SharePoint. The ability to visually design the menu layouts and content is a big win, especially for rapid prototyping – although one needs to consider carefully how much the design should be controlled by manual activities vs how much should be put on rails by creating formal CSS rules.
Being able to add complex controls like Search Inputs, or deliver link content based on Content Search queries can help create truly useful navigation systems. With mega menu powers, comes mega responsibilities: putting everything including the kitchen sink into a menu navigation system also can create it’s own user experience issues, so one has to to be mindful that underlying usability is paid attention to.
Thought i’d share that there’s an IE port of a valuable plugin i’ve used in Firefox for a while, View Source Chart:
Steps to get beautiful, visually sensible HTML source viewing in IE9:
1. Copy the script below and paste it into a new browser bookmark.
2. Click the bookmark from any page to view its source chart.
For other browsers, check the first code block on this page.
About View Source Chart
Cross-browser bookmarklet now available at viewsourcechart.com
A PICTURE SAYS A THOUSAND WORDS
Eyesight is the most efficient way for the human brain to process information. By placing visual boundaries where they already exist invisibly, Source Charting enables you to take in DOM structure and hierarchy as fast as your brain possibly can.
IT’S BETTER BECAUSE…
When mentally building tag boundaries by reading a tag name, then using manual actions like clicking, finding and scrolling, we experience forced breaks in cognitive processing. As the DOM becomes more complex, more productivity is lost. It doesn’t take long before mentally navigating the DOM becomes impossible.
Source Charting eliminates the need for processing any other way but the fastest: visually. It provides an instant and complete visualization of hierarchical nesting of any tag in the view port.
* Defines HTML Tag Boundaries (so you don’t have to)
* Defines DOM Structure and Hierarchy (so you don’t have to)
Case In Point: The Misapplication of Flowchart-style UI for DOM Inspectors
DOM inspectors and Folder Viewers have historically (and mistakenly) used flowchart-style GUIs to help users navigate hierarchies. The problem is that this type of GUI is intended to convey sequential movement or flow, not structure.
Because sequence and flow is measured one step at a time, the lines connecting elements in a flowchart-like GUI span only one generation (parent-child). When used to depict complex hierarchical structures like the DOM, the user is forced to inefficiently and inaccurately measure hierarchical nesting levels using white space indentation. (See image #3 above)
It is precisely this subtle but monumental mistake that View Source Chart overcomes.
The only way to visualize structure accurately is to measure hierarchical nesting. This is done simply by pictorially delineating element boundaries, which results in a manifestation of document structure.
For a full de-bugging How-To, visit http://viewsourcechart.com/what-why-how
Cross-browser bookmarklet available at http://viewsourcechart.com/get-the-bookmarklet
The CssRegistration control adds each of the style sheets to an internal collection in the SPContext and the CssLink renders each of them in alphabetical order before rendering the primary, default, and alternate CSS links. If you want one of them to appear after core.css, set the DefaultUrl property of CssLink.
<Sharepoint:CssLink runat="server" DefaultUrl="<% $SPUrl:~SiteCollection/Style Library/en-us/Core Styles/Style.css %>"/>
<SharePoint:CssRegistration Name="<%$ SPUrl:~sitecollection/Style Library/en-us/Core Styles/Style.css %>"
After="corev4.css" runat="server" EnableCssTheming="true"/>
It’s very easy to get confused by this because the CssRegistration controls are after CssLink, but they don’t render the links, CssLink does!
One advantage that the publishing definitions have over the SharePoint default.master is the $SPUrl expression that allows dynamic creation of the URL for sites under the root web that use the root web’s master pages. Unfortunately, while CssRegistration is part of the core Microsoft.SharePoint.dll, $SPUrl requires the publishing features to be turned on.
For a JS reference, it’s important to note that ScriptLink doesn’t support the expression builders like . If the script available in top-Level site, you can use:
<SharePoint:Scriptlink runat="server" name="~SiteCollection/Style Library/en-us/Core Styles/JS/script1.js"
If the script avaialble in the current site, we can use:
<SharePoint:Scriptlink runat="server" name="~Site/Style Library/en-us/Core Styles/JS/script1.js"
The SharePoint 2010 101 Code Samples set of examples is an excellent starting point for Developing with SharePoint.
Each code sample is part of the SharePoint 2010 101 code samples project. These samples are provided so that you can incorporate them directly in your code.
Each code sample consists of a standalone project created in Microsoft Visual Studio 2010 and demonstrates a distinct feature or feature set. Each sample includes comments describing the sample and the expected results. Each sample also contains comments that explain how to set up your environment so that the sample code runs, where necessary.
To open a solution:
1. Start Microsoft Visual Studio 2010.
2. On the File menu, click Open, and then click Project/Solution.
3. Navigate to the folder containing the .sln file, select it, and then click Open.
To run a solution:
1. In the solution files, read and follow the comments that describe how to set up your environment if necessary.
2. On the Build menu, click Build Solution.
3. When you have a successful build, right-click the project in the Solution Explorer window, and then click Deploy.
List of all Examples in the pack:
SharePoint 2010 Developing Styled Master Pages
This sample creates and deploys branded master pages to customize SharePoint sites, including custom stylesheets and images.
SharePoint 2010 Developing JQuery-Enabled Web Parts
This sample develops a Web Part that uses the JQuery library to display items from a SharePoint list.
SharePoint 2010 Hosting Silverlight Applications that Call Azure Services
This sample calls WCF web services that are hosted in Windows Azure from Silverlight applications that are stored in SharePoint.
SharePoint 2010 Developing AJAX-Enabled Web Parts
This sample creates a SharePoint Web Part that uses Ajax UpdatePanel and UpdateProgress controls to call server-side methods.
SharePoint 2010 Leveraging HTML5 Objects in SharePoint
This sample uses custom SharePoint master pages to enable IE9 and other compliant browsers to render HTML5 tags such as <audio>.
SharePoint 2010 Creating List Items from Silverlight
This sample creates SharePoint list items by calling the SharePoint Client Object Model from Silverlight applications.
SharePoint 2010 Developing Web Templates
This sample creates web templates, which are similar to SharePoint site definitions, but can be used in sandboxed solutions.
SharePoint 2010 Creating Document Sets Programmatically
This sample creates new SharePoint document sets and configures their properties.
SharePoint 2010 Developing List Definitions
This sample uses declarative programming to create a SharePoint list definition and an instance of that list.
SharePoint 2010 Developing Custom Navigation Providers
This sample creates and deploys two links to the top link bar on a SharePoint site.
SharePoint Online Accessing Web Services
This sample connects to SharePoint Online, authenticates by using claims authentication, and then displays the contents of a SharePoint Online list.
SharePoint 2010 Querying SQL Azure Data from Web Parts
This sample queries a SQL Azure database from code in a SharePoint Web Part.
SharePoint 2010 Developing Sequential Workflows
This sample develops SharePoint sequential workflows based on items in task lists.
SharePoint 2010 Creating Custom Field Types
This sample creates a new field type that adds options for users who create new columns in SharePoint lists, libraries, or content types.
SharePoint 2010 Creating Items in Lists from External WCF Services
This sample creates SharePoint list items by calling a method in a WCF service that uses the SharePoint List Data Retrieval Web Service.
SharePoint 2010 Developing Workflow Activities
This sample creates and deploys custom workflow activities that can be used in SharePoint Designer to extend workflows.
SharePoint 2010 Performing Cross-List Queries
This sample uses the SPSiteDataQuery class to find items from all the lists in a SharePoint site.
SharePoint 2010 Creating Custom Timer Jobs
This sample creates and schedules a SharePoint timer job that runs code at regular intervals.
SharePoint 2010 Developing Starter Master Pages
This sample sets master pages for SharePoint sites by using feature receivers, and deploys master pages without styles or images as starters for branded master pages.
SharePoint 2010 Updating SQL Azure Records from Web Parts
This sample saves changes to a SQL Azure record by using code in a SharePoint Web Part.
SharePoint 2010 Uploading SharePoint Library Content to Azure Storage
This sample uploads files from a SharePoint document library to Windows Azure storage.
SharePoint 2010 Displaying Video Files Stored in Azure
This sample displays videos stored in Windows Azure in Silverlight applications.
SharePoint 2010 Creating SQL Azure Records from Web Parts
This sample inserts records into SQL Azure tables by using code in SharePoint Web Parts.
SharePoint 2010 Developing Feature Receivers
This sample develops a Feature receiver that performs an action when Features activate and cleans up when Features deactivate.
SharePoint 2010 Calling Azure Services from Event Receivers
This sample calls WCF web services hosted in Windows Azure from SharePoint event receivers.
This sample uses the SharePoint Client Object Model to display the details of all the items in a SharePoint list.
SharePoint 2010 Creating Custom SharePoint Service Applications
This sample returns the current weekday by using a custom service application for SharePoint.
SharePoint 2010 Creating Content Types Programmatically
This sample creates SharePoint content types nondeclaratively in code.
SharePoint 2010 Developing Connected Web Parts
This sample creates two SharePoint Web Parts that you can connect to exchange information.
SharePoint Online Authenticating Using the Client-Side Object Model
This sample connects to, and authenticates in, SharePoint Online.
SharePoint 2010 Using REST to Discover the Contents of Excel Worksheets
This sample displays the names of tables that are in a spreadsheet by calling RESTful Excel Web Services.
SharePoint 2010 Displaying User Profile Pictures Programmatically
This sample evaluates and displays the pictures of all users who have set profile pictures in a Web Part.
SharePoint 2010 Using LINQ in REST Requests
This sample uses LINQ queries to return filtered lists of items from SharePoint lists.
SharePoint 2010 Accessing SharePoint Lists from External WCF Services
This sample writes a WCF service that returns all the items in SharePoint lists, and includes a sample client console application to test the service.
SharePoint 2010 Calling Azure Services from Web Parts
This sample calls WCF web services hosted in Windows Azure from SharePoint Web Parts.
SharePoint 2010 Performing Searches from Silverlight
This sample calls the SharePoint Search web service from a Silverlight application.
SharePoint 2010 Performing Searches from Web Parts
This sample calls a SharePoint Search or FAST Search service application from a Web Part.
SharePoint 2010 Creating Content Organizer Rules Programmatically
This sample creates and configures content organizer rules for content types in SharePoint document libraries.
SharePoint 2010 Creating Taxonomies Programmatically
This sample adds SharePoint groups, term sets, and terms to a term store programmatically.
SharePoint 2010 Developing Custom Field Controls
This sample creates custom field controls that display and edit fields on SharePoint publishing sites.
SharePoint 2010 Developing Application Pages
This sample creates and deploys a simple application page that displays information about the current SharePoint site, and modifies its description.
SharePoint 2010 Programmatically Reading User Profile Properties
This sample obtains properties from all SharePoint user profiles in your organization.
SharePoint 2010 Developing Event Receivers
This sample develops and registers an event receiver that intercepts SharePoint list item events such as ItemAdded and ItemUpdating.
SharePoint 2010 Managing Document Sets Programmatically
This sample reads properties from all the document sets in a given SharePoint document library.
SharePoint 2010 Deleting SQL Azure Records from Web Parts
This sample deletes records in SQL Azure by using code in SharePoint Web Parts.
SharePoint 2010 Calling Azure Services from Custom Workflow Activities
This sample calls WCF web services hosted in Windows Azure from code in SharePoint workflows.
SharePoint 2010 Accessing List Items from Silverlight
This sample returns items in SharePoint lists (in Silverlight applications) by using the SharePoint Client Object Model.
SharePoint Online Creating Documents Using Word, PowerPoint, or OneNote Web App
SharePoint Online Creating and Deploying Sandboxed Workflow Activities
This sample creates a workflow activity that functions in a sandboxed solution on SharePoint Online.
SharePoint 2010 Importing Content by Using the Content Deployment API
This sample imports content from CMP files into SharePoint lists by calling the Content Migration API.
SharePoint 2010 Developing Connected Silverlight Web Parts
This sample creates interconnected custom SharePoint Web Parts that can host Silverlight applications that exchange information.
SharePoint 2010 Programmatically Finding Tagged Items
This sample locates terms that match input strings and then locates all items tagged with those terms in SharePoint lists.
SharePoint 2010 Logging Site Events Programmatically
This sample develops and registers event receivers to intercept web events such as SiteDeleted and WebMoved, and logs those events to a list for auditors.
SharePoint 2010 Using REST to Obtain Excel Charts
This sample obtains image files of charts from Excel spreadsheets via REST.
SharePoint 2010 Calling WCF Services from Web Parts
This sample calls a WCF service that retrieves data after users click a button in a SharePoint Web Part.
SharePoint 2010 Deleting Items in Lists from External WCF Services
This sample creates a WCF service that finds a SharePoint item and deletes it.
This sample uses the SharePoint Client Object Model to change items in SharePoint lists.
SharePoint 2010 Developing Page Layouts
This sample creates and deploys custom page layouts for content types in SharePoint publishing sites.
SharePoint 2010 Declaring Records Programmatically
This sample can determine whether a document is a record and declare it as a record.
SharePoint 2010 Calling Azure Services from Timer Jobs
This sample calls WCF web services hosted in Windows Azure from SharePoint timer jobs.
SharePoint 2010 Developing Solution Validators
This sample develops SharePoint solution validators that check activating user solutions and help verify sandboxed solutions.
SharePoint 2010 Developing Custom Expiration Actions
This sample specifies custom actions to take and code to run after a document expires against a SharePoint information management policy.
SharePoint 2010 Retrieving List Contents and Parsing Atom Responses
This sample gets all the items in a SharePoint list by using the RESTful List Data web service.
SharePoint Online Creating and Deploying Sandboxed Event Receivers
This sample responds to item events (such as ItemAdded) in sandboxed event receivers.
SharePoint 2010 Using REST to Query Data Ranges in Excel Worksheets
This sample gets and displays data from a date range in an Excel spreadsheet by querying RESTful Excel Web Services.
SharePoint 2010 Developing Ribbon Actions
SharePoint 2010 Developing Delegate Controls
This sample creates an ASP.NET user control to replace the standard SharePoint Global Navigation.
SharePoint 2010 Working with Disposable Objects
This sample disposes SPWeb and SPSite objects properly so that they do not unnecessarily consume memory.
SharePoint 2010 Logging Data to the Developer Dashboard
This sample uses monitored scopes to log information to developer dashboards, and includes scripts to enable and disable those dashboards.
SharePoint Online Creating Excel Worksheets by Using Excel Web App
SharePoint 2010 Using JQuery to Retrieve List Contents in JSON
This sample uses the JQuery library to obtain and display items in SharePoint lists.
SharePoint 2010 Retrieving Single List Items in REST Requests
This sample gets a single item from a SharePoint list by using the RESTful List Data web service.
SharePoint 2010 Calling WCF Services from Custom Workflow Activities
This sample calls a WCF service from a SharePoint workflow that starts after a new item is created, and then modifies the item body field of that workflow.
SharePoint 2010 Retrieving List Contents in JSON Format and Parsing Responses
This sample gets items from SharePoint lists in JSON format, parses the responses, and then displays the item properties.
This sample uses the SharePoint Client Object Model to display an application page as a dialog box.
SharePoint 2010 Calling WCF Services from Event Receivers
This sample calls a WCF service from an event receiver; after a new item is added to a SharePoint list, the service returns data that is appended to the body of that new item.
SharePoint 2010 Performing Cached Cross-Site Queries
This sample uses the SharePoint PortalSiteMapProvider class to perform high-performance cross-site queries.
SharePoint 2010 Using REST to Create a SharePoint and Bing Maps Mashup
This sample uses SharePoint status and notifications to feed back information to users.
This sample uses the SharePoint Client Object Model with a CAML query to return matching items from lists.
SharePoint 2010 Developing Branded Media Controls
This sample brands a Media Field Control on a SharePoint site.
This sample uses the SharePoint Client Object Model to set titles and descriptions for SharePoint sites.
This sample uses the SharePoint Client Object Model to display information about the current SharePoint site.
SharePoint 2010 Developing Editor Web Parts
This sample modifies a Web Part properties sheet to include an Editor Web Part that enables users to choose from all the lists in the SharePoint site.
SharePoint 2010 Calling RESTful SharePoint Services From Desktop Applications
This sample uses a service reference to connect to the List Data Retrieval Web Service and display lists of SharePoint items in a Data Grid.
SharePoint Online Accessing Current User Information in Sandboxed Solutions
This sample creates a Web Part that functions in a sandboxed solution on SharePoint Online and gets information about the current user.
SharePoint 2010 Canceling Synchronous Events
This sample checks the properties of synchronous events and cancels them to prevent users from deleting SharePoint items.
SharePoint 2010 Calling WCF Services Hosted in SharePoint
This sample calls a WCF service that is hosted by Sharepoint, and whose code uses the SharePoint Foundation Server-Side Object Model.
SharePoint 2010 Developing Ribbon Drop Down Controls
This sample uses a drop-down control on the SharePoint ribbon to forward users to the selected list.
SharePoint 2010 Developing State Machine Workflows
This sample develops state machine workflows based on documents in SharePoint document libraries and items in tasks lists.
SharePoint Online Deploying Sandboxed Content Types and List Definitions
This sample creates a Web Part that functions in a sandboxed solution on SharePoint Online and uses code to create content types and list definitions.
SharePoint 2010 Developing Sandboxed Web Parts
This sample creates a Web Part in a sandboxed solution, and includes Panels to hide controls, radio buttons, and the Render method.
This sample uses the SharePoint Client Object Model to display information about the current site collection.
SharePoint 2010 Calling WCF Services from Timer Jobs
This sample calls a WCF service from a custom timer job that creates a new announcement when it runs.
SharePoint 2010 Developing Site Definitions
This sample creates a custom SharePoint site definition that specifies Content Editor and Image Viewer Web Parts on a Web Part page.
SharePoint 2010 Developing Custom Expiration Formulae
This sample calculates an expiration date for a SharePoint information management policy by using a custom expiration formula.
SharePoint Online Creating and Deploying Sandboxed Web Parts
This sample creates a Web Part that checks whether it is in a sandboxed solution and displays the title of the SharePoint site.
SharePoint 2010 Exporting Content by Using the Content Deployment API
This sample exports content from SharePoint lists by calling the Content Migration API.
SharePoint Online Creating and Deploying Sandboxed Feature Receivers
This sample creates a feature receiver that works in a SharePoint Online sandboxed solution.
The Community Kit for SharePoint: Development Tools Edition extends the Visual Studio 2010 SharePoint project system with advanced templates and tools. Using these extensions you will be able to find relevant information from your SharePoint environments without leaving Visual Studio. You will have greater productivity while developing SharePoint components and you will have greater deployment capabilities on your local SharePoint installation.
This version is targeted for users running SharePoint Foundation 2010, for the server version go here.
This project provides extensions to four core areas; Environment, Exploration, Content and Deployment.
Enhancements to the Visual Studio environment include the new SharePoint References tab available on the Add Reference dialog, allowing you to easily reference any SharePoint assembly without searching the file system or GAC for it.
Exploration extends the new SharePoint Explorer with advanced information about SharePoint sites such as the installed Web Parts and Master Pages or the Feature dependencies and elements. Also included in the Explorer are a variety of import functions to bring existing SharePoint items into your active solution.
The Content area includes advanced templates such as Linq to SharePoint, Custom Action or Delegate Control. Become extra productive while developing sandboxed solutions using the SharePoint Full Trust Proxy. Utilise the SharePoint Console Application project template to quickly build SharePoint code.
Our enhanced Deployment functions give you the ability to utilise quick deployment and almost a dozen other productivity enhancing deployment steps, including automated deployment (per file on change deployment).
Find the complete overview of all the CKS Development Tools Edition features on the documentation tab of the project site. The CKS Development Tools Edition works with Microsoft’s Visual Studio 2010 SharePoint Power Tools.
What’s new in this release
The current 2.3 release includes the following features:
– Activate Quick Deploy from global shortcuts – Activating the shortcut keys now from any VS item not just the SP Project.
– New ASHX SPI – New ASHX handler project item template.
– Cancel Adding SPIs – Cancel adding SPIs feature which stops VS automatically adding a SPI to features.
– Updates for Quick Deployment steps – Correct processing of the assembly name.
– Quick Deploy GUID replacable params – Quick deploy now supports GUID based replaceable params and will represent the latest dll version of them.
– Quick Deploy fixes – Improvements to Quick Deploy. Read only files not locked during Quick Deploy.
– WCF SPI Template update – Changes to the SPI to deploy to the root of the ISAPI folder to remove the need for a custom web.config. This should make deployment simple for default WCF SPI’s while still allowing custom implementation with a sub folder and web.config to be done.
If you have a great idea for a deployment tool, template or any other thing that you believe increases developer productivity, contribute! Contact the Project team or add your idea to the discussion forum. Use the #CKSDev tag to follow and connect with the team on Twitter.
About the Community Kit for SharePoint
The Community Kit for SharePoint is a set of editions, components, tools and recommended documentation for SharePoint development. You are currently viewing the edition project site for the Development Tools Edition. To learn about the other editions and components you can go to http://www.communitykitforsharepoint.org/default.aspx.