Skip to main content

What does Vista MCE ("Diamond") look like?

Just watched this on Charlie Owens blog.

This is a tour of Windows Vista Media Centre (code name Diamond). I have to say that I'm mildly impressed but I believe that with "consumer" grade products like this (and by consumer grade I mean ready for Joe Public - no computer science degree required to operate) the proof is in the long term experience with the product; i.e does it become indispensible or did you get frustrated with it because of stability/reliability issues? "Eye-candy" stuff is great but if it forgets to record a TV program it will get the boot! I've been pleased with MCE2005 so working on the assumption this will be a "better" product I hope this will become a truely indispensible integral part of my home.

Great video though demonstrating the features and improvements and I can't wait to get some long term experience with it myself. I'm holding off buying a new media centre PC until "Diamond" is released.

Comments

Anonymous said…
sorry for off the topic post.I am woking on an MSN bot and using dotMSN lib for .net 1.1.

I am having difficulty to handle users who add my bot Id.it does appear in reverseList ,even in Forward List(FL) if I call AddContact() method.My bot client doesnt get notified about new message sent by a user.

there is an option of Notify "DotMSN.MSNNotifyPrivacy.AutomaticAdd"
But I dont know how to add it.Can you guide me ?


Thanks

adnan[kadnanATgmailDOTcom
16 Sept 2006, 08:53:00
Unknown said…
If I understand you correctly you are successfully having the contacts added on the FL & RL but the bot is not receiving a message from the contact. I’ve looked at some code I have for a bot I worked on a while ago and think the problem might be in how you are wiring up the event handlers to send a message back to the contact. I’ve not seen/used the DotMSN.MSNNotifyPrivacy.AutomaticAdd feature you mention.

So once you have your main dotMSN messenger object you need to wire up the ConversationCreated handler.

You should do this only once

_messenger.ConversationCreated += new ConversationCreatedHandler(Messenger_ConversationCreated);

Then inside this event handler you need to wire up the new conversations “message received” handler. This will fire every time a contact opens a message window and types a message to the bot

private void Messenger_ConversationCreated(DotMSN.Messenger sender, ConversationEventArgs e)
{
e.Conversation.MessageReceived += new DotMSN.Conversation.MessageReceivedHandler(Conversation_MessageReceived);
}

Then finally this event handler is where you will get the message text from your contact. Use the sender.SendMessage method to send any text back to the contact, in the example below it simple returns the message they sent to the bot. This will fire for every message sent by the contact.

private void Conversation_MessageReceived(Conversation sender, MessageEventArgs e)
{
// this will send a message back to the sender

sender.SendMessage(string.format(“Thanks for your message of: {0}”, e.Message.Text));
}
20 Sept 2006, 09:01:00
Post a Comment

Popular posts from this blog

Walk-Thru: Using Wolfpack to automatically deploy and smoke test your system

First, some history... The advent of NuGet has revolutionised many many aspects of the .Net ecosystem; MyGet, Chocolatey & OctopusDeploy to name a few solutions building upon its success bring even more features to the table. I also spotted that NuGet could solve a problem I was having with my OSS System Monitoring software Wolfpack ; essentially this is a core application framework that uses plugins for extension ( Wolfpack Contrib ) but how to unify, standardise and streamline how these plugins are made available? NuGet to the rescue again - I wrapped the NuGet infrastructure (I deem NuGet to be so ubiquitous and stable that is has transcended into the software "infrastrucuture" hall of fame) with a new OSS project called Sidewinder . Sidewinder allows me to wrap all my little extension and plugins in NuGet packages and deploy them directly from the Wolfpack application - it even allows me to issue a new version of Wolfpack and have Wolfpack update itself, sweet huh...
5 comments
Read more

Configuration in .Net 2.0

11-Dec-2007 Update I've updated this post to fix the broken images and replaced them with inline text for the example xml and accompanying C# code. This post has been by far the most hit on this blog and along with the comments about the missing images I thought it was time to update it! Whilst recreating the examples below I zipped up the working source code and xml file and loaded this onto my Project Distributor site - please download it to get a full working custom configuration to play with! Just click on the CustomConfigExampleSource link on the right hand side, then the "Source" link to get the zip. We are in the process of converting our codebase to .Net 2.0. We've used Enterprise Library to great effect so decided that we should continue with this in the form of the Jan 2006 release which targets 2.0 and I've got the job of porting our Logging, Data Access etc wrappers to EntLib 2.0. ...And so far so good - the EntLib docs aren't bad and the migrati...
9 comments
Read more

Deployment - the final (.Net) frontier

[Update 19th Apr 2012]  - mission complete!...v2.4.0 of Wolfpack has been released and this includes a new set of plugins that can automatically download a NuGet package then execute a deployment tool (eg: DropkicK, MSBuild.exe) - it can even run NUnit tests (via the console runner). Wolfpack v2.4.0 Wolfpack.Contrib.Deployment [Original Post] Another day, another project and deployment raises its head... Thinking that this problem must have been cracked by now I had a look around the .Net landscape and found two interesting solutions. Octopus Deploy - a .Net convention based deployment system using NuGet packages, loosely based on AppHarbour's approach. DropkicK (aka DK) - another awesome initiative from Dru Sellers et al. I like the simplicity of Octopus but also like DK's  fluent code based deployment. Hmmm, this has got me thinking - Wolfpack could easily be adapted to be used as a deployment agent. Wolfpack can already monitor a NuGet feed for new pac...
6 comments
Read more