I'd love to see more Windows applications like that

i recvive crash in RT

Firma problema:

  Nome evento problema: CLR20r3

  Firma problema 01: metrotwit.exe

  Firma problema 02: 0.1.0.5

  Firma problema 03: 4c04af36

  Firma problema 04: TweetSharp.Twitter

  Firma problema 05: 1.0.0.0

  Firma problema 06: 4bfa2f13

  Firma problema 07: 243

  Firma problema 08: 186

  Firma problema 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB

  Versione SO: 6.1.7600.2.0.0.256.1

  ID impostazioni locali: 1040

  Informazioni aggiuntive 1: 0a9e

  Ulteriori informazioni 2: 0a9e372d3b4ad19135b953a78882e789

  Ulteriori informazioni 3: 0a9e

  Ulteriori informazioni 4: 0a9e372d3b4ad19135b953a78882e789

Dovella said:

Congrat Long Z.

 

i recvive crash in RT

 

Firma problema:

  Nome evento problema: CLR20r3

  Firma problema 01: metrotwit.exe

  Firma problema 02: 0.1.0.5

  Firma problema 03: 4c04af36

  Firma problema 04: TweetSharp.Twitter

  Firma problema 05: 1.0.0.0

  Firma problema 06: 4bfa2f13

  Firma problema 07: 243

  Firma problema 08: 186

  Firma problema 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB

  Versione SO: 6.1.7600.2.0.0.256.1

  ID impostazioni locali: 1040

  Informazioni aggiuntive 1: 0a9e

  Ulteriori informazioni 2: 0a9e372d3b4ad19135b953a78882e789

  Ulteriori informazioni 3: 0a9e

  Ulteriori informazioni 4: 0a9e372d3b4ad19135b953a78882e789

Firma problema:

  Nome evento problema: CLR20r3

  Firma problema 01: metrotwit.exe

  Firma problema 02: 0.1.0.5

  Firma problema 03: 4c04af36

  Firma problema 04: TweetSharp.Twitter

  Firma problema 05: 1.0.0.0

  Firma problema 06: 4bfa2f13

  Firma problema 07: 243

  Firma problema 08: 186

  Firma problema 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB

  Versione SO: 6.1.7600.2.0.0.256.1

  ID impostazioni locali: 1040

  Informazioni aggiuntive 1: 0a9e

  Ulteriori informazioni 2: 0a9e372d3b4ad19135b953a78882e789

  Ulteriori informazioni 3: 0a9e

  Ulteriori informazioni 4: 0a9e372d3b4ad19135b953a78882e789

I made it crash in under 10 seconds, but it does have exception handling

BorekB said:

The text is blurry which I find weird for a text-centric application.

This is a Silverlight problem (I think this is a SLOOB) that Microsoft need to fix

Dovella said:

Congrat Long Z.

 

i recvive crash in RT

 

Firma problema:

  Nome evento problema: CLR20r3

  Firma problema 01: metrotwit.exe

  Firma problema 02: 0.1.0.5

  Firma problema 03: 4c04af36

  Firma problema 04: TweetSharp.Twitter

  Firma problema 05: 1.0.0.0

  Firma problema 06: 4bfa2f13

  Firma problema 07: 243

  Firma problema 08: 186

  Firma problema 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB

  Versione SO: 6.1.7600.2.0.0.256.1

  ID impostazioni locali: 1040

  Informazioni aggiuntive 1: 0a9e

  Ulteriori informazioni 2: 0a9e372d3b4ad19135b953a78882e789

  Ulteriori informazioni 3: 0a9e

  Ulteriori informazioni 4: 0a9e372d3b4ad19135b953a78882e789

Firma problema:

  Nome evento problema: CLR20r3

  Firma problema 01: metrotwit.exe

  Firma problema 02: 0.1.0.5

  Firma problema 03: 4c04af36

  Firma problema 04: TweetSharp.Twitter

  Firma problema 05: 1.0.0.0

  Firma problema 06: 4bfa2f13

  Firma problema 07: 243

  Firma problema 08: 186

  Firma problema 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB

  Versione SO: 6.1.7600.2.0.0.256.1

  ID impostazioni locali: 1040

  Informazioni aggiuntive 1: 0a9e

  Ulteriori informazioni 2: 0a9e372d3b4ad19135b953a78882e789

  Ulteriori informazioni 3: 0a9e

  Ulteriori informazioni 4: 0a9e372d3b4ad19135b953a78882e789

