SharePoint In Action

An attempt to share my day-to-day SharePoint experience

Archive for the month “May, 2012”

Microsoft Deep Zoom


Let’s have some fun with Microsoft Deep Zoom Composer. It’s one of the fastest, smoothest, zooming technology on the Web, bringing the highest resolution images and frame rates with the lowest load times to users.

Deep Zoom also enables the display of thousands of items simultaneously, giving designers and developers new opportunities to create innovative navigation paradigms for both applications and the Web.

In order to be able to create and use this feature you will need to download “Microsoft Deep Zoom Composer”:

 Here are the steps after downloading this tool:

1) Open Deep Zoom Composer,  create a new project – I have named my project DZ_MugShots

2) Prepare your mug shots – I downloaded 90 images from internet and saved them in a local folder called MugShots

3) Click Add image and import all images from your local image folder.

4) Click Compose and drag all of the images from the Images pane onto the work space.

5) Right click on one of the images and click arrange à align à arrange into a grid

  • I aligned the 90 images into a grid with 5 rows of 18 images.

 6) Click Export pane and set the following settings.

  • Output type: Silverlight Deep Zoom
  • Name: DZ_MugShots
  • Export options: Export as a collection (multiple images)
  • Templates: Deep Zoom Navigation (Default)

7) Click Export

8) The project will create all required files under ….\DZ_MugShots\Exported Data\dz_mugshots

9) Note that the generated XAP file can be easily placed inside a web part and be added to a SharePoint page

10) Click test.html and it will open the generated Silverlight component in browser

Nader Heshmat


SharePoint log files location

Hi,Just as a reminder for SharePoint log files location:

SharePoint 2007
c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS
SharePoint 2010
c:\Program Files\Common Files\Microsoft Shared\web server extensions\14\LOGS

Nader Heshmat

Client Access Policy XML file


I just got an error after publishing my new WCF services to server different from the one that my Silverlight application was residing. Basically the error is caused by cross-domain service call from my Silverlight application. The error was:

“An error occurred while trying to make a request to URI ‘http://(myWCF).svc’. This could be due to attempting to access a service in a cross-domain way without a proper cross-domain policy in place, or a policy that is unsuitable for SOAP services. You may need to contact the owner of the service to publish a cross-domain policy file and to ensure it allows SOAP-related HTTP headers to be sent. This error may also be caused by using internal types in the web service proxy without using the InternalsVisibleToAttribute attribute. Please see the inner exception for more details.”

The solution was that I had to add the Client Access Policy XML file to the root of my site in IIS:


And the content of this file will look like below:

<?xml version=”1.0″ encoding=”utf-8″ ?>
       <allow-from http-request-headers=”*”>
         <domain uri=”*”/>
         <resource path=”/” include-subpaths=”true”/>

 Note that this is only needed if you have your services reside on a different server as you Silverlight application.


“Set As Start Page” In A Silverlight Project

Silverlight projects miss “set as start page” when you right-click on a xaml file.

In order to perform this action you would need to modify the code behind for file App.xaml in your project as below:

private void Application_Startup(object sender, StartupEventArgs e)
       // MyDefault.xaml is your default page 
       this.RootVisual = new MyDefault();

Nader Heshmat

Location of SharePoint Branding CSS files


Here is where you will find SharePoint 2010 CSS files for re-branding your sites:

File Name Location(relative from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14)
Search.css TEMPLATE\LAYOUTS\{Locale-ID}\STYLES\Themable\Search.css
Wiki.css TEMPLATE\LAYOUTS\{Locale-ID}\STYLES\Themable\Wiki.css
Corev4.css TEMPLATE\LAYOUTS\{Locale-ID}\STYLES\Themable\Corev4.css
Controls.css /Style Library/{Language-Culture}/Themable/Core Styles/Controls.css
Page-Layouts-21.css /Style Library/{Language-Culture}/Themable/Core Styles/Page-Layouts-21.css
Nightandday.css /Style Library/{Language-Culture}/Themable/Core Styles/Nighandday.css

** {Language-Culture} is a placeholder for language and culture; for example, en-us. The {Locale-ID} is another placeholder for locale ID; for example, US English is 1033.

Nader Heshmat

Post Navigation