Ok - before anyone says it.. yes, the grid in the version posted earlier tonight was not pretty.
It's been changed and now looks much better. See below:
 
I did four things this weekend - (1) I read some comments on blogs regarding what people thought Information Center was (and their expectations), (2) did a fair amount of usability testing, (3) wrote alot of code, and (4) consumed more diet coke than any individual should in a 48 hour period.
I've had feedback from alot of people both direct and through comments I've read on various sites, that they'd really like to be able to use this for more than just technology blogs / podcasts. There were *alot* of people who said they'd like a new tool to manage their podcasts specifically. I listened and I made some significant changes such that I think this is going to meet expectations. You'll see in the screenshots below sites that are distinctly non-technical, like NBC's Meet The Press and YouTube's Top Rated feeds. You'll also notice the guide now lists *alot* of non-technical categories. Alot of people were asking for this, so I rolled this in as a core feature in the first CTP vs. delivering it later on.
I've totally overhauled the UI, and for the first time since Information Center's inception, I'm really happy with it. One challenge was in providing as good as an experience for text based content (standard blogs) as media, the other was integrating subscriptions, subscribing, sharing, and mixing in such a way as it was intuitive. I really think the UI is finally there. I've taken a number of screenshots from my testing today and have placed them below so you can see for yourself.
In addition, you'll notice there are graphics for the blogs that are there. Where are these coming from? Images will be pulled from the relevant tags for the channel in core RSS (seen in my blog below), iTunes extensions (seen in Meet The Press and MajorNelson.com), or NewsGator extensions (seen in Channel 9). For those sites that do not specify a channel graphic, it will go to a default (see YouTube below)
I also had a fair amount of comments around the browsing window. Specifically "What if I want to watch the video in a bigger window?" What's not visible in the screenshots - but it's there, I swear  - is a slider. The upper section (video/blog description, image, description) and the list of items are on two separate panels. You can extend either as much as you'd like. Once you click on an item, it determines you current window size and resizes the embedded media player appropriately. You'll also note that the video/blog area is large in general. This works out particularly well for text blogs, as you can extend to the full screen to read.
I've also been building out a tool behind the scenes which I call FeedCenter/FeedStation, which is helping me manage all of the feeds behind the scenes as well.
So - if you've ever done consulting or project management, you're familiar with the trade-off triangle. For those unfamiliar, you have time, resources and features and impacts to one area have carry on effects on others. In this case, the UI has been re-done and locked down and this can be used for lot's on non-tech content much easier now - but it's pushed this back a few days more.
This is a slow week at the office, so should be able to freely crank this out in the evenings and turn it around soon.
Please keep those comments coming - mmercuri@microsoft.com - as you can see by the accelerated inclusion of non-tech content, I really do listen
Cheers,
Marc
 
        
I mentioned in an earlier post that InfoCenter would be delayed a few days. What does that translate to? No later than 12:01am Monday PAC time. Likely before, if you signed up for a notification, you'll receive an email.
Otherwise, if you check back on Monday there will be bits available for use.
If you're asking 'Why the delay?'. There were some things I'd wanted to include in V1, that I hand't and given the state of where InfoCenter is, and how long it would take to get them in, I decided to push the drop back a couple of days. It will, without question, be on the site on Monday. Right now, there are close to 200 channels configured, and there are a couple of additions I think you'll like when you get it on Monday.
If you're really keen, if you check back over the weekend, you'll start seeing some interesting stuff pop up on Sunday.
Cheers,
Marc
"Do we really need another aggregator?" - This is a question I've been asked alot lately, in regards to Information Center.
My answer is Yes. I hope yours is too. Let me tell you why I think this, and then I'll show you some pictures from the UI that underscore the point.
I think there are a couple of things that set InfoCenter apart:
(a) featured feeds. This isn't just a client, it's pro-active - new feeds find you.
(b) media is a first class citizen in InfoCenter. The future is in media. Audio in the form of podcasts, video in any number of forms. Look at the success of podcasts on portable media devices, look at the popularity and growth rate of places like YouTube. In most aggregators, media is viewed as an attachment. in Information Center, media is a first class citizen.
(c) Information Center is designed to support just about any type of mainstream media out of the box (or can readily support it something like, say , quicktime, with a download from that vendors site). This means it will play MP3s and WMAs, it means it will play WMVs, MOVs, and other video files, and it also will play shockwave and flash. What does this mean? You can play podcasts, vblogs, and even embed YouTube's player in a feed.
(c) Information Center heavily leverages categories. You'll be able to leverage this for discoverability, and dvr-like suggestions based on your tag preferences.
(d) As stated earlier, InfoCenter will come with feeds out of the box - but you can change them and re-mix them. AND you can share them. Think about television - tv shows like Friends, Law & Order, the Brady Bunch, are all in syndication (remember that last S in RSS?) You can effectively become your own network. You can build your own feed of *links* - even if they exist across multiple sites - and take that feed and publish it as your own network. You can generate IC files (these are familiar RSS files) and share them however you like online, via email, CD/DVD, etc.
(e) Speaking of DVD, you can ship a DVD with an IC file in root, and with InfoCenter defined in the autorun, and it will start up in a kiosk mode. Allowing you to use this for content that exists offline, online, or both.
(e) InfoCenter is going to be delayed a few more days, such that I can ship a tool to allow you to easily mix your own feeds on Day 1.
Take a look at the screenshots below, it shows how powerful RSS and a new style aggregator can be. You can see that this readily displays Microsoft content (Going Deep on Channel 9, a GnomeDex video from On10.NET, and ARCast with Ron Jacobs from Skyscrapr.NET), as well as content from other third parties - including TWiT, Digg, and YouTube.
How difficult was it to do? One line in a configuration file. You just point to their feed direct or add it to your subscriptions, and you're in business.
Oh, before I forget, alot of people assumed this was done in WPF. I WISH! This is a Windows Forms application that leverages a number of controls that I've written (12, at last count). There will be a full .NET FX 3.0 version of this once those bits ship.
       
