A look at the Printing API in Silverlight

A look at the Printing API in Silverlight: This article is compatible with the latest version of Silverlight.
With the addition of the much anticipated Printing API, Silverlight continues to round out its feature set. Although beta, it’s very flexible enabling you to print what you see on screen, selected portions of the UI, custom “print-friendly” views, and multiple page printing.
This post takes a deep dive into the Printing API, starting out with a simple scenario and moving to the more complex.

How do I print a page/ data grids in Silverlight 4. : The Official Microsoft Silverlight.NET Forums

How do I print a page/ data grids in Silverlight 4. : The Official Microsoft Silverlight.NET Forums: Re: How do I print a page/ data grids in Silverlight 4.
Aug 11, 2010 06:22 PM | LINK
http://channel9.msdn.com/learn/courses/Silverlight4/SL4BusinessModule6/SL4LOB_06_01_Printing/
http://channel9.msdn.com/learn/courses/Silverlight4/SL4BusinessModule6/SL4LOB_06_02_MultipagePrinting/
http://www.davidpoll.com/2010/04/16/making-printing-easier-in-silverlight-4/

Adding Script into a Content Editor Web Part (CEWP) in SharePoint 2010 » Marc D Anderson's Blog; upload file extention validation.

Adding Script into a Content Editor Web Part (CEWP) in SharePoint 2010 » Marc D Anderson's Blog: Adding Script into a Content Editor Web Part (CEWP) in SharePoint 2010

I've a requirement to validate the file extention (.xml) when its being uploaded to the docuemnt library.
Sol:
1) Follow the above steps to add teh CEWP to the page
2) Add the following javascript to the CEWP

return true;
}

Internet Explorer Gallery

Internet Explorer Gallery: Internet Explorer Gallery
Add-ons

Manage RBS (SharePoint Server 2010)

Manage RBS (SharePoint Server 2010): Manage RBS (SharePoint Server 2010)

Published: May 12, 2010

Remote BLOB Storage (RBS) is an add-on feature pack for Microsoft SQL Server 2008. RBS is designed to move the storage of binary large objects (BLOBs) from database servers to commodity storage solutions. If the content databases in Microsoft SharePoint Server 2010 are 4 gigabytes (GB) or larger, consider using RBS as part of your data storage solution.
In This Section

* Overview of RBS (SharePoint Server 2010)

This article is a conceptual overview of how RBS works with Microsoft SQL Server 2008 Express and Microsoft SQL Server 2008 R2 Express. It contains important information about RBS features and providers. We strongly recommend that you read this article before you implement RBS.

* Install and configure RBS (SharePoint Server 2010)

This article describes how to install and configure RBS and implement the FILESTREAM provider for use with SharePoint Server 2010.

* Install and configure RBS with a 3rd party provider (SharePoint Server 2010)

This article describes how to install and configure RBS without using the FILESTREAM provider.

* Set a content database to use RBS (SharePoint Server 2010)

This article describes how to set a content database to use RBS. You must already have RBS installed to perform these procedures.

* Migrate content into or out of RBS (SharePoint Server 2010)

This article describes how to migrate content into or out of RBS, or to a different RBS provider.

* Disable RBS on a content database (SharePoint Server 2010)

This article describes how to disable RBS in a SharePoint Server 2010 environment.

- Sent using Google Toolbar

Creating SharePoint Server 2010 External Content Type Associations Using SharePoint Designer 2010

Creating SharePoint Server 2010 External Content Type Associations Using SharePoint Designer 2010: Creating SharePoint Server 2010 External Content Type Associations Using SharePoint Designer 2010
SharePoint 2010

Published: June 2010

Summary: Learn how to use Microsoft Business Connectivity Services (BCS) to create associations between external content types in Microsoft SharePoint Designer 2010 without using code.

Applies to: Microsoft SharePoint Server 2010 | Microsoft SharePoint Designer 2010

Provided by: Russell Palmer, Microsoft Corporation | Goksel Genc, Microsoft Corporation

Contents

* Introduction

* Supported Associations Using SharePoint Designer 2010

* Unsupported Associations Using SharePoint Designer 2010

* Creating a Database-Based External Content Type Association

* Creating a Reverse Association

* Creating External Content Type Associations Based on WCF

* Conclusion

* Additional Resources

- Sent using Google Toolbar

PRO: Designing and Developing Microsoft SharePoint 2010 Applications

PRO: Designing and Developing Microsoft SharePoint 2010 Applications: Exam 70-576:
PRO: Designing and Developing Microsoft SharePoint 2010 Applications
Published: July 12, 2010
Language(s): English
Audience(s): Developers
Technology: Microsoft SharePoint Server 2010
Type: Proctored Exam

* Overview
* Skills Measured
* Preparation Materials
* Community

Preparing for an Exam
The Microsoft Certification website and this preparation guide contain a variety of resources to help you prepare for an exam. Preparing for and Taking an Exam — FAQ provides answers to frequently asked questions about exam registration, preparation, scoring, and policies, including:

* The most effective way to prepare to take an exam.
* The relationship between Microsoft training materials and exam content.
* Microsoft policy concerning the incorporation of service pack and revision updates into exam content.
* Exam question types and formats.
* Exam time limits and number of questions asked.

