Your resource quota is 300 server resources

AvePoint Introduces Free Tool for SharePoint BLOB Management

Technical Advantages of DocAve Extender

Comprehensive Support:

DocAve Extender leverages Microsoft’s BLOB APIs to securely offload Binary Large Objects with full fidelity to tiered storage. No metadata is lost when content is transitioned to file-based storage.

Full-Featured Management of Content:

Content offloaded to file-based storage with DocAve Extender can be managed using all of SharePoint’s management and collaboration tools, including versioning, workflows, and alerts, all as if it was residing directly in SharePoint’s SQL database.

Administrator-defined Rules for Automatic Off-load Based Upon File Size:

Determine what BLOB files are transferred to file-based storage by file size. DocAve Extender will automatically analyze all content attempting upload and transfer it to the appropriate storage resource.

Transfer Content to any Network File Shares, FTP system, or Cloud Storage System:

Offload to any network addressable file share, File Transfer Protocol system, or cloud-based storage system (including Rackspace, Amazon, and Microsoft).

Seamless Integration with SharePoint Search:

All data residing in file-based storage is fully integrated with SharePoint’s native, full text search functionality, as well as all other search tools that leverage the standard SharePoint API.

Comprehensive Support for Custom Metadata and Column Types:

All content transferred to file-based storage via DocAve Extender can be associated with all of SharePoint’s standard and customized metadata fields, and appended with any variety of column types.

Integrated Permissions Management:

Securities and permissions for content residing in file-based storage are fully integrated with SharePoint’s permissions management. Both unique and inherited permissions can be delegated to extended content as if it were residing directly in SharePoint’s SQL database.

Total Interactivity with Client Office Applications and Third-party Tools:

Extended content can be presented and modified directly through Office applications, or acted upon by third-party tools, just as if the content resided in SharePoint’s SQL database.

How To Download the Free DocAve Extender

AvePoint’s DocAve Extender will be available for download free of charge from the AvePoint website (www.avepoint.com/download) on March 11, 2010. After downloading the free, fully enabled 30-day trial of the full DocAve Software Platform, North American based organizations that wish to continue using DocAve Extender can call AvePoint at 1-800-661-6588 or email Sales@avepoint.com to receive their perpetual license for DocAve Extender.

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

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

Updated: 2009-11-12

[This article is pre-release documentation and is subject to change in future releases.]

Managed metadata is a hierarchical collection of centrally managed terms that you can define and then use as attributes for items in Microsoft SharePoint Server 2010.

The first articles in this chapter explain key concepts about managed metadata in SharePoint Server 2010. Additional articles in the chapter provide guidance about how to identify managed metadata for your solution, and how to determine the services and connections that you will need to implement your solution. The articles include:

• Managed metadata overview (SharePoint Server 2010)
  This article introduces the core concepts about managed metadata and then describes the way you use managed metadata. The final section presents several benefits of incorporating managed metadata into your SharePoint Server 2010 solution.
• Managed metadata service application overview (SharePoint Server 2010)
  This article describes the managed metadata service and connections and provides an example scenario for using them.
• Managed metadata roles (SharePoint Server 2010)
  This article defines user roles and identifies the actions that members of each role can perform.
• Plan terms and term sets (SharePoint Server 2010)
  This article provides guidance about how you can identify information that should become terms and term sets.
• Plan to import managed metadata (SharePoint Server 2010)
  This article explains how to locate existing terms and term sets and prepare them to be imported into SharePoint Server 2010.
• Plan to share terminology and content types (SharePoint Server 2010)
  This article contains procedures for identifying the managed metadata services and connections that your SharePoint Server 2010 solution requires.

Use this workbook as you plan your upgrade process to ensure that you have all the information that you need before you begin.

Fill out each worksheet in this workbook to get a complete understanding of the servers, services, Web applications, sites, and customizations in your environment. Some of this information is generated for you when you run the pre-upgrade checker tool and can be copied from the XML report that the tool generates. You can also gather information by using the Stsadm -o enumallwebs command. These tools have been updated to include additional functionality in the October 2009 Cumulative Update (such as which sites use a feature and information about large lists).

After running these tools, you will have a preliminary list of the components in your environment. When you perform a trial upgrade, you can verify that you have a complete list of the components.

When you perform your actual upgrade, you can use this workbook as a checklist to verify that you have upgraded all the components in your environment. You can also add to this workbook if you have additional post-upgrade tasks to perform (such as identifying missing server files or following up on sites that were not upgraded correctly).

Link to the .xls on the Microsoft Download Center

The cloud is getting crowded.
Google just purchased a Microsoft Azure and Live SkyDrive competitor.
In Office 2010 there is the ability to save your work to your Live SkyDrive account.

Google purchased DocVerse that allows for saving to online storage, multiple simultaneous editing, versioning, and a URL to the document that doesn’t change throughout the life of the editing process.

Honestly, it looks like what Groove was supposed to be except it is online.

Here are some of the features.

Check out the live event where Stephen Elop will announce the launch of Office 2010 and SharePoint 2010 on May 12, 2010 at 11 a.m. EST.

Check out the official announcement

The live keynote focuses on the next wave of productivity that delivers:

• End user productivity across the PC, phone and browser
• IT choice and flexibility
• A platform for developers to build innovative solutions

Join the virtual launch event with Microsoft executives, product developers, partners and customers to:

• Find out how peers and partners are already seeing benefits to their business by leveraging the next wave of productivity.
• Submit your questions through live Q&A.
• Participate via blogs, tweets, social media networks, commenting, and more.

View on-demand breakout sessions showing how Office 2010 and SharePoint 2010 meet the unique challenges people and businesses are faced with today, and provide the solutions they need for tomorrow.

Get the Flash Player to see this content.

For those of you that are members of the TAP program or the RDP then there is a new patch available.

Why am I posting this if it is only for TAP or RDP users? It is a sign that Microsoft is getting closer to release and items are being added and fixed as you read this.

Here is the official word from Microsoft:

“We have just released a new cumulative patch for customers running Release Candidate (RC) of our 2010 server products. This patch contains all the fixes made since the Release Candidate including several fixes for performance, reliability, and Profile Import functionality. We strongly recommend all customers install this patch. It is not required, but will be the first step we take in patching earlier builds.

NOTE: This patch applies to SharePoint Server 2010, SharePoint Foundation 2010, Project Server 2010.

Please install this patch from this location and review the installation notes posted on Microsoft Connect.

All post-RC patches are cumulative and all will be supported as the starting point in the final upgrade to the RTM build. For any issues, questions or feedback on this patch, please use the Connect feedback tool, to provide your feedback. We have also updated our SharePoint 2010 Beta to RC Upgrade document, which you can also find the latest copy here.”

Here is a great presentation from CriticalPath Training outlining the SharePoint 2010 Developer Roadmap and PowerShell Integration.

The presenter is Ted Pattison.

Get the Flash Player to see this content.