Ezequiel Jadib

Live Smooth Streaming: How-to: Retrieve the configuration settings programmatically

2009-04-20T10:41:00Z

In my previous post, I explained how the Microsoft.Web.Administration API of IIS7 helped us to manage the Live Smooth Streaming Publishing Points programmatically. In this post I'm going to show you how, using the same API, you can retrieve the Live Smooth Streaming configuration settings.

Read the full article

Live Smooth Streaming: How-to: Start, Stop & Shutdown a Publishing Point Programmatically

2009-04-17T00:13:00Z

During the last months I have been working in a project highly related to multimedia and client development technologies such as Silverlight. And in the last few weeks, I started to look to some of the new IIS Media services such as Smooth Streaming and Live Smooth Streaming in order to gather as much knowledge about them to perform some spikes for the project.

One of the things that came up while spiking was finding a way to start, stop & shutdown a publishing point via code.

Read the full article

New Samples in CompositeWPF (Prism) Contrib (2008-09-13)

2008-09-13T20:38:15Z

Four new samples has been added to the CompositeWPF Contrib community project:

Read the full article

Silverlight & Composite Application Guidance (Prism): Spike published

2008-08-06T19:10:29Z

Weeks ago we shipped the Composite Application Guidance for WPF and with the Prism team we started to spike around the migration of the Composite Application Library to Silverlight 2 Beta 2. The good news is that yesterday we published that spike. (A ’spike’ is a small and quickly developed sample application in order to mitigate some risks).

After downloading and decompressing the latest change set of the source control, you will find a new folder named spikes that contains the Composite Application Library migrated to Silverlight. As you may imagine, there were many challenges that we had to address in order to make it “work” (Rob Eisenberg wrote two articles describing differences between WPF and Silverlight that you might want to check: There’s some darkness in your silver light and Silverlight Problems That Affect Me).

Note: The migration is not complete, we used the spike to have a perspective of the challenges.

Read the full article

CompositeWPF (Prism) Contrib Latest Additions (2008-07-26)

2008-07-26T20:40:15Z

These are the latest extensions added to the CompositeWPF Contrib community project:

Read the full article.

Use the OutlookBar in your CompositeWPF (Prism) Applications

2008-07-22T00:22:47Z

Two years ago, together with Matias Woloski we wrote the Outlook Bar for the Composite Application Block (CAB). I can say that it was a popular workspace, with more than 19,000 downloads!. Now that we shipped CompositeWPF (Prism), some people at the CompositeWPF community started asking for the OutlookBar for CompositeWPF, so Julian Dominguez, Matias Woloski and me decided to spend some time and create the Composite WPF version.

Read the full article.

CompositeWPF (Prism) Contrib Latest Additions

2008-07-12T18:07:38Z

A week ago we shipped the Composite Application Guidance for WPF and many people (including me) started to contribute in the CompositeWPF Contrib community project and to play with the guidance.

Let’s explore the latest additions added to the CompositeWPF Contrib project.

Read the full article.

How-to: Fix the ‘The “ValidateXAML” task failed unexpectedly’ error after installing Microsoft Silverlight Tools Beta 2

2008-07-09T14:51:52Z

Last week I've installed Microsoft Silverlight Tools 2 Beta 2 on my laptop to start developing applications for Silverlight 2 Beta 2.

Once the installation finish, I created a Silverlight Application just to see if everything works as expected. The application was successfully created but when I tried to build and run the solution, I faced with the following error:

Read the full article.

Composite Application Guidance for WPF Visual Studio Templates

2008-07-03T16:56:06Z

As you may know, in the June 2008 release of the Composite Application Guidance for WPF we are not shipping a guidance package. So, I created two Visual Studio Templates to help you to start with the creation of a solution using the Composite Application Guidance for WPF.

Composite Application Guidance for WPF (Prism) June 2008 Released

2008-07-03T16:00:54Z

I’m proud to announce that we have just released the Composite Application Guidance for WPF. I want to thank to the Composite WPF Team. It was really great being part of this release.

Let’s see what this release is about.

Composite Application Guidance for WPF (Prism) Release Candidate Published

2008-06-30T12:58:55Z

Last Friday, we published the release candidate version of the Composite Application Guidance for WPF (formerly known as Prism). In this release you will find a Reference Implementation, a Hands on-Lab, several spikes we did, some QuickStarts, the Composite Application Library and documentation.

Prism: New drop published

2008-06-03T18:39:42Z

A new drop of Prism has been published last Thursday. Among other things, in this drop we refactored the Bootstrapper by extracting common functionality into a base class named UnityPrismBootstrapper located in the Prism.UnityContainerAdapter project.

