Archive

Archive for the ‘SharePoint Designer 2010’ Category

Add an item count to the SharePoint 2010 refinement panel

October 25, 2010 Leave a comment

In the SharePoint 2010 search results page there is a new webpart called the refinement panel.

This webpart displays facets, or refinements to the SharePoint 2010 search results based on categories that you can configure.

One common request in SharePoint 2007 was to add faceted search results with a count of items that belong to each facet.
Since faceted search results were not included in MOSS 2007 a common solution was to use a set of webparts available from CodePlex. http://facetedsearch.codeplex.com/

In SharePoint 2010 the faceted search is available right on the search results page.
However, one thing that is not visible, without some additional steps, is the count of items in each facet.

The goal:

image

The first step is to edit the Faceted Search webpart, then add a line to the Filter Category Definition XML in the Refinement Panel webpart.

A tutorial of what the Filter Category Definition XML can do and how to extend the categories.

image

Add  ShowCounts="Count" to each category you wish to include the count of results for.

In this example I added the ShowCounts=”Count” to the Category where the Title=”Site”.

image

The inclusion of counts is determined by the XSL of the Refinement Panel webpart.
The XSL parameter $ShowCounts looks for the value of ShowCounts=”Count” in the category XML.

image

Since the Refinement Panel webpart is rendered using XSL you have many opportunities for design and customization to meet your branding needs.

Advertisements

Preparation materials published for Exam 70-668: PRO: Microsoft SharePoint 2010, Administrator

The study guide has been published for

Exam 70-668: PRO: Microsoft SharePoint 2010, Administrator

 

Skills Being MeasuredThis exam measures your ability to accomplish the technical tasks listed below.The percentages indicate the relative weight of each major topic area on the exam.

Designing a SharePoint 2010 Farm Topology (27 percent)

  • Design physical architecture.
    • This objective may include but is not limited to: translating information architecture to physical architecture, determining capacity for a SharePoint farm (storage, number of users, bandwidth utilization, intranet/extranet, hardware), and scaling Web farm and services infrastructure
  • Design SharePoint integration with network infrastructure.
    • This objective may include but is not limited to: planning for internal and external farm communications, establishing network perimeter configuration, networking, Active Directory, DNS, SQL storage, IIS, and analyzing infrastructure services
  • Design logical taxonomy.
    • This objective may include but is not limited to: planning sites and site collections, planning for collaboration sites, planning My Site sites, planning for zones, planning for Service Applications, Web applications, content databases, sites and sub-sites vs. libraries, libraries vs. folders vs. document sets, security boundaries, site hierarchy, and content deployment path methodology
  • Plan for sandbox solutions.
    • This objective may include but is not limited to: content isolation, feature deployments, and trusted solutions
  • Plan for farm deployment.
    • This objective may include but is not limited to: sequential deployment, planning standalone deployment (Microsoft SQL Server Express), planning single-server farm (SQL Server), planning multi-server deployment in an N-Tier Farm, and designing a SharePoint virtual environment
  • Plan for availability.
    • This objective may include but is not limited to: designing SQL Server failover clustering strategy, types of availability (high-performance, acceptable downtime, Recovery Point Objective, Recovery Time Objective ), types of mirroring, high availability, high protection, whole farm as a failover cluster, and designing the Web Front-End NLB strategy

Planning SharePoint 2010 Deployment (26 percent)

  • Plan service applications.
    • This objective may include but is not limited to: formulating a Business Connectivity Services (BCS) strategy, planning a Microsoft Excel Services strategy, implementing a BI solution, planning service application server roles, and planning a Web server forms strategy (Plan InfoPath Forms Services)
  • Plan a SharePoint component strategy.
    • This objective may include but is not limited to: Web parts, Web applications, Microsoft .NET, Microsoft Silverlight, SharePoint features and solutions, workflow, site templates, site definitions, multilingual deployment, master pages and layout files, and e-mail integration
  • Plan an upgrade strategy.
    • This objective may include but is not limited to: supporting hardware upgrades (for example, 32 to 64 bit), OS upgrade, in-place upgrade, MOSS upgrade, and SQL Server upgrade
  • Design a migration strategy.
    • This objective may include but is not limited to: database migration, custom features, read-only and detached databases, designing a test and QA implementation plan (for example, development to production), migrating content databases, moving content between farms, moving content to and from the farm, moving content within the farm, and rollback
  • Design security architecture.
    • This objective may include but is not limited to: planning security for WebApp site collection, designing SharePoint users and groups administration, taxonomy of SharePoint security groups, managed accounts, site security (permission levels , list permissions, site permissions, personal permissions, default and custom security groups), and planning for Secure Sockets Layer (SSL)
  • Plan and deploy authentication methods.
    • This objective may include but is not limited to: planning for integration of multiple authentication sources/types, planning for NTLM authentication, planning for Kerberos authentication, planning for Forms-Based Authentication (FBA), planning for Claims Authentication (Identity and Access Management), planning for Secure Store Service

