News aggregator
Networking in Windows Vista
My Experience with Windows Vista Build 5219
I am currently writing this blog from Windows Vista Build 5219, known as the Community Technology Preview(CTP)Â for September or PDC 2005 Build.
I want to talk about several key areas that have spiked by interest in this new Build. But before I talk about those, I'd like to say overall stability-wise, Build 5219 seems to carry over the stability seen in Beta 1. I've noticed only very few issues. One of the issues for me has to do with the Wireless Networking (an issue I've noticed others have had troubles with from posts on different forums around the web). Build 5219 picked up my DLink Wireless Card and loaded the drivers and detected my wireless network. But for some reason, it wouldn't let me manually put in my IP Configuration (I do not have DHCP enabled on my Router). The IP config just wouldn't stick! I would right-click on the Wireless Networking icon in the taskbar to "Repair" and I would get a "Windows Explorer" error and then the Explorer shell would crash and reload. I did not have this issue in Beta 1.
Ok now on to the neat stuff.
Transparent Taskbar: Microsoft is now making the taskbar transparent as it does with all its new Aero windows you see within Vista. I like this. The transparency isn't too much or too little. Very cool enhancement. It makes me wonder what they have up their sleeve in terms of the new user interface being talked about for Beta 2.
Windows Sidebar: Ok, I am very happy Microsoft decided to bring the Sidebar back. Its potential was apparent right from the beginning (atleast to me) and it definately seems Microsoft sees that potential now and of course with the RSS built in all over the OS, the Sidebar is a great tool. And the Gadgets will surely rock the user interface in Vista. I can't wait to see the types of Gadgets people come up with. I can't really figure out why, I am very excited for the Sidebar.
Windows Mail: Although still called Outlook Express in this build, I am going to refer to it as Windows Mail because I think Windows Mail is so much cooler than Outlook Express, I think Outlook Express can easily be forgotten. Windows Mail redefines the standard home user's ability to check their mail. Just as explained in my previous blog about Windows Mail a few days ago, in Build 5219 you can see alot of what they talked about in the Channel 9 video emerging. The emails are saved as .eml files and searchable within Vista. Although, in this build it looks like Outlook Express, its going to end up looking alot more like Outlook 2003. Except, I challenge the Windows Mail team to go all out. Be different. Develop a rocking email client. Go beyond just minicing Outlook. I am definately really excited about this one.
Address Book: Ok, I am a big nerd for even mentioning this but its cool how the Address Book has changed to allow seperate "contact files" for each contact which I have no doubt will be searchable via Windows Vista's awesome Windows Search. I like this concept alot and hope and wish that the Windows Mail team taps into this (and even the Outlook team for Outlook 12). I remember reading somewhere someplace this will eventually be "Windows Phonebook". Not sure I like that name. I would rather see "Windows Contacts" or something else...cause from what I see now, it goes beyond just being a phonebook.
Windows Calendar: Could be cool. In this build, it doesn't do anything but I'd like to see it tap into the Sidebar technology with a gadget and also tap into Windows Mail. I want to see built in reminders in Vista for calendar entries.
Did I mention how much I love the Sidebar?
They also improved the search feature a bit in this build by allowing you to search beyond your User folder. I could never get it to search anywhere else in Beta 1.
I will be posting more later on with screenshots!
Reminder: Sam Gentile at Code Camp IV This Weekend
It wasn't until someone reminded me by phone today that Code Camp IV was this weekend that I realized. Look here for the “Almost Final Agenda.†You'll all be there right? As Thom mentions we have 75+ sessions and did we mention its free? What am I doing? Fun stuff, stuff that I haven't really talked on before:
400
How Agile is MSF-Agile and VSTS?
Ever since its creation in the early 90’s with Extreme Programming, Agile methodologies have become the methodology of choice for most programmers. VSTS takes a huge step forward by supporting Team development including process guidance with MSF-Agile as its default software methodology. But with daily use, many Agile developers are asking “How Agile is this really?†With this session, a creating member of Extreme Programming will examine Agile practices, what MSF-Agile provides out of the box, and then look at you can address the difficult areas of TDD and Continuous Integration, where VSTS and MSF-Agile fall somewhat short.
Sam Gentile
Presentation
300
VSTS for Architects: DSI, SDM and the Whitehorse Designers
There is a lot VSTS Team Architect Edition offers long-suffering Microsoft Infrastructure and Solution Architects. We will begin with an overview of DSM and the SDM Model that underlies Whitehorse and how it differs greatly from UML Modeling. From there, we will use the Distributed System Designers (Code-named Whitehorse) to design an SOA based Indigo Service
Sam Gentile
Presentation
400
Creating Advanced SOA Services with Indigo on Windows Vista
Building on sessions such as Michael Stiffel’s “Windows Communications Foundation aka Indigo and Service Oriented Architecture (SOA)â€, this session by an Indigo Insider and Software Design Reviewer, will delve into advanced Indigo SOA services using the added facilities available using Windows Vista. This is an advanced session and assumes prior Indigo and WSE knowledge.
Sam Gentile
Presentation
400
Occasionally Connected Smart Clients?
Many developers assume wireless will be everywhere enabling applications to communicate to centrally located servers regardless of where the user is. Any developer that has actually tried deploying connected applications knows that this is really just a dream of an alternate universe that simply frustrates users with reality. Users want their applications to just work and their data to be available even if the network isn’t. Custom applications require data and application updates to be constantly verified. Users shouldn’t have to press a button or manually switch from local to remote modes. In this session we’ll demonstrate how to build an Outlook 2003 style application that synchronizes data asynchronously when the network is available as well as checking for application updates. Using Visual Studio 2005 (Whidbey), we’ll cover how to use ClickOnce background sync API’s to constantly check for application updates so users don’t have to restart their application just to find out they have updates. We’ll cover synching technologies available using SQL Mobile for the Tablet PC and merge replication available for SQL Express as well as SQL Mobile. Empower your users with Smart Client Applications that work where the user is, not where the network may be.
Sam Gentile
Presentation
The new Outlook Express: Vista Windows Mail demoed
Developer Best Practices and Guidelines for Applications in a Least Privileged Environment
Crypto in Windows Vista
Windows Workflow Foundation Ahead of Schedule
PDC 05 site online
A Guided Tour of Windows Presentation Foundation
Where is IIS in Vista Build 5219?
9/14 WinFX Sept CTP Released but Will NOT Install on Vista Beta 1
posted on Wednesday, September 14, 2005 6:25 PM
9/14 - First of Monthly Vista CTP Builds
posted on Wednesday, September 14, 2005 10:44 AM
9/13 - New Stuff Videos Up on Channel 9
Also there now are the AERO interface video, the 10 things devs need to know to build a great Windows Vista video, LINQ video, and the Internet Hearts video (a cool game written with Windows Presentation Foundation).â€
posted on Tuesday, September 13, 2005 5:25 PM
9/13 - Microsoft MAX ! on Vista
5219 Build screenshots
Bill Gates Shows Next Windows
Vista Creates Developer Opportunities
Introducing Windows Mail
Channel 9 has thrown online a introduction and demo of the new Outlook Express now being called Windows Mail.
The new Windows Mail is dramatically different than what we have today with Outlook Express. The underlying way Outlook Express stores email has been completely tossed out. Instead, Windows Mail will store email messages on your machine as SEPERATE files (they talked about these email files me .eml extensions in the video). So you don't have to worry about corruption as much. It will be more less likely to have Windows Mail become corrupt and you loose all your email. The database storage system is JET which is being used all over the place in different applications and even within Windows Vista. What's even cooler is that you can open these emails seperately from having to launch Windows Mail. So lets say you store all your emails in a folder in Documents and are in a hurry and need to check out a specific email - you can open it via that folder in Documents, or of course use the nifty Windows Search. The email files are stored in a nice neat view in the Windows shell, just as most of your files in Vista so - in all actuallity, your email is just files. The mail program is nothing more than a nicer more organized view with a few more features. You can even reply to an email direct from the Windows shell in Vista by just right-clicking on one of the emails! I'm not sure if this is bringing on the end of email applications but it sure seems like it. Its a very overwhelming concept that will take me quite some time to get used to.
For the user interface, they are pretty much copying the Outlook interface to a certain degree of course with Vista UI enhancements thrown in such as the search box in the upper right hand corner of the program.
The Windows Mail Team has also devised a much easier way for the user to back up their email. Outlook Express pretty much blows when it comes to trying to back stuff up. Now there is only one directory you really need to back up: /mail/. This is fantastic.
What the Channel 9 Video here!
I personally think that Windows Mail is very promising for the home end user. Do I think I'll go to Windows Mail after using Outlook 2003 (and have had an great experience) for so long? Perhaps. I am willing - and more definately will - to give Windows Mail a try.
Another thing, I give big kudos to Microsoft for steamlining the naming in Windows Vista. I like the "Windows" application name theme they seem to be going with such as "Windows Mail" or "Windows Calendar" and so fourth. Its easy to remember, its consistant, and it makes sense. When I start talking to people about these applications, they will probably more likely to remember and understand its name.
Windows Vista Build 5219 Aero Glass is Amazing!
So, I said in my last post that I didn't get Aero Glass by default on my NVidia GeForce FX Go5200 but you can change this. I found how on this post on Neowin:
Start > run, type in devmgmt.msc
Display Adapters > right click on Geforce FX Go5200
goto drivers
update drivers
don't do win update
don't search
choose pick from list
uncheck show compatible hardware
Man: nVidia
Device: Geforce FX 5200 (LDDM)
The thing that is amazing is all the visual candy that now works such as the Sliding Full Preview Alt-Tab feature and the Windows - Spacebar Window stacking! Holy cow this rocks! The only trouble is with the LDDM Glass driver I can only get 1024X768 instead of the regular 1440X900 widescreen which makes it hard to work but the effects are mindblowing.
Hmm, now my Glass is gone. I installed and ran VirtualPC and its gone now. [:@]
Model, View and ModelView pattern
Sparkle is the code name of Microsoft Interactive Designer. It is probably the first significative project totally build with WPF/Avalon: it's 100% managed code, with a total build time of 90 seconds (on a 2GHz PentiumM) and it designs WPF/Avalon user interface using WPF/Avalon user interface. His developers learned many lessons by this experience, shared with us at PDC.
A suggested pattern to implement user interface in WPF/Avalon is a Model, View, ModelView pattern:
- a Model is code (classes);
- a View is written in XAML;
- a ModelView is a class (code) that makes an abstraction of the view in terms of state and interaction activities.
The XAML View can use data-binding to Model and/or ModelView classes (it depends on the operation that has to be implemented) in an effective way. Data binding can join a button with a method, for example to set a certain state of the Model. This pattern allow developers to take control over Model and ModelView (code), while graphic designers control Views (XAML), both accessing to the same source tree!
I think that developing today a Windows Forms application following the same pattern (remove all the form state and behavior from the Form class and put it into another class) could give the better code base to easily migrate to WPF/Avalon. Also refactoring an existing application to this pattern could be a suggested migration path.
