This post announces an event for the spanish talking community
El martes 13 de Mayo, con mi amigo experto en ASP.NET MVC, Juan Pablo Garcia, vamos a dar una introducción al nuevo framework de 45 minutos. Usaremos el Preview 2 y durante la presentacion haremos una demo que abarca la mayor parte de los conceptos nuevos de ASP.NET MVC.
Se pueden registrar aca: http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032376090&EventCategory=4&culture=es-AR&CountryCode=AR
It's been a while as Kent said in his post. We've packaged lots of work done in the past 6 months or so. Mariano and Sebastian from the Southworks team have been actively commiting code.
Read the features in the home page of our codeplex site and download the release if you want to see some cool reference implementations and WPF CAB on esteroids.
This friday (Feb, 15th) Microsoft is holding an Architect Forum. Agile is the topic.
When: Feb 15th
Where: Buchard 710 4to
Lots of things will be covered by different experts that apply agile methodologies: Scrum and TFS, TDD, FDD, Crystal, MoQ Framework and Build Automation and Continous Integration among other things.
Together with Johnny we will present about our experiences automating builds and applying CI in many projects.
If you want to attend send an email to: v-sconde at microsoft dot com
For those who don't have VS 2008 yet, I created the VS 2005 templates
You will get two kind of solution/project templates (the same you get for VS 2008)
The MVC framework uses anonymous types extensively (for instance when you add Routes and set Defaults values for the route segments). You can see I provided an MvcDefaults class in the template which contains common properties like controller, action and id. You can either use that approach or install support for C# 3.0 in VS 2005.
Download ASP.NET MVC Visual Studio 2005 Templates (VSI format)
Enjoy!
I've arrived to China after a long journey (~35 hours). I still needs to figure out what's the time and what should I eat. Shanghai is very nice and it looks like any occidental city plenty of people and lights.
This week I will present in Chengdu about Software Factories and next week will deliver a 2 day workshop. And of course I will go to the Great Wall, the Forbidden City and squeeze every minute I'm here.
The good old Updater Application Block won't be updated <g> by patterns & practices, and the community now owns it. Our team at Smart Client Contrib took ownership of it. We (Curtis Gray mainly) ported it to work on .net 2.0 and Windows Vista. Below is the change log:
Application Block source code
- Works in Windows Vista!
- Updater Application Block relies on Enterprise Library 2.0 (Jan 2006) for the configuration
- Enterprise Library 3.0 could be used by recompiling the block and changing the configuration files
- BITS downloader no longer requires Administrator access.
- InstallUtil processor scans the .NET framework redist folders for a specified version of the InstallUtil application. It is no longer necessary to have .NET 1.1 installed.
- Multiple downloaders are correctly enumerated.
- Various changes and bug fixes to correctly parse Updater configuration files for each activation processor.
- Added saving of Source Folder in Manifest Editor
- The code compiles on .Net 2.0
- Quickstarts migrated to support the new configuration system
- Breaking changes only related to configuration and not the Updater API
- Bits Downloader now handles broken downloads gracefully
- UpdaterTask serialization fixed. There was a bug on the net 1.1 version of UAB related to the partial update scenario. When some files were removed from the manifest, the UAB serializes the UpdaterTask with the original version of the files. This caused the ApplicationDeployProcessor to fail.
- Partial update scenario fixed. The algorithms that might be used to calculate file hashes are non-keyed hash algorithms like: MD5; RIPEMD160; SHA1; SHA256; SHA384; SHA512
- Manifest tool fixed to correctly support salt enabled hashes
Samples
- Bootstrapper sample: a small exe app that will be installed in the client and will manage the updates
- MSI: showcase how to use MSIs to install, patch or remove an application
- Automatic Update: the application managing the updates automatically
- Manual Update: the user might decide to update or not the application
On the Smart Client side, we have some new features, samples and bugs fixed:
New Features:
- ItemsControlChildUIAdapter : allows any child of an ItemsControl to be utilized as a UI extension site (for example, allows a Separator to be used as an extension site)
- FrameworkContentElementActivationService : ensures any WPF FrameworkContentElements are built up correctly and exhibit the same behavior as FrameworkElements
- WrappedCabCommand : a WPF ICommand that wraps a CAB Command
Samples:
- Shell samples:
- ApplicationShellApplication
- WindowShellApplication
- Workspace samples:
- WindowsWorkspace
- DeckWorkspace
- TabWorkspace
- ZoneWorkspace
- Miscellaneous samples:
- Custom Visualizer
Bug Fixes
- Fixed bug in FrameworkElementActivationService that was assuming the OriginalSource of a focus event was a FrameworkElement
- Ensuring WindowSmartPartInfo only applies values to dependency properties if explicitly set
Go to our Codeplex site and start using them!
Thanks to everyone who attended the briefing. It was really cool to see so many people interested in what we were talking. These are Beto and myself on stage during my presentation about user experience with WPF (look at the cool snowboard in 3D:)...
Thanks to Paulo and Ezequiel who wrote this piece of code. Paulo is an expert on XAML art and Ezequiel simply grabbed the XAML, open it in Visual Studio and added offline support within a couple of hours. Thanks!
As I said during the presentation here is the code and the ppt...
When: September 20th, 2007
Where: Paseo La Plaza, Buenos Aires, Argentina
I'll be presenting about "user experience" and what could be achieved using WPF in a scenario where offline is required. This is a preview...
Register here!
The p&p client team is working hard on getting hands on labs for both Smart Client Software Factory/CAB and Web Client Software Factory out of the door. I've been following the work they've been doing and I must say that the labs are the most insightful labs I ever seen.
Mariano was heavily involved in the creation of the labs and he really knows the technology, so the quality of the labs is pretty good. Now he's asking for feedback on the Smart Client labs since a final release of them is coming that will show how to use the Disconnected Service Agent and the WPF support. He also announced that the labs for Web Client Software Factory are available to download.
I’ve been playing with Visual Studio 2008 Beta 2 lately and found a little gem: offline support for source control. It does not do everything I would like (like ability to use the Source Control Explorer offline), but we get enough to work with a solution when there is no connection to TFS.
1. When you open a solution offline (no access to TFS) this dialog will pop up saying that the solution will be opened in offline mode. Click OK.
2. Let's say you need to change “styles.css”. You open it and when you are done you will try saving it. You will get this known dialog saying that the file is write-protected. This is because the source control client protects the file against changes outside the tool.
Click on Overwrite to save the changes
3. Online again! Right click on the solution and press “Go Online”
4. Visual Studio 2008 will check the solution for changes while you were offline and will show this dialog. Press Go Online so the changes are applied in the TFS.
5. Notice how the styles.css file is checked out.
6. Now you can go on with more changes and check in your code. Changes made offline/online will be commited to TFS
Now there is no excuse if the TFS is down or you don't have access to it :)
We started this effort a month ago and now we have a v1!
The team conformed by Kent Boogaart, Bil Simser, Ward Bell, Chris Holmes, Ezequiel Jadib and myself worked together to get a decent release out!
The package includes the following:
The CAB Visualizer is soo cool. It will help both newbies and experts to understand better what is happening behind the scenes on a CAB application.
Download the binaries or the source code from the codeplex site!
Now that the Outlook Bar is finally in scsf contrib I will close codeplex.com/cabextensions.
It was on December 2006 when I first looked at this new framework on a developer lab at Redmond. I'm a big supporter of CAB as you may noticed if you read this blog and that is why I was invited. They want feedback. Acropolis grabbed many concepts and patterns that were successful in CAB, so people who invested in CAB and/or SCSF will have a seamless migration path and will understand Acropolis without too much hassle. Read this post from Glenn for more information on the future of CAB/SCSF.
Ezequiel Jadib is starting a set of posts/tutorials for Acropolis and the first is the classic hello world using a Part and a Command with the default layout.
Glenn posted about it. I will be collaborating in the project and together with Bil Simser, Ward Bell and Kent Boogaart we will try to make it significant.
I will move the Outlook bar to the contrib project and any other addition I made in the past and will do in the future will go there. Kent already uploaded the WPF CAB layer implementation.
We've been working with the Microsoft Learning group at Redmond to define the upcoming TS (Technology Specialist) exam for WCF 3.5. Howard Dierking hosted the design session and it was a great experience.
He explained us the refactoring of the exam stack. Now they have these new TS exams that are specific to a single technology and other exams on top of TS called PRO that will be more scenario oriented. They are doing the right thing by bringing Subject Matter Experts to the design sessions. We brainstormed on the most important aspects of WCF that someone should be tested on.
I'll be waiting for the beta exams to see how it finally shapes...
Read Miguel's post about the upcoming support for WPF.
There is no black magic. Simply you will be able to treat WPF smartparts as you treated Winforms smartpart (i.e. dependency injection will apply).
Also you will get a recipe to add a WPF view with a presenter.
People who invested in CAB will have a smooth migration path from Winforms to WPF and a familiar programming model.