There's a bug report form. Why not use it?

It could be slightly smoother moving the columns around -- but otherwise, this app appears great.

fknight said:

Thank you for putting together an application that defaults to requiring me to opt in to notification sounds. This is the first time I've seen a sensible default to such a feature. Additionally, the fact that I don't have to wait several annoyingly long seconds for the tooltips to appear on the buttons in this application is a welcome aspect as well. A lot of app developers can learn from this application's non-annoying design.

 

It could be slightly smoother moving the columns around -- but otherwise, this app appears great.

You're welcome

longzheng said:

fknight said:

*snip*

You're welcome

Thanks. It obviously reminds me of Tweetdeck, but it's not as "in your face" as that application. The notification windows also tend to not appear as much of a disturbance as other applications. I can't wait to see how this application progresses in the future.

BorekB said:

The text is blurry which I find weird for a text-centric application.

The blurry text is indeed strange, considering it is a WPF 4 application. Also, I wonder if this could have been done in Silverlight 4 (and if so, what the motivation was to use WPF instead of Silverlight).

vesuvius said:

BorekB said:

*snip*

This is a Silverlight problem (I think this is a SLOOB) that Microsoft need to fix

Blurry text was fixed in WPF 4 which this app supposedly uses.

mawcc said:

BorekB said:

*snip*

The blurry text is indeed strange, considering it is a WPF 4 application. Also, I wonder if this could have been done in Silverlight 4 (and if so, what the motivation was to use WPF instead of Silverlight).

I think they did it because of the task bar integration.

longzheng said:

fknight said:

*snip*

You're welcome

Hi Long, any insight into why the text is blurry?

This program / .Net 4 is lame because it require a reboot. A reboot just to install a twitter client ... wow.

intelman said:

I'd like to see Live Messenger get the Metro Treatment. Flat fonts, no shadows, looks really nice.

 

This program / .Net 4 is lame because it require a reboot. A reboot just to install a twitter client ... wow.

Didn't reboot on any of my machines. Maybe you just didn't have .NET 4.0 installed?

PaoloM said:

intelman said:

*snip*

Didn't reboot on any of my machines. Maybe you just didn't have .NET 4.0 installed?

Even if that is the case, that is still pretty lame.

intelman said:

PaoloM said:

*snip*

Even if that is the case, that is still pretty lame.

That you have to reboot to replace system level components?

I guess all systems are lame, then...

intelman said:

PaoloM said:

*snip*

Even if that is the case, that is still pretty lame.

Not really, anyway..

Visually its certainly 'inspired' by metro, by that I mean, pretty much a ripoff, however I think that was the aim, to try and see if some UI unity could be created, and the UI/UX works great already.

