Adrian Mascarenhas' blog

Silverlight Beta2 released.

Adrian Mascarenhas — Mon, 09 Jun 2008 04:33:00 GMT

We just released silverlight beta2. Try it out and send me any feedback you have.

Also, try out the NBC olympics site powered by silverlight. Click on any of the videos and it will launch the silverlight player.

First two weeks.

Adrian Mascarenhas — Mon, 10 Sep 2007 21:30:00 GMT

So far I have completed my first two weeks on the Silverlight team. The transition has been quite hectic but fun:

Managed to Native code. I have been training my eyes and brains to read native code. Looking at managed code for awhile can pamper you quite a bit.
Understanding the technology and terminology around it.
Understanding the platform space. It is different from the tooling space.
The team is bigger. The challenge is figuring out what areas need your attention and what you can ignore.
Office move. My office move from previous office has not yet been done. So, I am living in two offices in two different buildings right now.
Reading blogs for SL, WPF and Expression.
Identifying contacts in the team from dev, test, pm.

Moving on... Silverlight 1.0

Adrian Mascarenhas — Thu, 06 Sep 2007 09:07:00 GMT

After having worked on the Expression Blend tool for some time, I have decided to move on to Silverlight team. It has been fun learning about the tooling story, now its time for me to delve into the platform side of things.

Today, we made some big announcements about Silverlight. We released the Silverlight 1.0 version. I highly encourage you to download it and try it out. This version is centered around a rich media experience and javascript integration.

Feel free to send any feedback my way and I will do my best to pass it on to the right folks in the silverlight team.

Silverlight

Adrian Mascarenhas — Mon, 14 May 2007 04:51:00 GMT

If you are not yet caught up on Silverlight, I highly encourage you to do so. You can download the preview versions of Expression tools that support silverlight from here.

The Customer is always right.

Adrian Mascarenhas — Mon, 22 Jan 2007 08:42:00 GMT

This a well known phrase and I have heard so many times at so many different places. But I got to experience it in a special way this week. As you know, I have been part of a product team known as Blend for nearly 4 years now and we have always been making decisions based on what we think our customers need. But hardly did we get to meet our customers to find out whether we made the right or in some cases wrong decisions.

When I heard of the opportunity to visit one of our customers, I immediatley jumped on it. So, I got to visit a team of designers down in Santa Clara, California, who are actively using Blend to build, oops wrong term, I should say design their UI. I got to meet them, see them use Blend and also help answer any questions they had. While working in their midst, I was thrilled to see how excited they are to use our tool and how empowered they really feel. I also saw some of the areas of the product where we could have done a better job, but ran out of time.

This customer experience made me realize the impact of the decisions we make during the product lifecycle on our customers. The bottom line is that when youare building a product for your customer, the customer is always right. We have to clearly understand their requirements and strive to give them the best possible experience using our tool.

I learnt a lot and took a lot with me back home, including a cold...

eXpression Slides aka XSlides - Bring your presentations to life.

Adrian Mascarenhas — Wed, 17 Jan 2007 10:29:00 GMT

Disclaimer - This is not a professional tool to enhance your presentation experience as the title of the blog post implies. It is merely a couple of hours worth of effort that I and a colleague of mine spent using our tool as our customers would use.

This is an old project that I and Mario had created for one of our app bashes. In case you are wondering, an app bash is one of the myriad of test activites that we do as a team where everyone for a day stops what they are doing and uses Blend as our customers would use. The intent is to create an user application that validates end-to-end customer scenarios. This helps to find bugs and workflow issues.

The vision for XSlides was to enable folks to use the power of WPF to easily create rich, animated presentation slides using xaml and then use our presentation viewer for their presentations. Another key goal, at the time, was to get folks to create their slides in Blend itself. Our future goal was to create an application that would allow you to organize your slides, change the themes et. al. during the presentation, but we did not get to this.

We identified a key Avalon perf issue while building this application and if your run it, you will notice it too. When run in full screen mode, the animations get choppy since they are now being software rendered, but if you minimize it then it uses the full power of hardware acceleration and is much more performant. The perf issue was related to having a visual brush inside a viewport. Unfortunately, this bug did not get fixed in current version of WPF.

We provide a few sample templates for your slides - clouds, ring of light and image animation. You can easily create your own templates by adding it to the resource dictionary. Also, the organization is pretty rudimentary (we just had a few hours to come up with this app). Basically, name your slides sequentially and we will iterate throught them accordingly.

The source code is attached to this post. Feel free to use it and bring your presentations to life!

Here are some snapshots:

Vista!

Adrian Mascarenhas — Mon, 15 Jan 2007 11:53:00 GMT

I have been using only Vista for a while now as my primary OS. I have it on my work laptop and desktop. Also, I do all my coding on Vista. So far, I have to say, I really like it. It has not crashed, the side bar is really cool (especially the stock ticker gadget). The animations and the UI are cool.

The LUA(limited user account) mode can be a little annoying at times with several dialogs to wade through, but I have grown to like it as it tells me exactly what and who is attempting to install anything on my machine and whether I want to go ahead with it or not. It gives me more control on whats on my machine.

Also, the vista perfomance index can help you back your claim for a machine upgrade at work:)

I have not really looked under the hood to know how Vista is an improvement over XP, but so far I just feel a lot better on Vista than on XP.... maybe its just a perception, maybe there is a lot more to Vista than most folks think....

Not in V1, sorry.