Defining a SharePoint 2010 Operations Strategy and Business Continuity (25 percent)

  • Design a maintenance strategy.
    • This objective may include but is not limited to: preparing test plans for patching and maintenance, SharePoint Maintenance Manager, rebuilding SQL indexes, search maintenance
  • Recommend provisioning strategies.
    • This objective may include but is not limited to: managing self-service components (My Sites, service architecture administration), delegating site administration, limiting site templates and page layouts, assigning quotas, defining policy for Web application
  • Establish an enterprise monitoring plan.
    • This objective may include but is not limited to: developing monitoring points for performance and availability, utilizing performance monitoring, analyzing search reports, Web analytics, diagnostic logging, usage logging, analyzing health and usage data (SharePoint Health Analyzer), and validating farm topology against performance requirements
  • Plan SharePoint backup and restore.
    • This objective may include but is not limited to: developing and testing recovery strategy and implementation plan, server recovery, site recovery, granular backup and recovery strategy, exporting a site or list, recovering data from an unattached content database, and backup and restore of the following: farm, farm configuration, site collection, Web applications, Secure Store Service, snapshots, content database, configuration database, custom features, solutions, code, service, site, list, document library, performance site collection, and recycle bin

Planning for Search and Business Solutions (22 percent)

  • Define search requirements.
    • This objective may include but is not limited to: types of data, types of distribution (Internet, extranet), segregation of data, index file location, index size, federation requirements, content sources, search scopes, search taxonomy, server name mappings, promoting or demoting exclusions, synonyms and compound search processing, and defining facets for search
  • Plan search topology.
    • This objective may include but is not limited to: indexing strategy, index partition, query component, property database, crawler component, separate crawler servers, and administration component
  • Plan an enterprise search strategy.
    • This objective may include but is not limited to: designing information access and enterprise search strategy, planning for metadata and search, people search, search reporting, and planning enterprise search technology
  • Plan enterprise content management.
    • This objective may include but is not limited to: records management, BPM (record deployment), document management, metadata planning, information management policies, implement data taxonomy structure, Web Content Management (WCM), and Information Rights Management (IRM)
  • Plan for social computing and collaboration.
    • This objective may include but is not limited to: user profile service, user profiles, organization profiles, audiences, My Sites, social tags, and planning enterprise wikis, blogs, and personalization sites
  • Plan for a business intelligence strategy.
    • This objective may include but is not limited to: PerformancePoint service (dashboards and scorecards), Excel Services Service, Visio Graphics Service, SQL Reporting Services, chart Web parts, and report center

Preparation materials published for Exam 70-667: TS: Microsoft SharePoint 2010, Configuring

May 17, 2010 1 comment

The study guide has been published for

Exam 70-667: TS: Microsoft SharePoint 2010, Configuring

 

Skills Being MeasuredThis exam measures your ability to accomplish the technical tasks listed below.The percentages indicate the relative weight of each major topic area on the exam.