Smart Client Software Factory (SCSF) April 2008 for Visual Studio 2008 Released

2008-04-26T17:08:57Z

After publishing an alpha version, a beta version and a RC 1 version I'm glad to announce that the final version of Smart Client Software Factory for Visual Studio 2008 has been published on MSDN.

What is new in this release?

The April 2008 release of Smart Client Software Factory includes support for Visual Studio 2008 and .NET Framework 3.5. This release does not support Visual Studio 2005.
April 2008 Guidance Package can run side-by-side with May 2007 Guidance Package.
The April 2008 release requires Guidance Automation Extensions 1.4.
Support for Enterprise Library 3.1.
We fixed a few bugs that were identified by the community. These are some of the bugs fixed:

How to enable a May 2007 solution

If you have a May 2007 solution and you want to enable it to use this new guidance please read this page.

Known Issues

In this page you will find the list of known issues that exists in Smart Client Software Factory - April 2008.

Downloads

Smart Client Software Factory - April 2008

Smart Client Software Factory Source Code - April 2008

Smart Client Software Factory Documentation - April 2008 (CHM format)

Documentation

Documentation on MSDN (HTML format)

Feedback

Feel free to give us your feedback on the discussion board. If you see issues, please post them to the Issue Tracker.

More Information of this release

For more information about this new release please read Blaine's post and Michael's post.

Enjoy this new guidance.

Crossposting from here

Prism How-To: Provide metadata to a view that was placed into a region

2008-04-24T17:02:17Z

If you downloaded our fourth drop probably you may have noticed that we have removed the IMetadataInfo and IMetadataInfoProvider classes. (See Julian's post for more info about this change).

In the Prism Forum some people are asking how to provide metadata to the view now that the IMetadataInfo class has been removed, so in this post I will explain how to do it.

Imagine that you have a TabRegion named MainRegion in your Shell and you want to add a view to it.

 <TabControl Name="Tab" Prism:RegionManager.Region="MainRegion">

After you do this

regionManagerService.GetRegion("MainRegion").Add(new View())

you will see something like the following picture

Looks good, but... we don't have a header, so let's see how to do it

Create a HeaderModel class

namespace PrismTabHeader
{
    using System.Windows;

    public class HeaderModel : DependencyObject
    {
        public static readonly DependencyProperty HeaderInfoProperty =
            DependencyProperty.Register("HeaderInfo", typeof(string), typeof(HeaderModel));

        public string HeaderInfo
        {
            get { return (string)GetValue(HeaderInfoProperty); }
            set { SetValue(HeaderInfoProperty, value); }
        }
    }
}

This class contains a HeaderInfo dependency property.

Update the view by adding the Model property.

public HeaderModel Model
{
    get { return DataContext as HeaderModel; }
    set { DataContext = value; }
}

Create a new style named HeaderStyle in the Shell.

<Window.Resources>
  <Style TargetType="{x:Type TabItem}" x:Key="HeaderStyle">
     <Setter Property="Header" Value="{Binding RelativeSource={RelativeSource Self}, Path=Content.DataContext.HeaderInfo}" />
  </Style>
</Window.Resources>
This style is going to be applied to TabItem elements and is saying that the value of the property Header is going to binded to Content.DataContext.HeaderInfo where Content is the view.

Note: You can also expose a HeaderInfo property in the view and change the binding path to Content.HeaderInfo.

Replace the TabControl definition of your Shell with the following code

<TabControl Name="Tab" Prism:RegionManager.Region="MainRegion" ItemContainerStyle="{StaticResource HeaderStyle}" />
As you may see we are setting the ItemContainerStyle dependency property to affect the appearance of the elements that contain the data items. In this case, the style is going to be applied to all TabItem elements within the scope the style is defined in.

Set the Model to the view before adding it to the region

View view = new View();

view.Model = new HeaderModel() { HeaderInfo = "My Header" };
 
region.Add(view);

If you run now the application you will see the header.

Hope this helps.

Crossposting from here

Page Flow Guidance Package Shipped

2008-04-22T23:20:37Z

As Glenn mentioned we published a new Page Flow Guidance Package in WCSF Contrib.

What's in the new PageFlow?

New stand alone PageFlow guidance package that works on Visual Studio 2008. This guidance package does not require WCSF
New XmlPageFlowProvider that does not depend on Windows Workflow Foundation
Migrated PageFlowWithShoppingCart Quickstarts to Visual Studio 2008
Updated Dependencies to GAT/GAX 1.4

You can get the bits here.

Note: We are not shipping the documentation in this release because we are still working on it.

Crossposting from here