The app works really well, and its really nice to see clickonce being used, not only does it have a fantastic install experience, but uninstalling is great too (I'm not really a twitter desktop client user).

The funny thing is this makes me almost depressed, clickonce and wpf has been available for some time now, and offers a fantastic app experience on windows, but isn't at all the experience people think of when windows is mentioned.. I'm pretty sick of the PC hardware/software campers who are willing to make meagre, dull windows software/hardware. That said, I guess with so many 'cooks' the vision for the windows platform is insanely vague, and I guess that's why apple are doing so well by having their own defined universe.

longzheng said:

fknight said:

*snip*

You're welcome

I don't use twitter, but downloaded to see that zune UI. You guys did awesome job, really like how smooth it all works. How long did you guys cook this thing? Did you follow any ui guidelines or just copied zune software feel?

C

BorekB said:

longzheng said:

*snip*

Hi Long, any insight into why the text is blurry?

 

I find the current text rendering to be pretty good although we have had some users say the text is blurry. We'll keep playing with it but it's my understanding most people find it acceptable.

RoyalSchrubber said:

longzheng said:

*snip*

I don't use twitter, but downloaded to see that zune UI. You guys did awesome job, really like how smooth it all works. How long did you guys cook this thing? Did you follow any ui guidelines or just copied zune software feel?

We definitely looked at the Zune desktop UI as the starting point to do a Metro-like experience in a desktop client. We also draw a lot of inspiration from the Metro guidelines on WP7S, but obviously not all of that is applicable on the desktop.

In areas like the notifications, we're trying some UX concepts of our own with the "Metro" philosophy in mind.

In anycase the text rendering in this client is beautiful. It is probably the best looking text I've seen on my LCD ever. I really want to see this expanded to other clients, especially IM clients. Someone needs to make a great looking IM client.

Oh and after the reboot for .NET 4, that stupid optimization process really destroyed my PC, I thought the twitter client had horrible performance, turns out it was just .NET...

longzheng said:

RoyalSchrubber said:

*snip*

We definitely looked at the Zune desktop UI as the starting point to do a Metro-like experience in a desktop client. We also draw a lot of inspiration from the Metro guidelines on WP7S, but obviously not all of that is applicable on the desktop.

 

In areas like the notifications, we're trying some UX concepts of our own with the "Metro" philosophy in mind.

This could be a dumb question but can MetroTwit handle more than one account simultaneously?

Brilliant client BTW. Simple, elegant, stupidly easy to read and use. Well done Long.

Ion Todirel said:

Search at the bottom, blasphemy!

Search at the bottom does seem a bit odd, and the search box is a little on the large side for my liking (especially given how short tweets are!) but overall I'm liking it. Have had a few weird redraw issues (bug report submitted) but maybe that is just my machine.

longzheng said:

BorekB said:

*snip*

I find the current text rendering to be pretty good although we have had some users say the text is blurry. We'll keep playing with it but it's my understanding most people find it acceptable.

The issue with the blurry text seems to boil down to a sub-optimal choice of font and maybe also not using the new text rendering options available in WPF 4.

http://10rem.net/blog/2010/06/06/wpf-and-silverlight-choose-your-fonts-and-text-rendering-options-wisely

mawcc said:

longzheng said:

*snip*

The issue with the blurry text seems to boil down to a sub-optimal choice of font and maybe also not using the new text rendering options available in WPF 4.

 

http://10rem.net/blog/2010/06/06/wpf-and-silverlight-choose-your-fonts-and-text-rendering-options-wisely

That article suggests using Segoe UI instead of Segoe WP.

I suggest Segoe UI Light instead.

Edit: I meant for the title/headers only. Tweets in Segoe UI please.

Ion Todirel said:

Search at the bottom, blasphemy!

It's like that in Windows too, unless you move the taskbar to the top (or sides)

AdamSpeight2008 said:

Why hasn't anyone commented on the name? Sound like a French Underground (Metro)  Idiot. (Twit)

Sounds more like a metro-sexual twit to me.

But then again, isn't that somewhat appropriate? In fact, I'd like to propose that we call everyone who uses twitter a twit from now on.

mawcc said:

longzheng said:

*snip*

The issue with the blurry text seems to boil down to a sub-optimal choice of font and maybe also not using the new text rendering options available in WPF 4.

 

http://10rem.net/blog/2010/06/06/wpf-and-silverlight-choose-your-fonts-and-text-rendering-options-wisely

Segoe WP for Windows Phone works well because the device runs at a high dpi.  For the default 96dpi of Windows, Segoe UI with its hints work better.

Also WPF4 brought in updated font handling, also be sure to snap to device pixels.

But WPF4 will not have as crisp a font rendering that Direct Text or standard GDI+ does.  But WPF works best for scalable DPI, and you could re-factor the code for the MetroTwit Windows Phone app I know you will be planning as I type!

littleguru said:

The text is exactly as blurry as the VS 2010 beta code editor was. I can't read it without getting a headache...

The fix is really simple. All they need to do is add TextOptions.TextFormattingMode="Display" to every window, and preferably also change the font back to Segoe UI.

Anyway, that's just my point of view. It's clear that you've made a nice client that looks just as nice as, if not nicer than, other twitter clients.

Actually, it looks as if you'll have taken care of my main concern if you just hide the client from the taskbar when minimized.

Sven Groot said:

littleguru said:

*snip*

The fix is really simple. All they need to do is add TextOptions.TextFormattingMode="Display" to every window, and preferably also change the font back to Segoe UI.

Just wanted to follow up on the fonts stuff.

In terms of the "fuzzy" text problem, this is actually subject to personal preference and the technical specifications of your monitor. Many people (myself included) actually don't have any problems with the "current" font rendering. I can agree it's sort of blurry, but it's readable (better than earlier WPF font rendering) and I actually enjoy the smoother aesthetics. At the same time, I can see why some people can find a problem with it.

In terms of a "solution", it's actually not that straight forward. Scott Hanselman and Pete Brown reached out to me to work on this issue specifically. TextFormattingMode and TextRenderingMode were one of the first things I tried and it really didn't have any positive effect. To cut a long story short, it actually turns out enabling transparency on the application disables ClearType font rendering application-wide.

We required transparency because of the custom chrome drop shadow we've implemented so currently we need to solve that issue to solve this fonts issue.

Rest assured though, we're looking into this and will seek a solution to satisfy everyone.

longzheng said:

Sven Groot said:

*snip*

Just wanted to follow up on the fonts stuff.

 

In terms of the "fuzzy" text problem, this is actually subject to personal preference and the technical specifications of your monitor. Many people (myself included) actually don't have any problems with the "current" font rendering. I can agree it's sort of blurry, but it's readable (better than earlier WPF font rendering) and I actually enjoy the smoother aesthetics. At the same time, I can see why some people can find a problem with it.

 

In terms of a "solution", it's actually not that straight forward. Scott Hanselman and Pete Brown reached out to me to work on this issue specifically. TextFormattingMode and TextRenderingMode were one of the first things I tried and it really didn't have any positive effect. To cut a long story short, it actually turns out enabling transparency on the application disables ClearType font rendering application-wide.

 

We required transparency because of the custom chrome drop shadow we've implemented so currently we need to solve that issue to solve this fonts issue.

 

Rest assured though, we're looking into this and will seek a solution to satisfy everyone.

Wild idea, and it sounds impossible to me even typing it, but I shall...

What about having two windows/forms open, one transparent for the drop shadow, the other opaque, and tie the position of the two windows/forms to each other, so you get the same kind of effect?

I'll go and hide now...

longzheng said:

Sven Groot said:

*snip*

Just wanted to follow up on the fonts stuff.

 

In terms of the "fuzzy" text problem, this is actually subject to personal preference and the technical specifications of your monitor. Many people (myself included) actually don't have any problems with the "current" font rendering. I can agree it's sort of blurry, but it's readable (better than earlier WPF font rendering) and I actually enjoy the smoother aesthetics. At the same time, I can see why some people can find a problem with it.

 

In terms of a "solution", it's actually not that straight forward. Scott Hanselman and Pete Brown reached out to me to work on this issue specifically. TextFormattingMode and TextRenderingMode were one of the first things I tried and it really didn't have any positive effect. To cut a long story short, it actually turns out enabling transparency on the application disables ClearType font rendering application-wide.

 

We required transparency because of the custom chrome drop shadow we've implemented so currently we need to solve that issue to solve this fonts issue.

 

Rest assured though, we're looking into this and will seek a solution to satisfy everyone.

Actually it looks blurry on 7 different computer displays, ranging from 4 laptops to 2 hi-end IPS panels, so I don't buy that argument, it's blurry, period

mdtauk said:

longzheng said:

*snip*

Wild idea, and it sounds impossible to me even typing it, but I shall...

 

What about having two windows/forms open, one transparent for the drop shadow, the other opaque, and tie the position of the two windows/forms to each other, so you get the same kind of effect?

 

I'll go and hide now...

Even wilder idea: use the system chrome.

I don't like any application that doesn't use the system chrome. This includes e.g. WLM and older versions of WMP (where I always turn the chrome on first thing). I also greatly dislike that all of the Silverlight 4 OOB apps I've seen so far use a custom chrome (I'm not sure if they can have the default chrome or not).