Installing and Configuring a SharePoint Environment (25 percent)

  • Deploy new installations and upgrades.
    • This objective may include but is not limited to: running Visual Upgrade, performing an in-place upgrade, performing a database attach upgrade, analyzing a PreUpgradeCheck report, installing language packs, and scripting installations; analyzing ULS logs, installation error logs, and event logs to identify installation problems; and repairing installation errors
  • Configure SharePoint farms.
    • This objective may include but is not limited to: configuring inter-server communications, server roles, high availability, InfoPath Forms Services (IPFS), Alternate Access Mappings (AAM), external sites, host headers, and applying and managing patches
  • Configure service applications.

    • This objective may include but is not limited to: configuring service applications such as Business Connectivity Services (BCS), Access Services, Visio Services, Microsoft Office PerformancePoint Server 2007, user profiles, Microsoft Office Excel services, Managed Metadata Services (MMS), and IPFS
  • Configure indexing and search.
    • This objective may include but is not limited to: configuring FAST Search for SharePoint, crawl schedules, iFilters, crawl rules, content sources, scopes, managed properties, content types, search components, index partitioning, and federated search locations

Managing a SharePoint Environment (26 percent)

  • Manage operational settings.
    • This objective may include but is not limited to: configuring logging, quotas, monitoring levels, health reports, security, and SQL Server Reporting Services (SSRS) integration
  • Manage accounts and user roles.
    • This objective may include but is not limited to: managing user accounts, group accounts, managed accounts, computer accounts, and service accounts; and delegating site collection administration
  • Manage authentication providers.
    • This objective may include but is not limited to: managing NTLM, Kerberos, claims-based, and forms-based authentication; and configuring Secure Store Service (SSS) and Active Directory Federation Services (AD FS).

Deploying and Managing Applications (24 percent)

  • Manage Web Applications.
    • This objective may include but is not limited to: managing databases, Web Application settings, security, and policies.
  • Manage site collections.
    • This objective may include but is not limited to: managing site collection policies, features, caching, and auditing; configuring site collection security; configuring multi-tenancy; and configuring site collection quotas and locks.
  • Deploy and manage SharePoint solutions.
    • This objective may include but is not limited to: deploying and managing SharePoint solution packages, managing sandbox solutions, and managing user solutions

Maintaining a SharePoint Environment (25 percent)

  • Backup and restore a SharePoint environment.
    • This objective may include but is not limited to: configuring backup settings; backing up and restoring content, search, and service application databases; detaching and attaching databases; and exporting lists and sites
  • Monitor and analyze a SharePoint environment.
    • This objective may include but is not limited to: generating health, administrative, and Web analytics reports; interpreting usage and trace logs; identifying and resolving health and performance issues
  • Optimize the performance of a SharePoint environment.
    • This objective may include but is not limited to: configuring resource throttling (large list management, object model override); configuring remote Binary Large Objects (BLOB) storage and BLOB and object caching; and optimizing services

Preparation Tools and ResourcesTo help you prepare for this exam, Microsoft Learning recommends that you have hands-on experience with the product and that you use the following training resources. These training resources do not necessarily cover all of the topics listed in the "Skills Measured" tab.

Classroom Training

  • 10174A: TS ITPro: Configuring and Managing Microsoft SharePoint 2010 (5 Days)

Microsoft E-Learning There is no Microsoft E-Learning training currently available.

Microsoft Press Books There are no Microsoft Press books currently available.

Practice Tests There are no practice tests currently available.

Have Questions? For advice about training and certification, connect with peers:

For questions about a specific certification, chat with a Microsoft Certified Professional (MCP):

To find out about recommended blogs, Web sites, and upcoming Live Meetings on popular topics, visit our community site:

Preparation materials posted for Exam 70-576: PRO: Designing and Developing Microsoft SharePoint 2010 Applications

March 8, 2010 Leave a comment

On the Microsoft Learning site the prep materials for the 70-576 PRO exam have been published. It appears that the exam is scheduled to be released June 15 and the exam is still in development.

To see full details visit the Microsoft Learning Center exam description for 70-576

About this Exam

This exam is designed to test the candidate’s knowledge and skills on designing developing applications on the Microsoft SharePoint Server 2010 platform.

Audience Profile

The candidate is responsible for designing custom code for projects that are deployed to SharePoint servers. This includes technology selection across the many ways to build code in SharePoint, ensuring the team development environment is configured, creating a strategy for code deployment, versioning, configuration, or structure.
The candidate also leads a team of SharePoint developers, has at least two years of SharePoint development experience, has at least three years of ASP.NET development experience