One of the primary drivers for my creating InfoCenter was to provide a tool that made discoverability easier. Earlier in the year, I came to the conclusion that even in the best case scenario - where a robust, populated guide is provided - the web is fluid, and there was still a need for search.
That being said, search covered a number of areas - the traditional (web), but also blogs, wikis and newsgroups. Sometimes I'll go to search site #1, then to a wiki site, and then to a blog search engine, etc. Rather than going to 4 or 5 different sites, I wanted a single interface where I could enter my query once and then be able to readily navigate amongst the different type of search stores.
In addition, sometimes even within a category - some search engines algorithms are a bit different, and if unsatisfied with the results from the favorite engine, people will check a secondary, and sometimes even a third search engine.
As my customers are primarily in the Enterprise, I also added an area called 'Vendors' - this taps into the search engines of major software vendors (Microsoft, IBM, Sun, Oracle, SAP, etc.)
Information Center provides the ability to determine the category of search at the top of the screen, allowing you to change context very easily. If search criteria have been established, the search will kick off automatically in the new context (i.e. from Web to Blogs).
In addition, at the bottom of the screen are a number of tabs that represent different search engines within a category. Clicking on any of these will send a query to those search engines automatically.
Under the covers, what I've done is written a .NET assembly that knows how to structure a search for these various web, newsgroup, blog, wiki, and third-party vendors. As a result, you don't need to navigate amongst multiple sites in a browser, nor do you need to re-key your search criteria.
I've attached screenshots below of the various tabs and their functionality. If you have any questions or feedback, I'm very much interestedin hearing it.
Regards,
Marc
In my work, I work very heavily with pre-released technologies (like Windows Communication Foundation, Workflow Foundation, etc.)
The two questions I get asked fairly often - particularly now that we have so many products coming out and have embraced community technology previews for those products - is 'How do I know what the new stuff is, and how do I know when I can get it?". Right behind that are requests for things such as samples, utilities, etc.
InfoCenter has a tab named Downloads that aims to help alleviate this issue. The screen has links to downloads, betas and CTPs, demos, trial software, and utilities. In addition, the current MSDN top 10 downloads are featured on the main page.
Reposted after the Microsoft Watch - EWeek references:
If you've seen/heard the latest podcast by the great folks over at DotNetRocks, you've heard the first public talk about a pet project of mine called InfoCenter. If you haven't - then it might be worth checking out here - http://dotnetrocks.com/default.aspx?showID=189.
While this is the first public discussion/showing of InfoCenter, the UI has undergone a very interesting set of changes recently. The .NET Rocks podcast was actually recorded close to a month ago, at which time this announcement was targeted to go live on the 18th. Unfortunately, the original UI for InfoCenter (below) was similiar enough to a certain next-generation gaming console that it was ...err.. politely suggested (strongly too ), that the interface be changed before sharing outside the company. Fortunately, those same next generation console folks were very cool about it, and offered to re-design the interface for me for free. The UI also incorported alot of feedback I had from folks inside Microsoft who took a look at the original design / navigation flow.
You can see the original and the new UI below:
The original, and the released UI
 