If I used Twitter (which I don't), I would likely not use this app because of its use of a custom window chrome.

Sven Groot said:

mdtauk said:

*snip*

Even wilder idea: use the system chrome.

 

I don't like any application that doesn't use the system chrome. This includes e.g. WLM and older versions of WMP (where I always turn the chrome on first thing). I also greatly dislike that all of the Silverlight 4 OOB apps I've seen so far use a custom chrome (I'm not sure if they can have the default chrome or not).

 

If I used Twitter (which I don't), I would likely not use this app because of its use of a custom window chrome.

QFT

For me, it's much more than the aesthetic, an application's window must work the same as the host OS. This includes windowing controls, context menus, and things like Aero Snap. Photoshop is a big violator for breaking Snap. Chrome (the browser) is out because I hate not having (window) chrome to grab on to. Zune gets partial points for obeying snap, but instead of allowing the OS to show the transparent preview of a Snap operation, it immediately reflows the application. I'd rather have the consistency.

kettch said:

Sven Groot said:

*snip*

QFT

 

For me, it's much more than the aesthetic, an application's window must work the same as the host OS. This includes windowing controls, context menus, and things like Aero Snap. Photoshop is a big violator for breaking Snap. Chrome (the browser) is out because I hate not having (window) chrome to grab on to. Zune gets partial points for obeying snap, but instead of allowing the OS to show the transparent preview of a Snap operation, it immediately reflows the application. I'd rather have the consistency.

I like the Chrome, and think Expression Blend lead the way, even though there is no placating you, hence, I know not why I bothered to post.

It is differentiated UI, casting away "prior art" and giving designers complete control.

Sven Groot said:

mdtauk said:

*snip*

Even wilder idea: use the system chrome.

 

I don't like any application that doesn't use the system chrome. This includes e.g. WLM and older versions of WMP (where I always turn the chrome on first thing). I also greatly dislike that all of the Silverlight 4 OOB apps I've seen so far use a custom chrome (I'm not sure if they can have the default chrome or not).

 