Credit Toward Certification

When you pass Exam 70-576: PRO: Designing and Developing Microsoft SharePoint 2010 Applications, you complete the requirements for the following certification(s):

PRO: SharePoint Server Developer

 Skills Being Measured

This exam measures your ability to accomplish the technical tasks listed below.The percentages indicate the relative weight of each major topic area on the exam.

Creating an Application Design (19%)

  • Evaluate application data access and storage

    This objective may include but is not limited to: SharePoint List and relationships, Document Library, SQL Database, BCS, web service, file system, remote BLOB storage, and all other external data sources

  • Identify artifacts from application requirements

    This objective may include but is not limited to: web parts, event receivers, list definitions, list templates, workflows, site definitions, custom actions, content types, site columns, mapping artifacts to application requirements

  • Select a deployment model

    This objective may include but is not limited to: identifying artifacts and execution appropriate for sandbox and farm (i.e. GAC vs. BIN) implementation, designing solutions for single server or multi-server environments, dividing artifacts between sandbox and farm

  • Select the appropriate execution method

    This objective may include but is not limited to: in-page, workflow, event receiver (asynchronous vs. synchronous), timer job, and service application, selecting which logic execution model to use for a problem, determining where code or artifact runs

Designing UX (17%)

  • Determine presentation page type

    This objective may include but is not limited to: Web Part page, application Page, publishing page, page layout, static page

  • Determine SharePoint visual components

    This objective may include but is not limited to: web parts, silverlight, AJAX, ribbon, visual web parts, delegate controls, custom field types, dialog

  • Plan branding strategy

    This objective may include but is not limited to: determining usage of themes, templates, enforce consistency via site definitions, master pages and page layouts, determining usage of CSS styles and JavaScript, designing usage and role of Styles Library or Site Collection Library

  • Design application customization strategy

    This objective may include but is not limited to: supportable customizations allowed through SharePoint UI, SharePoint Designer 2010, VS 2010 (site columns, content types, page customization, themes, page layouts, personalization)

  • Design navigation strategy

    This objective may include but is not limited to: identify inclusion of navigational items (global/current/custom), consume an existing site map provider vs. create a custom provider, determine depth and inclusion of pages/sites, dynamic vs. static navigation, consume an existing navigation control vs. create a custom navigation control

Managing Application Development (18%)

  • Design for localization and globalization

    This objective may include but is not limited to: use and implementation of resource files, variations (content creation and workflow, multilingual content), selecting locales, date and time, regional settings, RTL vs. LTR

  • Develop a security approach

    This objective may include but is not limited to: authentication (NTLM, Kerberos, Forms-based Authentication, claims, Single Sign-On, Anonymous), authorization (SharePoint groups, AD groups, claims, permission levels) enterprise-wide security policies

  • Define application configuration approach

    This objective may include but is not limited to: defining "web.config" modifications, Lists as a configuration option, Property bags, declarative vs. programmatic, SP persisted objects

Optimizing SharePoint Application Design (15%)

  • Optimize page performance

    This objective may include but is not limited to: View State, Inline JS, Inline  CSS, HTML output, AJAX, Client side cache, .NET cache, BLOB Cache, Session State, IIS compression

  • Optimize data access

    This objective may include but is not limited to: SPQuery, SPSiteDataQuery, Large lists, Search (managed properties), SharePoint 2010 query throttling, Client object model vs. web service/rest/SOAP/RPC, Linq

  • Design for logging and exception handling

    This objective may include but is not limited to: Determining appropriate level of logging to include in a custom code project, Evaluating SharePoint log data, Instrumenting code to improve the ability to maintain the system, Determining when exceptions are raised, error values returned, and what should be written to the SharePoint ULS log, Debugger, and Event log

  • Identify and Resolve deployment issues

    This objective may include but is not limited to: single server vs. farm vs. multi-farm, infrastructure vs. content database, web applications, application pools, feature activation failures, pushing applications to front end, security context, feature scope, feature dependencies

  • Analyze memory utilization

    This objective may include but is not limited to: Memory profiling, Disposal of SharePoint objects, Load testing, Identifying memory bottlenecks (hierarchy), Analyze ULS logs, Monitoring memory counters, ensure implemention of IDisposable on custom artifacts containing IDisposable members