Before we get to the introduction, I want to stress that InfoCenter is a pet project of mine - it is not an official Microsoft product, there is no sku for it, and until someone tells me otherwise, it's free.
Without further ado, the introduction........
Introduction
In the early days of Windows, discovery of Microsoft related content – be it new product announcements, documentation, guidance/how to’s, downloads or community – was relatively straightforward. There were four key areas to look – Microsoft.Com, MSDN, ftp.microsoft.com, and UseNet newsgroups.
During this period, Microsoft excited, educated, and enabled a legion of developers and developer-hopefuls to become part of the profitable software economy. UseNet Newsgroups provided a forum that had not yet been corrupted by spammers, and provided a unique opportunity for individuals to audit a master class, a class where the professors were some of the more well known names in the industry.
Today, things are significantly different. There are more products, more places to look for information, more categories of information, and less time in which to find it.
Today’s reality has Microsoft releasing more new products and new product versions than in the entire history of the company. There are new versions of Windows, Office, Server, Mobile, Web, and Live. There are first class server products like Biztalk, Speech, SQL, and MOM. There are great new technologies like WCF, WF, WPF, and CardSpace.
With more products comes more content, and in the intervening years the number of locations where content can be found has exploded. When looking solely at Microsoft web properties, Microsoft.com and MSDN have been joined by Channel 9, ASP.NET, GotDotNet, and CodeZone. There are also numerous community sites now online, such as WindowsCommunication.NET, WindowsWorkflow.Net, IIS7.NET,MSDomino.net, etc.
Looking beyond 1 Microsoft Way, there are a multitude of other sites that are providing articles, downloads, code, and communities as well. Beyond the sites, there are hundreds of blogs that are driven by individuals both inside and outside the company. Discoverability of content is a major issue.
In addition to more locations to find more content, there are also new categories of content available. Due to the adoption of broadband in the intervening period, it is now realistic to distribute audio and video content in both streaming and downloadable varieties. This opens up new opportunities to both serve and distribute this content to various devices and formats.
I think developers need a mechanism by which top tier content is identified, categorized, aggregated, and searchable from a single interface. And that mechanism needs to be automated, such that fresh, targeted content finds its way to the Enterprise consumer.
To enable this, I thought there was a need for an application that leverages aspects of both the Windows OS and the web, with an engine powered by RSS. Through RSS, we can empower our clients to consume not just the feeds that we provide – but also the ability to mix in those of third party vendors as well as their own internal corporate blogs and best practices.
Just as we created a Media Center to harness the growing amount of media content enabled by software, the thought was that there could be something similiar that could be done for information. Essentially, I saw a need for an Information Center.
By harnessing information for people and providing them the ability to readily find and consume content of interest to them, I think there is an opportunity to once again educate, excite, and enable our next generation of developers.
Getting InfoCenter
With the late breaking design change, I've had to make some changes in the layout and the flow, and am just wrapping up the revised CTP. The link for the bits will officially be listed here August 9th. If you'd like an email sent if this is available sooner, if you'd like to chat suggest 'channels' for InfoCenter, or if you want to chat about InfoCenter, click here or send an email to mmercuri@microsoft.com with the following subject "[RequestFromBlog][InfoCenter][CTPNotification]"
Very best regards, Marc Mercuri
Prior to coming to Microsoft, I was VP of Development for a company called Gazelle. One of the challenges we had there, was the need to standardize the names of items in a restaurant environment such that they could be warehoused and compared across chains.
The problem that we found – and the problem I see getting out of hand with blogs today – is there is no common set of definitions that people utilize or contribute to. In a restaurant example, you have no UPC codes for say a margarita. The name is essentially what exists on the POS button. This name can change from physical location to physical location within a chain of restaurants, and also variants between chains. There are no hard rules on what name is defined on the POS key, other than name length. As a result, you ended up with “Marg”, “Rita”, “MRITA”, “Mrgrta”, “Mrgarita”, “Margarita”, etc. An elaborate set of filters needed to be developed, run through, tweaked, and run through again, with ultimately a human with domain expertise mapping the unknown items to an existing or known definition.
This is the same thing we’re seeing in blogs, only there are far more blogs than restaurants, and blogs cover far more subject matter domains than restaurants. Eventually, we will want to do what I did for restaurants at Gazelle – standardize data, provide common tags by which to identify, find, and share information.
I think there is a distinct opportunity for someone to stand up and show some leadership here and build a common repository of tags and allow people to contribute to them. This would need to also include a thesaurus of similar tags.
In addition to categorizations you might expect “Technology”, “Windows Communication Foundation”, etc. we can let people identify contexts in which that definition applies – be it verticals (retail, hospitality, financial services, entertainment, etc.), demographics (geography, language, age bracket, gender, marital status, etc.) This provides additional context which can help us with relevancy determinations in future.
If we ignore these categorization issues, I think we’re missing out on an easy opportunity to provide leadership in the web 2.0 space, and make it easier for both bloggers to get visibility as well as our search engines (and related advertising services) more information to bring results and ads back to customers.
At Gazelle, we approached the problem by designing a system that broke apart the word(s) and did pattern matching, auto-mapping what it could and going to an individual when it was questionable. The challenge there was it required someone who had domain specific knowledge and was not easily outsourced. In this scenario, we found that the team in India had a hard time mapping back some of the items purely from lack of exposure of some of the brands. When you look at tags, you have something exponentially larger because they cover any subject.
Consistency in tags is something that's a pre-requisite for the opportunity to do something meaningul with context, affinity, and trust for the next generation web.
One of the negatives of having InfoCenter as a sideproject, is that I've got a full time job that sometimes gets in the way
I've got to unexpectedly head to NYC next week to deliver an architectural design session for a customer, and while I've tried to get it polished off this weekend, it's just not there yet. The introduction of the new UI has required both new controls and some variants on the existing ones, and I'm not happy with where they're at right now (10pm on Sunday). As a result, I'm pushing the 'official' date is now Aug 9th, if it's wrapped up any sooner I'll post it here.
Cheers,
Marc
There's a blogger from Australia who had run across the DotNetRocks podcast, and had some questions about what InfoCenter is and what InfoCenter isn't. Quite frankly, I've been amazed at the response, considering the CTP isn't yet evailable.
At any rate, one of the questions that came up was around the value and/or role of the aggregator of feeds - not just software, but the humans who inject domain expertise and experience in putting together an aggregated blog. People who involve software and people to bring together a noise-free, targeted feed.
For this, I look to the last letter in RSS? That S stands for Syndication. Effectively, the way I see the world is that every blogger is a production company, generating syndicated content. While we can broadcast our own content via our blogs, there's also interest in repackaging our content and leveraging it in other places.
Just like in television, people generate revenue by hiring program directors / editors that compile a group of syndicated content into a product or programming schedule and sell ads based on viewership.
While the underlying value is in the content, there's tremendous value in the aggregation of particular content by people we trust and who we hold up as experts in a particular area.
We all have the opportunity to become program directors of RSS content, what needs to be figured out is how the revenue stream works back for the creator of the content. In the syndicated television world, you buy rights to a show for a particular period, for a particular market. The payment, as I understand it, is established up front.
On the web, it would seem this would be more fluid, and as a result there needs to be a way for either the syndicator to specify ads to be shown in conjunction with their content, or for networks/program directors to provide incremental revenue back to the networks/program directors.
If you've seen/heard the latest podcast by the great folks over at DotNetRocks, you've heard the first public talk about a pet project of mine called InfoCenter. If you haven't - then it might be worth checking out here - http://dotnetrocks.com/default.aspx?showID=189.
While this is the first public discussion/showing of InfoCenter, the UI has undergone a very interesting set of changes recently. The .NET Rocks podcast was actually recorded close to a month ago, at which time this announcement was targeted to go live on the 18th. Unfortunately, the original UI for InfoCenter (below) was similiar enough to a certain next-generation gaming console that it was ...err.. politely suggested (strongly too ), that the interface be changed before sharing outside the company. Fortunately, those same next generation console folks offered to re-design the interface for me for free. The UI also incorported alot of feedback I had from folks inside Microsoft who took a look at the original design / navigation flow.
You can see the original and the new UI below:
The original, and the released UI
Before we get to the introduction, I want to stress that InfoCenter is a pet project of mine - it is not an official Microsoft product, there is no sku for it, and until someone tells me otherwise, it's free.
Without further ado, the introduction........
Introduction
In the early days of Windows, discovery of Microsoft related content – be it new product announcements, documentation, guidance/how to’s, downloads or community – was relatively straightforward. There were four key areas to look – Microsoft.Com, MSDN, ftp.microsoft.com, and UseNet newsgroups.
During this period, Microsoft excited, educated, and enabled a legion of developers and developer-hopefuls to become part of the profitable software economy. UseNet Newsgroups provided a forum that had not yet been corrupted by spammers, and provided a unique opportunity for individuals to audit a master class, a class where the professors were some of the more well known names in the industry.
Today, things are significantly different. There are more products, more places to look for information, more categories of information, and less time in which to find it.
Today’s reality has Microsoft releasing more new products and new product versions than in the entire history of the company. There are new versions of Windows, Office, Server, Mobile, Web, and Live. There are first class server products like Biztalk, Speech, SQL, and MOM. There are great new technologies like WCF, WF, WPF, and CardSpace.
With more products comes more content, and in the intervening years the number of locations where content can be found has exploded. When looking solely at Microsoft web properties, Microsoft.com and MSDN have been joined by Channel 9, ASP.NET, GotDotNet, and CodeZone. There are also numerous community sites now online, such as WindowsCommunication.NET, WindowsWorkflow.Net, IIS7.NET,MSDomino.net, etc.
Looking beyond 1 Microsoft Way, there are a multitude of other sites that are providing articles, downloads, code, and communities as well. Beyond the sites, there are hundreds of blogs that are driven by individuals both inside and outside the company. Discoverability of content is a major issue.
In addition to more locations to find more content, there are also new categories of content available. Due to the adoption of broadband in the intervening period, it is now realistic to distribute audio and video content in both streaming and downloadable varieties. This opens up new opportunities to both serve and distribute this content to various devices and formats.
Our customers need our help, specifically they need a mechanism by which top tier content is identified, categorized, aggregated, and searchable from a single interface. And that mechanism needs to be automated, such that fresh, targeted content finds its way to the Enterprise consumer.
To enable this, we need to build the ultimate mash-up, a truly Live application that leverages aspects of both the Windows OS and the web, with an engine powered by RSS. Through RSS, we can empower our clients to consume not just the feeds that we provide – but also the ability to mix in those of third party vendors as well as their own internal corporate blogs and best practices.
Just as we created a Media Center to harness the growing amount of media content enabled by software, we need to now do the same for information. Essentially, we need to build an Information Center.
By harnessing information for our customers and providing them the ability to readily find and consume content of interest to them, we have an opportunity to once again educate, excite, and enable our next generation of customers.
Getting InfoCenter
With the late breaking design change, I've had to make some changes in the layout and the flow, and am just wrapping up the revised CTP. The link for the bits will officially be listed here next Wednesday, August 2nd. If you'd like an email sent if this is available sooner, if you'd like to chat suggest 'channels' for InfoCenter, or if you want to chat about InfoCenter, click here or send an email to mmercuri@microsoft.com with the following subject "[RequestFromBlog][InfoCenter][CTPNotification]"
Very best regards, Marc Mercuri
|
Twice a year, Microsoft hosts an internal technical readiness event called TechReady. TechReady3 is upon us, and I'll be hosting a couple of sessions. Both a session covering the scenarios where I'm seeing top customers use these technologies, as well as a set of instructor led labs that serve as a walk-through of WCF.
Details are below - some information was excluded ,such as customer names, as several of them are still confidential and will be announced when the technologies launch later this year.
ARC201 - WCF and WF in the Fortune 500: Lessons Learned During Enterprise GO Engagements (Solutions Architect) |
July 25, 2:30 PM - 3:45 PM
Hyatt-Leonessa I & II
|
|
As part of Enterprise GO, Marc worked with a number of Fortune 500 companies to incorporate WCF, WF, and Infocard into their solutions. Customers included [not shown here as some are MS confidential, full list in the schedule guide) This session reviews the scenarios in which the technologies were employed, lessons learned, and design decisions made.
| CONIL203 - Understanding Windows Communication Foundation in a Solution |
July 26, 11:00 AM - 12:15 PM
WSCTC-602-604
|
| In this lab you will witness the unified distributed programming model of Windows Communication Foundation. The exercises will walk you through creating and deploying a service and client as well as examining the management and monitoring capabilities of Windows Communication Foundation. Finally, the exercises will introduce you to the security and hosting capabilities available for your services. |
| CONIL203R - Understanding Windows Communication Foundation in a Solution |
July 26, 1:45 PM - 3:00 PM
WSCTC-602-604
|
| In this lab you will witness the unified distributed programming model of Windows Communication Foundation. The exercises will walk you through creating and deploying a service and client as well as examining the management and monitoring capabilities of Windows Communication Foundation. Finally, the exercises will introduce you to the security and hosting capabilities available for your services. | |
I've gone ahead and updated the sample for Chapter 9 - Custom Behaviors.
Rather than just do a straight port, I looked at the sample and recognized there were some opportunities to make it more interesting for the reader. I've made some changes and additions, which I think you will find beneficial -
Changed this to an EndpointBehavior. This is a more common scenario, and I think you'll find it more valuable.
Added code that shows how to add support for behaviors in the Config file. Note that this is accomplished through a combination of the code in AuditBehavior.AuditBehaviorSection.cs, by adding the behaviorExtensions section in the Service app.config, by specifying a behaviorConfiguration attribute on the endpoint element, and by defining that endpoint in the endpointBehaviors sections.
Use the behavior via configuration (service) and via code (client)
Added significant Console.Write comments so you can see exactly what is happening in which part of the code (i.e. the behavior, message inspector, etc.)
Consolidated all behavior related classes (including message inspectors) to a single project for greater clarity.
I've renamed the projects so there is no question which project is the service, which is the audit recording service, and which is the audit behavior class.
For querying the meta-data of a service, you must now explicitly do several things - add an endpoint for mex, add a behavior, and reference the behavior on the service via an attribute in the configuration file. These changes are also reflected in this sample. 09.zip (98.58 KB)
If you're working with the latest CTP, you may have noticed that InstanceContextMode.Shareable was removed from the InstanceContextMode enumeration.
You can still achieve this same functionality through extensibility. While the sample is being updated, I wanted to point out Maheshwar Jayaraman's blog. Maheshware is in the product group, and provides more information here:
http://blogs.msdn.com/mahjayar/archive/2006/07/08/660176.aspx
There were changes in the later CTPs that affected the code for Chapter 5.
InstanceContextMode.Shareable has been cut. As two of the three excercises here leverage shareable instancing, I am currently talking with the product team about a workaround they have using extensibility.
In the interim, I have updated the first exercise which deals with MSMQ. One thing that is different here is that binding on the sample was changed in the config files as based on Active Directory configurations, people were having challenges with the default binding. The sample in it's current state is should work regardless of configuration.
Also, for the service definition in the configuration file, the type attribute is now changed to name.
For querying the meta-data of a service, you must now explicitly do several things - add an endpoint for mex, add a behavior, and reference the behavior on the service via an attribute
05-PartI.zip (55.21 KB)
This is the updated code for Chapter 7. I will post a doc that covers the specific changes that were made.
The key changes here were very straightforward, and primarily were focused on the following -
For the service definition in the configuration file, the type attribute is now changed to name.
For querying the meta-data of a service, you must now explicitly do several things - add an endpoint for mex, add a behavior, and reference the behavior on the service via an attribute.
07.zip (322.66 KB)
I've had a couple of people ask me recently 'Why is the book using the January CTP bits and not the Feb/May/June/July CTP?"
If you're on one of the latest builds, I can imagine waiting for a new code update could be a bit annoying. I wanted to share that I've actually taken a couple days off of work to update and test the the code for the samples I wrote, and I've almost got everything moved over such that they're running fine on the June and July CTP bits. Expect them to be posted here tomorrow.
I also feel it's important to provide some insight into how that decision was made to go with the January CTP.
One of the great things about Microsoft is that they’re providing broad access to bits much earlier in the lifecycle, with regular refreshes via Community Technology Previews. For WCF, Microsoft is releasing drops in CTP form roughly every 1 – 1.5 months. As the product is still in development, the object model has changes each month based on customer feedback (moreso back in November, less so now). Now, of those monthly drops, only a small subset of them are actually allowable for use in production using a ‘go live’ license (per the end user license agreement).
There are distinct differences between a CTP that is licensed to ‘go live’ and one that is not. Testing for a ‘Go Live’ release is at a much higher quality bar than a non-Go Live release. The benefit for developers is that they can continue to develop and take advantage of the interim changes much more quickly than in years past (whereas historically, you may have hit a stopping point that of 6 months between a release of a Beta1 and a Beta2) The January CTP ,on which the released code was tested, was the last version that was approved to go into production with a ‘Go Live’ license. The interim drop that followed (February) was not available for Go Live. Based on the information we had, we went with the January CTP, with a commitment to update it – which we’re doing now.
I think you'll find of the authors who've written Beta books, Craig, Nigel, and I are probably the most eager to get updates for the new CTPs out there.
Over the weekend, I made some changes to the blog.
The underlying software has been updated to the latest dasBlog which has some nice enhancements.
I've built a new UI on top of DasBlog as well that looks a bit better than the oh-so-stylish, white on gray on darker gray style I have right now. The new graphics will go live on July 18th. The new 'blog' is much more of a site, and has links to the blog, whitepapers, demos, webcasts, and my history/resume. The timing of that launch will coincide with the CTP release of InfoCenter (my pet project). For those who can't wait until next week, here's a sample screenshot from the version running locally:
While you won't see that live until next week, what you can see today are two big changes tied to categorization. You will now be able to easily filter on just those posts from a particular month, as well as by a particular category. I actually went back and categorized every one of the posts going back to last October, and will categorize each post going forward.
I found that as the blog was evolving, there were now enough posts that some items that people were interested in were getting lost in all the posts. While there's a big chunk of people that read the blog for WCF/WF/CardSpace info, there is also a sizable number that liked the blog to read about my entries about Technology Futures (context, trust, identity).
To make the blog more accessible, the following categories have been added -
Announcements
Atlas
Cardspace
Context
CRM
Demos
Ideas
Identity
Interop
Legacy
Live
Meet
Other
Presentations
Search
SQL
Technology Futures
Trust
Virtualization
Visual Studio
WCF
Webcasts
WF
WPF
Looking for another one stop shop for your WCF, WF, WPF, and CardSpace (formerly InfoCard) needs?
http://netfx3.com/ was launched with the rebranding of winfx to netfx3, and now you can find info, demos, and forums on CardSpace and all your favorite foundation technologies there. This site consolidates what was windowsworkflow.net and windowscommunication.net.
Definately worth checking out, particularly as there were a number of new samples and demos uploaded that weren't on the old sites.
For those of you wondering where the heck I've been for the past couple of weeks, I think this helps describe the why...
World Cup - U2 - Sick Days Video:
(http://www.youtube.com/watch?v=W1zRcIJPrg8&search=u2%20world%20cup)
I've not just been a total World Cup slacker, however, I've been recording a new video series I'm looking to publish on Channel 9, been to TechEd, incubating a new project (to be unveiled on July 11th), closing out the end of year (Microsoft's fiscal year), some demos, a technical whitepaper or two and a blog software upgrade.
Lots of stuff will hit this week and next, so stay tuned..
Awhile back, I wrote about how Wikis and community sites would be our new memorials (Wiki as memorial? http://www.marcmercuri.com/PermaLink.aspx?guid=0f22d71f-8eed-4f32-a1da-7ced952bc97f). In that piece I commented on how Wikis and community sites like MySpace and space.msn.com would become the memorials of the digital age
“If you look at spaces.msn.com and myspace.com, you're starting to see the dawn of things happening. What is 'cool' for todays teens will become institutionalized, and we'll start to see people taking technology in interesting places to build these interactive histories and memorials.”
I ran across an interesting article this morning on the Associated Press wire “MySpace generation preserves memories online“(http://www.msnbc.msn.com/id/13526522/).
It looks like it's starting...
InfoCard has officially been renamed this week. It is now Microsoft CardSpace (WCS). As with the rebranding of Indigo to Windows Communication Foundation or for old schoolers like Thunder to Visual Basic, this is nothing to be concerned about.
This is just a natural transition from an internal, pre-release codename to a the official product name.
One of the things that was announced at TechEd was that was has been known as WinFX is being re-branded as .NET Framework 3.0.
Some folks have some questions about what this means, so I wanted to provide some clarifying info on this.
The .NET Framework 3.0 will still be comprised of the existing .NET Framework 2.0 components, including ASP.NET, WinForms, ADO.NET, base class libraries, and the CLR, as well as new technologies Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and Windows Workflow (WF). In addition, we have made a decision to name the technology formerly codenamed “InfoCard” as Windows CardSpace (WCS). Windows CardSpace will also be a component of the .NET Framework 3.0:
We announced this over the weekend through Soma's blog, and the two questions that I'm hearing are -
Is this new code?
No. This is not a code change, this is a marketing/name change.
So I can just install .NET Framework 3.0 binaries?
No. This is an additive release, ,NET Framework 3.0 will require .NET Framework 2.0 be installed.
If you saw Craig McMurtry's demo for the Xbox 360 finder earlier this year, you saw an interesting phenomenon.
In that example, he built out an app that queried for the availability of Xbox 360s at certain electronics resellers. In theory, once the Xbox360 was acquired, the app would have served its purpose and be deleted. There would be no v2 (until perhaps the release of the Xbox 720). This poor app's existence was to be short-lived by design, and to be honest there's something cool about the state of software and services that this could be done.
Today, I saw another one of these cool apps with an intentionally short lifespan. Checking my email this afternoon, I saw that a colleague had forwarded me a link to download “Microsoft Soccer Scoreboard” (hopefully the internationalization team called it “Microsoft Football Scoreboard” for folks installing outside the US)
World Cup is upon us, and for those of us who left the 62 inch HD screen back home to go to TechEd were wondering where we would get our World Cup scores and reviews. For those who want up to date information, scores, tables, RSS feeds, etc. You should check this out - the link is here:
-----------------------
Follow your favorite teams and players during the FIFA World Cup tournament with Microsoft Soccer Scoreboard. This fun program allows you to access all the latest tournament news and information with the click of a button! Live game data allow you to monitor your favorite teams progress in real-time. Want more? Check out your team’s fixture (schedule), standing, and news as they advance through the tournament. If you are a soccer fan, don’t miss a minute of the action.
Note: You can share this with everyone!!!
Download Microsoft Soccer Scoreboard today!
http://www.microsoft.com/downloads/details.aspx?FamilyID=df6a6e6e-21af-4786-ad1d-a38e8bfda82f&DisplayLang=en
----------------------------
For those who also want to check out the matches on someone elses big screens, you can try the Thirsty Scholar. I haven't lived in Boston for a few years, but when I was there for the last World Cup and they - and their taps - were open early, and the place was filled with fans from every country, who knew every song, and came in the type of gear you're used to seeing in Europe. I checked their web site and it looks like they're doing the same this year. http://www.thirstyscholarpub.com/
WCF and WF in Public Sector.PPT (2.16 MB)
I did a webcast today on WCF, WF, and Infocard in Public Sector today. For the Retail and Fin Serv webcasts I'd done previously, I'd had great scores (>8/9 in some cases), but there were always requests for additional vertical content after the fact.
I tried switching it up today for the pub sector session (more vertical, less core wcf/wf/identity), but the presentation just didn't click. I think I'll re-record and post a link to it when it's available, I'm pleased with the InfoCard demo, though, as I think it provides additional value.
I've attached my deck to the start of this post, as I wanted people to see the legacy empowerment section that we didn't get to review.
If you're new to the blog, I wanted to point you to some of the demos I've got online, including:
http://www.marcmercuri.com/ct.ashx?id=d0cffe95-b683-4f7c-b883-44feeb0afd43&url=http%3a%2f%2fwww.marcmercuri.com%2fDownloads%2fFinServDevCon.zip
As well as a syllabus for learning InfoCard:
http://www.marcmercuri.com/PermaLink.aspx?guid=eae5a6ef-a12e-4cfd-bd65-56fdf0b103f4
Cheers,
Marc
|