If I used Twitter (which I don't), I would likely not use this app because of its use of a custom window chrome.

I don't mind a custom window chrome, as long as everything is consistent, and custom

Ion Todirel said:

Sven Groot said:

*snip*

I don't mind a custom window chrome, as long as everything is consistent, and custom

For me it's also more about consistency rather than aesthetics per se. It's just inviting trouble, because you have to replicate functionality that everyone is used to, and do it in such a way that you're consistent with current and future versions of Windows.

This case is a perfect example. If you have no window border, you don't have a drop shadow. If you try to create one, you apparently mess up ClearType in WPF. All problems that wouldn't even have occurred if you just stuck to the regular window chrome. Oh, and I mentioned consistency with future versions: what if those use a different drop shadow or none at all; this app will look weird then. Does MetroTwit try to draw a drop shadow in XP, or the basic or classic theme, or other situations where windows wouldn't normally have a drop shadow?

And what if I disabled the window shadows in the performance settings (maybe because my graphics card is too slow for them)? Does MetroTwit obey that setting?

These are all silly little things that will annoy your users and that you don't need to worry about if you just use a standard window border.

Sven Groot said:

Ion Todirel said:

*snip*

For me it's also more about consistency rather than aesthetics per se. It's just inviting trouble, because you have to replicate functionality that everyone is used to, and do it in such a way that you're consistent with current and future versions of Windows.

 

This case is a perfect example. If you have no window border, you don't have a drop shadow. If you try to create one, you apparently mess up ClearType in WPF. All problems that wouldn't even have occurred if you just stuck to the regular window chrome. Oh, and I mentioned consistency with future versions: what if those use a different drop shadow or none at all; this app will look weird then. Does MetroTwit try to draw a drop shadow in XP, or the basic or classic theme, or other situations where windows wouldn't normally have a drop shadow?

 

And what if I disabled the window shadows in the performance settings (maybe because my graphics card is too slow for them)? Does MetroTwit obey that setting?

 

These are all silly little things that will annoy your users and that you don't need to worry about if you just use a standard window border.

No I agree with you about the chrome, we really didn't want to get "rid" of it and do our own, but in reality, the glass frame really doesn't not fit with the Metro look and feel.

Ion Todirel said:

longzheng said:

*snip*

Actually it looks blurry on 7 different computer displays, ranging from 4 laptops to 2 hi-end IPS panels, so I don't buy that argument, it's blurry, period

It looks perfect on my IPS panel, on some generic Dell 24 inch panel at school, and great on my old Dell Laptop, but horrible on my tablet

I really love the look of the text on the panels where the text looks good. I prefer it to anyting else I've seen on Windows.

Pehaps it is heavily DPI dependent.

Text remains a pretty big issue on Windows. There are so many font renderings, none are consistant. Cleartype needs an overhaul. Or directwrite needs to be forced. Something needs to happen.

intelman said:

Ion Todirel said:

*snip*

It looks perfect on my IPS panel, on some generic Dell 24 inch panel at school, and great on my old Dell Laptop, but horrible on my tablet

I really love the look of the text on the panels where the text looks good. I prefer it to anyting else I've seen on Windows.

 

Pehaps it is heavily DPI dependent.

 

Text remains a pretty big issue on Windows. There are so many font renderings, none are consistant. Cleartype needs an overhaul. Or directwrite needs to be forced. Something needs to happen.

Something needs to happen

I wish we could all get 320ppi displays and forget about ClearType.

/no, really.

Sven Groot said:

Ion Todirel said:

*snip*

For me it's also more about consistency rather than aesthetics per se. It's just inviting trouble, because you have to replicate functionality that everyone is used to, and do it in such a way that you're consistent with current and future versions of Windows.

 

This case is a perfect example. If you have no window border, you don't have a drop shadow. If you try to create one, you apparently mess up ClearType in WPF. All problems that wouldn't even have occurred if you just stuck to the regular window chrome. Oh, and I mentioned consistency with future versions: what if those use a different drop shadow or none at all; this app will look weird then. Does MetroTwit try to draw a drop shadow in XP, or the basic or classic theme, or other situations where windows wouldn't normally have a drop shadow?

 

And what if I disabled the window shadows in the performance settings (maybe because my graphics card is too slow for them)? Does MetroTwit obey that setting?

 

These are all silly little things that will annoy your users and that you don't need to worry about if you just use a standard window border.

In case anyone was wondering, we fixed both custom chrome issues and ClearType in our latest release

longzheng said:

Sven Groot said:

*snip*

In case anyone was wondering, we fixed both custom chrome issues and ClearType in our latest release

But still the rendering is not as good as it could be. Could you drop Zegoe (that's not properly hinted at 96dpi) and use Segoe UI?

longzheng said:

Sven Groot said:

*snip*

In case anyone was wondering, we fixed both custom chrome issues and ClearType in our latest release

Cool Long, will have to update and see how it looks.... nice app and i think if the rendering is fixed it will be great!

PaoloM said:

longzheng said:

*snip*

But still the rendering is not as good as it could be. Could you drop Zegoe (that's not properly hinted at 96dpi) and use Segoe UI?

We already do use Segoe UI for the tweets

blowdart said:

Now if only there was proper retweeting (what is this, 2009?) picture service support, and url shortening and working favouriting and I would switch off Seesmic. The fonts do look better now.

You want the moon on a stick, you do.

rhm said:

blowdart said:

*snip*

You want the moon on a stick, you do.

Heh. Or just add MEF extensibility points for services and I'll knock out my own.

We're getting close to a v1 release with streaming and multi-account support but I think we're far more polished than where how it was when this thread started.

Feedback of course always welcomed. http://www.metrotwit.com/

 Great job!!

Following errors were detected during this operation.
 * [03/05/2011 1:26:22 PM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
  - File, beep.mp3, has a different computed hash than specified in manifest.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
   at System.Deployment.Application.ComponentVerifier.VerifyComponents()
   at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
   at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
   at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

8 hours ago, Minh wrote

Hey Long, ... if you had coded this w/ HTML, you'd be $40-50 mils richer today?

2 hours ago, longzheng wrote

*snip*Except we bet on WPF

Any regrets?

1 hour ago, Ray7 wrote

*snip*

 

Any regrets?

Sure. There's consequences but there's also benefits. I just wish we had better "support" to shift the balance.