Installing the Silverlight Integration Pack

Retired Content
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
The latest Enterprise Library information can be found at the Enterprise Library site.

On this page:

System Requirements and Prerequisites | Installation Using NuGet and Extension Manager - Installing NuGet into Visual Studio, Adding Enterprise Library Components to Your Application, Database Scripts, Installing the Configuration Console | MSI Installation - Performing a Clean Installation, Upgrading from Enterprise Library 5.0, Upgrading from a Version Earlier than Enterprise Library 5.0 | Installing the Learning Materials - Documentation, Installing the Stock Trader V2 Reference Implementation, QuickStarts, Source Code

There are several ways to install the Enterprise Library Silverlight Integration Pack:

• **Installation of binaries through NuGet.
  **NuGet is a package manager that makes it much easier to add and configure library packages to your projects. The binaries for Enterprise Library 5.0 and the Enterprise Library Silverlight Integration Pack are available for installation through NuGet. You can use the public NuGet repository or use a local NuGet repository.
• **Install configuration console through Extension Manager.
  **Enterprise Library 5.0 also ships with a Visual Studio Extension, that allows you to launch the configuration console from within Visual Studio. You can install this extension though the Extension Manager in Visual Studio. Alternatively, you can download the VSIX package and install it directly.
• Full installation using Microsoft Windows Installer. There are two .msi files that will install all the binaries, the configuration console, and the other support tools needed to use the Enterprise Library 5.0 Silverlight Integration Pack.
• Installation from source. Download the source (either through CodePlex or NuGet) and build it.

These installation options are described further in this chapter.

System Requirements and Prerequisites

To run an application that was built using the Enterprise Library 5.0 Silverlight Integration Pack, you will need the following prerequisites:

• Silverlight 4.0 or Silverlight 5.0 (Beta).
• A Silverlight 4.0-supported browser and platform. The supported browsers and platforms are described on this page: https://www.microsoft.com/silverlight/faq.

For Remote Logging Service of the Logging Application Block, the following are also required:

• Microsoft .NET Framework 3.5 with Service Pack 1 or Microsoft .NET Framework 4.0.
• Logging Application Block of Microsoft Enterprise Library 5.0 Optional Update 1.

For WCF RIA Services Validation Integration or WCF Data Services Integration, the following are required:

• Microsoft .NET Framework 4.0.
• Validation Application Block of Microsoft Enterprise Library 5.0 Optional Update 1.

These are the minimum system requirements for Enterprise Library 5.0 Optional Update 1:

• Supported architectures: x86, x64.
• Operating system: Microsoft Windows® 7 Professional, Enterprise or Ultimate; Windows Server® 2003 R2; Windows Server 2008 with Service Pack 2; Windows Server 2008 R2; Windows Vista® with Service Pack 2; or Windows XP with Service Pack 3.
• Microsoft .NET Framework 3.5 with Service Pack 1 or Microsoft .NET Framework 4.0.

For a rich development environment, the following are recommended:

• Microsoft Visual Studio® development system 2010 SP1 (any edition).
• Silverlight 4.0 Tools for Visual Studio® 2010.

To run the Enterprise Library unit tests, you will also need:

• Visual Studio 2010 Premium, Visual Studio 2010 Professional, or Visual Studio 2010 Ultimate edition.

Moq v4.0 assemblies.

To use the Stock Trader reference implementation, you will also need the following items installed:

Microsoft SQL Server 2008 Express.

Installation Using NuGet and Extension Manager

Enterprise Library is now available via NuGet to install and update references to libraries in your projects. All Enterprise Library 5.0 components have been added as NuGet packages. The diagram below illustrates the Enterprise Library NuGet Package dependencies.

Note

NuGet is a free, open source developer-focused package management system for the .NET platform intent on simplifying the process of incorporating third party libraries into a .NET application during development. It helps you to quickly add references to .NET libraries such as Enterprise Library.

NuGet provides a great experience for adding references to Enterprise Library binaries to your project. For example, if you wish to apply the Enterprise Library Caching block, you can simply select and install the caching block from the NuGet Library Manager. It will automatically download and install the component and all of its dependencies, such as the Microsoft.Practices.EnterpriseLibrary.Common and the Microsoft.Practices.Unity assemblies.

For the assemblies that have both a Silverlight and a .NET Framework version, the packages will contain both versions (denoted in blue in the diagram). However, NuGet takes into account the type of project you are trying to add a reference to. If you have a Silverlight project selected, it will only add a reference to the Silverlight project, but if you have a .NET Framework project selected, then it will only add the reference to the .NET Framework project.

For example, when you download the Enterprise Library 5.0 Validation Application Block, it will download both the Silverlight and .NET Framework assemblies. If you try to add that reference to a Silverlight project, then only the reference to the Silverlight project will be added. For the Data Access Application Block, which is only available for the .NET Framework, the package will only contain the .NET Framework assembly. If you try to add the Data Access Application Block to a Silverlight project, you will get an error message.

Ed Says:
	The NuGet packages do not contain the configuration console or any of the other tools. If you wish to use the configuration console, you can use the Extension Manager to download it. Any other tool, such as the MSMQDistributor, mergeconfiguration.exe, or installutilities.bat can only be obtained by installing the complete MSI.</td>

Installing NuGet into Visual Studio

To install NuGet into Visual Studio, perform the following steps:

