lunes 9 de junio de 2008

Silverlight Tools Beta 2 for Visual Studio 2008 Released!

Silverlight Beta 2 has been released, a release very expected by the community.

Here is available for download:

http://www.microsoft.com/downloads/details.aspx?FamilyId=50A9EC01-267B-4521-B7D7-C0DBA8866434&displaylang=en

Also , there is a new release of Blend 2.5 that supports authoring
Silverlight 2 Beta 2 projects. It also works with .Net Framework 3.5 SP 1 beta runtime. Here is available for download:

http://expression.microsoft.com/en-us/cc507094.aspx#blendpreview


 

What's new with Silverlight Tools Beta 2? In a nutshell:

1. WCF templates for Silverlight Enabled.

2. Build configurations.

3. XAML Validation now reports build errors.

4. Setup Improvements.

5. Projects created in Beta 1 are prompted for conversion when opening to Beta 2.

6. Linking a Web Site to a Silverlight Application.


 

Here is a post from Mike Snow who explains in detail these news:

http://blogs.msdn.com/webdevtools/archive/2008/06/06/what-s-new-with-silverlight-tools-beta-2.aspx


 

jueves 5 de junio de 2008

OSLO, see you in October …

Microsoft seems to be making good advances in modeling-based development. OSLO three primary components are proof of that:

  • A modeling tool
  • A repository
  • A declarative programming language

A bit far yet to know details about of these components, it was announced that in October it will be available the first CTP of the series J.

The news here:

http://www.infoworld.com/archives/emailPrint.jsp?R=printThis&A=/article/08/06/03/microsoft-readies-oslo_1.html    

Some key notes:

  • The modeling tool will be a graphical tool for building any kind of application. It will feature schema design and be leveraged by Microsoft products such as Visual Studio and BizTalk.
  • The repository, based on Microsoft's SQL Server database, will provide a single view of an application across different products, such as Visual Studio Team System application lifecycle management platform, Microsoft System Center, and BizTalk.
  • The declarative language is intended to leverage declarative concepts to make it easier to customize applications and reduce the need to write code. It is to be used within Visual Studio and the BizTalk integration platform.
  • Also at TechEd, company officials noted plans to support Unified Modeling Language (UML) in the planned "Rosario" release of Visual Studio Team System
  • Microsoft at the conference also will release a second beta version of its Silverlight 2 browser plug-in technology for rich Internet applications.

Microsoft also plans to release its Sync Framework in the third quarter of this year. The company at TechEd announced a CTP of Sync is available for the Windows Mobile platform.

miércoles 4 de junio de 2008

The real value of any creation is in the implementation, not the idea.

Honestly, I am the kind of people that come up with ideas and then think everything needed around the idea, including planning, resources, etc, etc, having in mind the best implementation of that idea.

Regrettably, very few times (believe, very few L) I can achieve that kind of implementation and hence, maybe a good motivating idea turned into a demotivating one, because the complex I made the implementation. Even worse, on the middle a lot of value was lost.

Why? Because the real value of any creation is in the implementation, not the idea
itself. The more concrete an idea becomes, the more valuable it is.

I came up with this concept and reflection [mostly about myself], after reading this article from Steve Pavlina http://www.stevepavlina.com/blog/2008/05/the-value-of-ideas/

I will share some key phrases/concepts for me about the article and I strongly recommend reading it:

Generating Good Ideas

  • Coming up with good ideas is easy, anybody can generate new ideas. If you do not have anything on mind, just make a brainstorming, you will find lots of good ideas.
  • That is not the problem, neither the challenge.

The Value of Implementation

  • Implementing ideas is hard because that's where things get complicated. The devil is in the details. Turning something mental into something physical is often quite a challenge.
  • The more concrete your ideas become, the more valuable they are.
  • I keep trying to find more optimal solutions to problems when it would be faster and easier to just implement a mediocre solution and deal with the consequences. I have to remind myself that getting some value is better than none.

Making Ideas Concrete

  • Part of implementing an idea is making it more concrete, such as by creating a design doc or business plan.
  • The more concrete your ideas become, the more valuable they are. The ultimate value, however, isn't delivered until your idea is in some kind of physical form that can be shared.

Focusing on Implementation

  • In many situations, mistakes can be easily corrected. If you make a mistake in building a website, you can reprogram it to fix the mistake. If you move to a neighborhood you don't like, you can move again. If you get in a bad relationship, you can break up. If you quit a job and later regret your decision, you can find employment again. If you write a bad draft of your book, you can rewrite it. Sure there are consequences, but in many cases it's not the end of the world if you jump to implement a half-baked idea. At least your implementation will still provide some value, and sometimes that's good enough.
  • If you're not sure if you're stuck in the idea phase, give yourself a deadline to start implementing your idea, regardless of how good it is. Deadlines are a necessary evil in many creative fields like movies and game development.
  • For example, my website has a fairly basic design. I put together something simple and functional in order to get the site launched without worrying about perfecting it. If I were starting from scratch today, I would have done a few things differently.
  • If an idea doesn't quickly lead to its own implementation, maybe it's not such a great idea after all. Maybe you're overcomplicating the idea to the point where it actually becomes demotivating. Can you define the idea in simpler terms, so simple that you can actually start working on it today?
  • What you release may not be the perfect implementation, but at least you'll get it out the door.

Action Time

  • Time to work on implementation, but when If I am up to my head of work!! ? Well, a technique that Steve says and I also recommend is: to have Action Hours or Action Days. Do set aside a block of time such as an hour or a day to do nothing but implementation.
  • To kick off this period of action, create a quick Action List. An Action List is a specific type of to-do list. It doesn't include any items that involve planning, high-level decision-making, communication, or discussion. Every item on the list must be geared towards moving some project forward to the point of value delivery. This means each item on the list must shift a task or project further along the spectrum from mental idea to physical action.


 

Well, hope this post delivers some value too. When I saw Steve's article I said to myself 'I will put it on my To-Blog list'. Then I thought twice and said to myself 'Let's take it to the implementation'. Maybe this is not the perfect post but at least I think this way I am delivering some value instead of just putting it on my list and wait to have the right time and the right words to write the right post J.

Thanks,

PP