[Update: False Alarm] Windows Live Wave 4 Icon Spotted
So far Windows Live Essentials and Live Services had the Windows flag as their logo. With Wave 4 Microsoft seems to be doing some branding for the suite. The Favicon for Microsoft’s Live Wave 4 preview website gives a glimpse of the icon. It’s just a ‘4’ superimposed on the Windows flag.
Whether this remains as a favicon or becomes a part of the branding is anybody’s guess. Microsoft is expected to show a preview of their Wave 4 today on Windows Live Preview. However, LiveSide and LiveSino have screenshots what is expected to be shown.
Live Messenger in Wave 4 is to have the following features:
- Tabbed conversations
- Badges
- Receive social updates from Hotmail
- Inline commenting
- Synchronized status updates
Update: now that the website is up and the Windows Live image and icon on the website does not have the 4 super-imposed, I guess it is just for the favicon. Sigh.
The WL Preview site is down …
Server Error in ‘/’ Application.
——————————————————————————–
Sequence contains no elements
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.InvalidOperationException: Sequence contains no elements
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[InvalidOperationException: Sequence contains no elements]
System.Linq.Enumerable.First(IEnumerable`1 source) +730976
System.Data.Objects.ELinq.ObjectQueryProvider.b__0(IEnumerable`1 sequence) +40
System.Data.Objects.ELinq.ObjectQueryProvider.ExecuteSingle(IEnumerable`1 query, Expression queryRoot) +59
System.Data.Objects.ELinq.ObjectQueryProvider.System.Linq.IQueryProvider.Execute(Expression expression) +109
System.Linq.Queryable.First(IQueryable`1 source) +269
Wave.Localization.LocaleSettings.get_CurrentLocaleID() in Localization.cs:50
Wave.Models.ChannelEntityContext..cctor() in ChannelRepository.cs:333
[TypeInitializationException: The type initializer for ‘Wave.Models.ChannelEntityContext’ threw an exception.]
Wave.Models.ChannelRepository.ChannelExists(String channelName) in ChannelRepository.cs:204
Wave.Controllers.ChannelController.Index(String channelName) in ChannelController.cs:41
lambda_method(ExecutionScope , ControllerBase , Object[] ) +86
System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, Object[] parameters) +17
System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters) +178
System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters) +24
System.Web.Mvc.c__DisplayClassd.b__a() +53
System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation) +258
System.Web.Mvc.c__DisplayClassf.b__c() +20
System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodWithFilters(ControllerContext controllerContext, IList`1 filters, ActionDescriptor actionDescriptor, IDictionary`2 parameters) +193
System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName) +300
System.Web.Mvc.Controller.ExecuteCore() +104
System.Web.Mvc.ControllerBase.Execute(RequestContext requestContext) +36
System.Web.Mvc.ControllerBase.System.Web.Mvc.IController.Execute(RequestContext requestContext) +7
System.Web.Mvc.c__DisplayClass8.b__4() +34
System.Web.Mvc.Async.c__DisplayClass1.b__0() +21
System.Web.Mvc.Async.c__DisplayClass8`1.b__7(IAsyncResult _) +12
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +53
System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult) +30
System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.EndProcessRequest(IAsyncResult result) +7
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +8678910
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155
——————————————————————————–
Version Information: Microsoft .NET Framework Version:2.0.50727.4200; ASP.NET Version:2.0.50727.4016
They were having some issues when the launched the site. I believe it’s been solved now. A lot of people were facing the error.
I just dumped WLM for Yahoo Messenger because they dumped XP support. Howsoever stone age XP might be, fact remains it’s in use and what’s in use MUST BE SUPPORTED.
most software for the home consumer is now dumping XP. IE9 – only XP, Live Essentials – only XP. About time they killed it. Backwards compatibility isn’t exactly as easy as we think.