1. Start Visual Studio 2010.

2. Go to Tools -> Extension Manager.

3. From the left menu, select Online Gallery.****

4. In the search box, type NuGet and wait for the list to filter.

   

5. Select Download on the NuGet Package Manager.

6. Read the license agreement and if you agree, click Install.

7. Restart Visual Studio.

Adding Enterprise Library Components to Your Application

To add an Enterprise Library component to your application, perform the following steps:

1. Right click your project and select Add Library Package Reference.****

2. From the left menu, select Online. If you are using a local repository, point to that feed.

3. In the search box, type Enterprise Library and wait for the list to filter.

   

4. Select the block you wish to add and click Install.

NuGet will now download the required dependencies and store them in your solution folder under the folder named packages. When you install a NuGet package, it will also register the location of the binaries as a solution property, which is needed by the configuration console.

Database Scripts

There are two NuGet packages for Enterprise Library 5.0 Optional Update 1, that also contain database scripts. These are EnterpriseLibrary.Caching.Database and EnterpriseLibrary.Logging.Database. Once you have installed these packages, you can find the files in the following locations, relative to your solution file:

• /Packages/EnterpriseLibrary.Caching.Database 5.0.505.0/Scripts/CreateCachingDatabase.sql
• /Packages/EnterpriseLibrary.Logging.Database 5.0.505.0/Scripts/CreateLoggingDatabase.sql

Installing the Configuration Console

The configuration console can be installed from the extension manager:

1. Start Visual Studio 2010.

2. Go to Tools -> Extension Manager.

3. From the left menu, select Online Gallery.

4. In the search box, type Enterprise Library and wait for the list to filter.

   

5. Select Download on the EnterpriseLibrary.Config item.

6. Read the license agreement and if you agree, Click Install.

7. Restart Visual Studio.

Alternatively, you can download the Visual Studio Extension package (.vsix) and install it.

The configuration console is now available when you right click a .config file. You can choose Edit Server Configuration, which will start the configuration console in the desktop profile. You can also choose Edit Silverlight configuration file on .config files other than Web.config, which will start the configuration console in the Silverlight profile.

MSI Installation

If you don’t wish to use NuGet install Enterprise Library, then you can also install Enterprise Library 5.0 Optional Update 1 and the Enterprise Library Silverlight Integration Pack using an MSI.

The installer for Enterprise Library 5.0 Optional Update 1 contains the updated versions of Enterprise Library 5.0 assemblies and the updated configuration console.

The installer for the Enterprise Library 5.0 Silverlight Integration Pack contains the binaries for Silverlight and the design time components for the configuration console.

Performing a Clean Installation

If you do not have Enterprise Library installed, then you can perform a clean installation. To do this, you will have to install the following MSI’s:

• Enterprise Library 5.0 Optional Update 1.msi
• Enterprise Library 5.0 Silverlight Integration Pack.msi

Upgrading from Enterprise Library 5.0

If you have Enterprise Library 5.0 already installed, then you have two options for continuing:

1. Uninstall Enterprise Library 5.0 and then execute a clean installation.
2. Upgrade Enterprise Library 5.0 to Optional Update 1 from the command prompt, then install the Enterprise Library 5.0 Silverlight Integration Pack.msi

To upgrade Enterprise Library 5.0 to Optional Update 1 from the command prompt, you can perform the following steps:

1. Rename the Enterprise Library 5.0 Optional Update 1.msi file to Enterprise Library 5.0.msi.

2. Execute this command from the command prompt:

   msiexec /i "Enterprise Library 5.0.msi" REINSTALLMODE=vomus REINSTALL=ALL
   

1. This command will update your existing installation of Enterprise Library to Optional Update 1.

Upgrading from a Version Earlier than Enterprise Library 5.0

Enterprise Library 5.0 introduced many improvements over previous versions of Enterprise Library. It did however, introduce a couple of breaking changes. If you are currently using a version of Enterprise Library older than 5.0, we recommend that you use the Migration Guide to help you to upgrade to the latest version of Enterprise Library 5.0.

Installing the Learning Materials

The Enterprise Library 5.0 Silverlight Integration Pack ships with several learning materials:

• Documentation
• Stock Trader V2 Reference Implementation
• Quick Starts

Documentation

This guide and the API Reference are available for download from: https://go.microsoft.com/fwlink/?LinkID=217989

Installing the Stock Trader V2 Reference Implementation

The Stock Trader V2 reference implementation is available as a separate download.

To run the Stock Trader V2, perform the following steps:

1. Ensure you have the required pre-requisites installed.
2. Download the zip archive from CodePlex.
3. Extract the source code.
4. Open the StockTraderRI.sln using Visual Studio 2010.
5. Ensure the project StockTraderRI.Web is set as your startup project.
6. Press F5 to compile and run the Stock Trader V2.

QuickStarts

The Enterprise Library 5.0 Silverlight Integration Pack ships with the following QuickStart:

• WCF Data Services QuickStart

Source Code

The Source Code for Enterprise Library is available from NuGet or CodePlex. You can download the source code either as a zip file, or use one of the many supported source control clients to retrieve the source code.

The source code can be used to learn how Enterprise Library works, to use as a basis for custom extensions, or to create a custom signed version for Enterprise Library.

Next Topic | Previous Topic | Home

Last built: July 8, 2011