Designing SharePoint Composite Applications (13%)

  • Design external application integration

    This objective may include but is not limited to: Selecting appropriate BCS connection from Web Service, .NET Type, and SQL Connection, Defining authentication requirements, Defining solutions that include Office client applications

  • Determine data capture approach

    This objective may include but is not limited to: Evaluate when to use different forms technologies (InfoPath vs. ASP.NET), Office client, Silverlight, BCS, Infopath Forms Services

  • Design SharePoint information architecture

    This objective may include but is not limited to: Content types (local, global), Site columns, Site structure, Taxonomy (managed metadata)

  • Design a workflow solution

    This objective may include but is not limited to: workflow tool (Visio, SharePoint Designer, Visual Studio), Sequential vs. State Machine, Item vs. Site, Declarative vs. Code, custom actions

Designing SharePoint Solutions and Features (18%)

  • Plan SharePoint Features

    This objective may include but is not limited to: Feature Sets, Feature Stapling, determine feature scope, Create a new Feature (vs. extending), activation dependencies, feature receivers

  • Plan SharePoint solution packaging

    This objective may include but is not limited to: Create a new Solution (vs. extending), Manage reference assemblies in a SharePoint WSP solution, solution sets,  solution dependencies,  solution targeting

  • Establishing application modification and version upgrade strategy

    This objective may include but is not limited to: Designing an artifact upgrade strategy,  Feature and solution upgrade,  Site upgrade,  Versioning custom assemblies,  Versioning workflows (new feature, new assembly version, new code),  Resolving incompatible changes between dev and production

  • Develop a strategy for delivery of application modifications and existing data transformation

    This objective may include but is not limited to: Formulating a new version of custom code,  Updating Web parts while retaining properties, connections and other user entered settings,  Content maintenance, Developing a content upgrade strategy, Deployment configurations, Deploying modified code safely (data safe), Preparing scripts (PowerShell, EXE), packages (WSP, MSI), or installers

Preparation materials published for Exam 70-573: TS: Microsoft SharePoint 2010, Application Development

March 8, 2010 2 comments

On the Microsoft Learning site the prep materials for the 70-573 MCTS exam have been published. It appears that the exam is scheduled to be released June 15 and the exam is still in development.

To see full details visit the Microsoft Learning Center exam description for 70-573

About this Exam

This exam is designed to test the candidate’s knowledge and skills on developing applications on the Microsoft SharePoint Server 2010 platform.

Audience Profile

A Microsoft Certified Technology Specialist (MCTS) in Microsoft SharePoint 2010, Application Development should be able to perform the following tasks:

  • Write code that extends SharePoint 2010
  • Add and support code to an existing project
  • Write code for and test custom features in a SharePoint solution such as a Visual Web Part or Event Receiver
  • Implement a solution designed by lead SharePoint Developer

The candidate should also have the following experience:

  • 12 months with ASP.NET 3.5 with Visual Studio 2008 (or later)
  • 6 months develop with SharePoint 2007 or later
  • 3 months with SP 2010 and VS2010 (includes beta releases)

Credit Toward Certification:

When you pass Exam 70-573: TS: Microsoft SharePoint 2010, Application Development, you complete the requirements for the following certification(s):

TS: SharePoint 2010 Developer

Exam 70-573: TS: Microsoft SharePoint 2010, Application Development: counts as credit toward the following certification(s):PRO: SharePoint Server 2010 Developer

 

Skills Being MeasuredThis exam measures your ability to accomplish the technical tasks listed below.The percentages indicate the relative weight of each major topic area on the exam.