Adrian Mascarenhas — Mon, 15 Jan 2007 11:38:00 GMT

Last week, I actively engaged in answering newsgroups posts for Blend. Here are some features not supported for authroing in V1. However, if you create it manually by editing xaml yourself and then load the project in Blend, Blend should be able to handle it just fine. If it crashes, then please let us know and we will try to fix it before RTM.

NavigationWindow: We ran into workflow related issues and decided not to support this for V1. If you want to create a NavigationWindow in your project:

To create a NavigationWindow. In an empty xaml file, paste the following and
point the source to whichever xaml you want in your project, in the example
below it is pointing to Page1.xaml.
<NavigationWindow
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    Title="NavigationWindow Sample"
    Source="Page1.xaml" />

Another simpler way to convert a Window to NavigatinWindow, is to replace the <Window> tags with <NavigationWindow> and wrap the child element of Window with <NavigationWindow.Content> tags.

HierarchicalDataTemplate: Blend should be able to load any hand-created hierarchicaldatatemplates. But you cannot author them for V1. You will have to author them in xaml.

XBAP and Deployment: We tried doing this, but decided to scale back for V1 as we ran into a bunch of implementation and workflow issues.

Code Editng: Here too, we decided to scale back. Given the time we had for V1, we could not put in a code editor that was rich, powerful and well integrated with the rest of our tool. But we did get in good amount of Visual stuido interop code. So, folks can seamlessly modify code with VS and Blend will be able to pick up the changes. To edit code files, just right click on the project item and choose 'edit externally', this will open up VS with the code file. I usually prefer to do an 'edit externally' on the solution itself so that it opens the entire solution in VS instead of just the particular code file.

DataGrid:Blend only supports what is in WPF and unfortunately, there is no DataGrid in WPF. You could implement your own datagrid using ListView. But if you are really bent on using a datagrid, then you can use "crossbow" to use winforms datagrid inside your wpf app. Here is a post that shows you how:http://geekswithblogs.net/lorint/archive/2006/09/09/90740.aspx

Code Duplication- When is a good time to get rid of it?

Adrian Mascarenhas — Mon, 15 Jan 2007 10:52:00 GMT

These last couple of weeks, I have been working on a project that led me to think about the risks of code duplication and when would be a good time to get rid of it. Make no mistake, I completely agree that duplicating code of any sort and any extent is a bad idea right from the beginning. In theory, we should never take that route. But in practice, you may have to walk that path if it is in the best interests of your project.

For instance, in the Expression Suite, we have couple of other products that are still further behind in testing infrastructure than Blend. Blend has a well defined automation model that initally was pretty product agnostic, but in time the law of thermodynamics caught up and product specifics found its way in our code making it more and more harder to clean it up. The reasons why produt specifics went in is another good blog post for a later time. Other products in the suite, came along and adopted our testing infrastructure, by copying over our automation stack. It was the best and least risk path at the time. But now it is a growing problem that is coming to bite us. When we change some test code, we have to update the rest of the copies. So, we decided to fix this problem by creating a core test infrastructure and pulling it all the product agostic code into core. The next step is for each of the products to remove the duplicate code and point it to core instead.

All this sounds good, right? Looks like we are heading in the right direction, right? Unfortunately, we are in the last mile of shipping a product to our customers. Making big changes in the last mile has potential of breaking a lot of things with little time to fix. So, the question, I faced for the last couple of weeks was to clean up or not to. I decided to go ahead and give it a shot. It was a two week long project that involved touching every single file of our test code, porting changes over, working with other product teams to make sure the changes did not have negative impacts on their side, and so on and so forth. The big check in finally went in .... We had some new failures here and then, but as of today, we are pretty much where we were before the checkin. The only change is less code duplication at our end.

Overall, I am super excited to see us maintaining just one code copy. Other teams still have to go this route. I guess they too are battling the question of when is the right time to do the right thing. Sometimes, doing the right thing at the wrong time can backfire. In my case, I just knew that it was a good thing. I had a gut feel and it turned out to be right. To someone reading this post, you need to decide.... what is your gut feel?....what is best for your product?....what is best for the customer?

If you expected answers from me, then I am sorry to have taken so much of your time. I am here to only share my experience with you, the decision is still yours to make....

Bring Your Vision To Reality using Microsoft's Expression Studio

Adrian Mascarenhas — Mon, 11 Dec 2006 07:31:00 GMT

I am super excited to be a part of Microsoft's Expression Studio. We just made a public announcement recently. I am sure you have already heard the buzz around the tools. In case you have not, here is quick recap -

The studio consists of 4 tools:

Expression Blend : Expression Blend is the professional design tool to create engaging, Web-connected, user experiences for Windows.
Expression Design: Expression Design is a professional illustration and graphic design tool that lets you build compelling elements for both Web and desktop application user interfaces.
Expression Web: Expression Web is a professional design tool to create modern, standards-based sites which deliver superior quality on the Web.
Expression Media:Expression Media is a professional asset management tool to visually catalog and organize all your digital assets for effortless retrieval and presentation.

Blend is in Beta, Design is in a CTP (Community Technology Preview), Web and Media also have free trials available.

I work for Expression Blend exclusively and I am excited to see the amazing transformation that the tool has gone through since its previous CTPs, all thanks to the valuable feedback from our customers especially designers. The UI is very sleek and designer friendly. For a more detailed list of the improvements see Unni's post.

I will be posting a bunch of samples that I have been working on in the past couple of months. So, keep posted.