We recommend that you review this preparation guide in its entirety and familiarize yourself with the FAQs and resources on the Microsoft Certification website before you schedule your exam.
Exam Topics Covered
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 CertificationExam 70-576: PRO: Designing and Developing Microsoft SharePoint 2010 Applications: counts as credit toward the following certification(s):
MCPD: SharePoint Developer 2010
Note This preparation guide is subject to change at any time without prior notice and at the sole discretion of Microsoft. Microsoft exams might include adaptive testing technology and simulation items. Microsoft does not identify the format in which exams are presented. Please use this preparation guide to prepare for the exam, regardless of its format.
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.The higher the percentage, the more questions you are likely to see on that content area on the exam.

The information after “This objective may include but is not limited to” is intended to further define or scope the objective by describing the types of skills and topics that may be tested for the objective. However, it is not an exhaustive list of skills and topics that could be included on the exam for a given skill area. You may be tested on other skills and topics related to the objective that are not explicitly listed here.
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

- Sent using Google Toolbar

Using FILESTREAM with Other SQL Server Features

Using FILESTREAM with Other SQL Server Features: Using FILESTREAM with Other SQL Server Features

Because FILESTREAM data is in the file system, this topic provides some considerations, guidelines, and limitations for using FILESTREAM with the following features in SQL Server:

*

Database Snapshots
*

Replication
*

Log Shipping
*

Database Mirroring
*

Full-Text
*

Failover Clustering
*

SQL Server Express

- Sent using Google Toolbar

Plan the Secure Store Service (SharePoint Server 2010)

Plan the Secure Store Service (SharePoint Server 2010): Plan the Secure Store Service (SharePoint Server 2010)

Updated: September 7, 2011

In Microsoft SharePoint Server 2010, the Secure Store Service replaces the single sign-on (SSO) feature of Microsoft Office SharePoint Server 2007. The Secure Store Service is a claims-aware authorization service that includes a secure database for storing credentials.

In this article:

* About the Secure Store Service

* Secure store service preparation

* Target applications

* Secure store service mappings

* Secure store service and claims authentication

- Sent using Google Toolbar

What's new in Silverlight 5: Silverlight.NET

What's new in Silverlight 5: Silverlight.NET: Silverlight 5 Release Overview

December 8, 2011|Level 200 : Novice

In this video, Pete provides an overview of the new and updated features in the release of Silverlight 5. Here's the related Silverlight 5 launch blog post on Pete's blog.

- Sent using Google Toolbar

Exercise 3: Creating InfoPath forms

Exercise 3: Creating InfoPath forms: Exercise 3: Creating InfoPath forms

The last task that you will perform is modifying the edit and display forms used by the New Toy Ideas list. SharePoint 2010 allows forms to be easily customized by Information Workers using InfoPath.

1. In SharePoint Designer 2010, navigate to the list overview page for the New Toy Ideas list by selecting the Lists and Libraries choice in the Site Objects List box (on the left side of the screen). Next select the New Toy Ideas hyperlink located under the Lists heading on the center of the screen.
2. On the ribbon, in List Settings tab, expand Design Forms in InfoPath and choose Item. InfoPath will open with a generated form.
3. Modify the labels to display descriptive texts instead of just the field name. You will do this by replacing the existing labels (on the left side of the list below) with the text on the right side (after the colon).

- Sent using Google Toolbar

Create a publishing page layout - SharePoint Designer - Office.com

Create a publishing page layout - SharePoint Designer - Office.com: This article explains what page layouts are and how they relate to publishing pages, master pages, and content types. This article also shows you how to create a page layout content type and a page layout, as well as how to use the browser to create a new publishing page that is based on your new page layout.

Important In order for you to create a publishing page layout, your site must be located on a server running Microsoft Office SharePoint Server 2007, and publishing must be turned on in the top-level site of the site collection. Also, to create content types, you must have authoring permissions for that top-level site. If you find that you are unable to create a page layout, contact your server administrator.

- Sent using Google Toolbar

Querying SharePoint List Items using jQuery - Jan Tielens' Bloggings

Querying SharePoint List Items using jQuery - Jan Tielens' Bloggings: Querying SharePoint List Items using jQuery

Due to popular demand I’ve created another sample of how you can make use of the jQuery Javascript library in your SharePoint sites. This example uses SharePoint’s Lists.asmx web service to retrieve all the list items of a specific list. In my previous posts I showed how you could use jQuery in SharePoint Site Pages (regular .aspx pages uploaded to a Document Library), so let’s do something different now; let’s use jQuery in a plain Content Editor Web Part.

To try this sample navigate to the home page (usually /default.aspx) of a SharePoint site that has a list with some list items in it, in my code I’ll use the Task list of a plain vanilla Team Site. Switch the page to Edit mode (Site Actions, Edit Page), and add a new instance of the Content Editor Web Part to the page. In the properties of that web part, copy and paste the following code using the Source Editor button.

- Sent using Google Toolbar

HTML – jQuery (MVC) vs Silverlight « BugKiller – A Web Development based knowledge sharing initiative.

HTML – jQuery (MVC) vs Silverlight « BugKiller – A Web Development based knowledge sharing initiative.: HTML – jQuery (MVC) vs Silverlight

- Sent using Google Toolbar

Hiding fields on NewForm.aspx and EditForm.aspx

First open entry form (NewForm.aspx / EditForm.aspx / DispForm.aspx) in advanced mode in sharepoint designer. Then search for tag :



Now copy & paste this JavaScript code after this tag :