Working with the SharePoint User Interface (19%)

  • Manage SPSite and SPWeb programmatically by using Visual Studio 2010
    This objective may include but is not limited to: creating sub webs, referencing SPFiles, manipulating property bag, when to call Update, referencing SPContext, SPSite, SPWeb,  SPSite.OpenWeb, SPWeb.Webs, feature activiation and deactivation

    This objective does not include: trivial cases such as setting title and other loose properties of the objects

  • Implement a dialog by using the Dialog Framework

    This objective may include but is not limited to: Create dialogs from JavaScript or from server side, display dialogs

  • Create a custom ribbon object

    This objective may include but is not limited to: adding custom actions to the ribbon, customizing groups, customizing tabs, customizing the existing ribbon

  • Customize navigation programmatically
    This objective may include but is not limited to: TopNav bar, quick launch, custom actions

    This objective does not include: custom menu controls, custom site map providers

  • Create and apply branding to a SharePoint site
    This objective may include but is not limited to: applying custom master pages to content pages and application pages, placeholders, page layouts, programmatically working with themes, deploying CSS, CSSlink, ScriptLink

    This objective does not include: graphic design, creating a CSS

Developing Web Parts and Controls (21%)

  • Create Web Parts
    This objective may include but is not limited to: including properties, controls using Render vs. CreateChildControl, life cycle,  visual, standard Web Parts,  

    This objective does not include: trivial case where developer uses Visual Web Part project template

  • Create connectable Web Parts

    This objective may include but is not limited to: Implement consumer/provider interfaces

  • Debug Web Parts

    This objective may include but is not limited to: ULS log, and event log, debug.log tracing, developer dashboard

  • Create and implement delegate controls

    This objective may include but is not limited to: overriding existing controls with lower sequence, developing and using .ascx files

Developing Business Logic (19%)

  • Implement a custom workflow in Visual Studio 2010
    This objective may include but is not limited to: work with inititation data or association data to create a SharePoint task, extend a workflow imported from SharePoint Designer 2010, use a HandleExternalEvent and CallExternalMethod to interact with a custom local service, work with inititation data or association data in a site workflow, corelation token

    This objective does not include: trivial cases such as workflows with no custom actions, initiation data, association data.

  • Create a custom workflow action

    This objective may include but is not limited to: create a custom SPD action, create and add a custom activity to a Visual Studio workflow, define an action.xml file

  • Create and implement event receivers

    This objective may include but is not limited to: accessing event properties, list, item, site, email, avoiding recursion, cancelling events, choosing synchronization state

  • Customize Enterprise Content Management (ECM)
    This objective may include but is not limited to: creating a content type that inherit from appropriate parent, creating and implementing a custom publishing field control that is page mode aware, activating a master page programmatically including token usage

    This objective does not include: page layouts, formatting

  • Create, implement and debug a Timer Job

    This objective may include but is not limited to: configuration, programmatic scheduling, queueing, attaching debugger to the Timer service

  • Create and modify Business Connectivity Service model in Visual Studio 2010

    This objective may include but is not limited to: create a BDC model in Visual Studio 2010, define insert, update and delete methods, create and read items, make data searchable

  • Manage Users, Groups, Permissions

    This objective may include but is not limited to: SPGroups, SPUser, permission inheritance, all securable objects, SPRoleDefinition, SPRole, SPRoleAssignment

Working With SharePoint Data (22%)

  • Access list data by using the Server object model

    This objective may include but is not limited to: SPQuery, LINQ, SPList, SPSiteDataQuery, schema management, working with a query Governor, create LINQ query that includes a join statement, SPQuery Vs. SPSiteDataQuery

  • Access SharePoint Data by using ADO.NET Data Services

    This objective may include but is not limited to: WCF ListData.svc, RESTFUL URLs conventions, create and use a client service reference

  • Access (CRUD) data by using the Client Object Model

    This objective may include but is not limited to: Javascript, .NET, Silverlight, Build Silverlight User Interface for SharePoint using Client Object Model, Query data by using CAML over the Client Object Model in Silverlight, non data API (site, web, list, access)

  • Work with documents programmatically

    This objective may include but is not limited to: SPFile, SPFolder, SPVersion, upload document and set meta data

  • Work with the meta data

    This objective may include but is not limited to: Access data from user profiles, taxonomy, folksonomy

  • Extending SharePoint Search

    This objective may include but is not limited to: creating a custom query using full text query or keyword query, customize the look and feel of the search result using XSLT

  • Implement and debug code that executes in an alternative security context

    This objective may include but is not limited to: create code that uses the RunWithElevatedPrivileges delegate (including debugging), create code that uses the System Account, create code that impersonate a different user

  • Create and modify a custom content type

    This objective may include but is not limited to: declaratively and programmatically creating and upgrading content type using Visual Studio 2010, modifying an exisiting content type, site columns

