Expression Design 4 Issues With Windows 8

Expression Design 4 Issues With Windows 8 by PeekMySite-Peter

Closed

as Won't Fix Help for as Won't Fix

Type:	Bug
ID:	755390
Opened:	7/24/2012 10:27:19 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

Installing Expression product lines under Windows 8 has a considerable number of issues, especially with Expression Design, where the application is not rendering properly but of greater importance, is that with Xaml or WPF output files, there is a consistent error with rgba color definition. Example: Transparency is F4, under Windows 8 transparency is E2, and there may or may not be a total % difference in color definitions, as well.

Details (expand)

Design

Web 4 SP2

Bug

I'm hoping Microsoft will give Expression Pro and Studio an update overhaul or complete new run because Expression and intellisense, since its introduction, has replaced approximately 10 to 12, other then Microsoft, Web developing applications, I used in past. So, now, I no longer invest in updates of older non Microsoft applications and rely heavily on Expression.

Most importantly, I'm now translating Expression Design Xaml and WPF 4 output into HTML 5 canvas objects. To the best of my knowledge, there are no HTML 5 tools which will produce or provide for interpretation of Xml into HTML 5 canvas vector design object, so color discrepancy and Expression as the only design software at my desk, if Expression will be updated is becoming a considerable concern.

I'd like to point out, Xaml and WPF translated at the client into many grouped HTML 5 canvas objects will produce equal quality design, yet will render many canvas objects faster or will out perform the Silverlight plug-in. This involves a considerable study of Xaml and WPF, such as could be applied server-side and translated to HTML 5 and CSS 3, in planning to default Web pages to vector.

0 attachments

We recently announced that we are discontinuing development of Expression Design. You can read the full announcement on our community page at http://msdn.microsoft.com/expression. Because this product is no longer in development, we are closing all outstanding bugs.