Stabilizing and Deploying SharePoint Components (19%)

  • Manage a solution in Visual Studio 2010

    This objective may include but is not limited to: modify the contained features in the solution, add an assembly that is not included in the visual studio solution, manage mapped folders for localization, sandbox and farm solutions, customize manifest.xml 

  • Manage a feature by using Visual Studio 2010
    This objective may include but is not limited to: upgrading, localizing, versioning, developing features, feature receivers (activating and installing) that interact with their parent object, customizing feature.xml

    This objective does not include: features without elements

  • Store and retrieve configuration data

    This objective may include but is not limited to:  App config, web config, persisted object, list, xml, file system, cookies, property bag

  • Create a site definition by using Visual Studio 2010
    This objective may include but is not limited to: feature activation, site provisioning, localization

    This objective does not include: list definitions and modules defined in ONET.xml, SharePoint Designer

  • Manage SharePoint object life cycle by using the Dispose API

    This objective may include but is not limited to: SPWeb, SPContext, IDisposable, Try…Catch…Finally, using blocks

  • Develop, debug, and deploy sandboxed solutions

    This objective may include but is not limited to: APIs that are allowed or not allowed in sandbox, use a full trust proxy

Free evaluation of online hosted SharePoint 2010

February 22, 2010 Leave a comment

Here is a free trial to a hosted instance of SharePoint 2010. Try for 90 days and check out the new features of SharePoint 2010 on your own hosted version.

Thanks to ICS Solutions which has this to say about their offering:

Simplifying the evaluation of SharePoint 2010 by providing free and instant online access to a unique, private and customisable beta trial. The portal allows users to share in the same private space without the hassle of installing the beta software locally – saving time, money and IT resources.

The Portal aims to be one of the world’s most comprehensive sources of SharePoint 2010 information with over 600 vetted and categorised items that will assist in your evaluation. 

Dip into SharePoint 2010

http://www.dipintosharepoint2010.co.uk/Pages/default.aspx

SharePoint Developer credit class at DePaul University in Chicago

February 20, 2010 Leave a comment

This looks like a great option to learn SharePoint 2007 and SharePoint 2010 development while earning college credit at a well known University in Chicago.

It is rare to see universities offering classes on very current technologies not to mention offering college credit for a very current version and the future version of SharePoint.

http://www.cdm.depaul.edu/ipd/Programs/Pages/SharePointDeveloperProgram.aspx

Overview
A 10-week comprehensive program covering Microsoft SharePoint development. The program exposes students to SharePoint architecture and the use of SharePoint as a development platform for building customized solutions, focusing on SharePoint as a collaboration framework and content management system.

The program will begin with an overview of the various product editions and their features as well as a refresher of the .NET 2.0+ fundamentals that SharePoint is built upon. The program will then provide in-depth coverage of the core development constructs of SharePoint to enable the student to understand how the pieces fit together in common use cases. Finally, the program will expose the student to current development trends and how they will carry over into the next release of the product, SharePoint 2010.

Admission Requirements
Applicants must have a solid programming background (at least two years of professional experience is preferred), including some experience building dynamic websites using ASP.NET and C#, and knowledge of basic HTML/CSS.

Dates & Location: Spring Quarter 2010
Application deadline: Mar. 12, 2010
Tuition deadline: Mar. 18, 2010
Classes begin: Mar. 30, 2010 
Classes end: Jun. 3, 2010
Classes meet on Tuesday and Thursday evenings (5:45pm-9pm) at DePaul University’s Loop Campus at 243 South Wabash Avenue, Chicago, IL.

Online Section:
Students may elect to register for an online section of the course. For more information about the online section, click here.
DePaul University reserves the right to cancel any program prior to that program’s first class meeting.

Course Credit

The SharePoint Developer Program is an accredited course of DePaul University, which follows the quarter system (as opposed to the semester system).
Course #: IPD 358
Credit hours: 10 undergraduate

For a complete program description, download the program brochure.