 |
|||||||||
|
|||||||||
|
|
So I went to go re-watch Scott Guthrie's video illustrating the new upcoming MVC (Model-View-Controller) framework for ASP.NET when I noticed that the content is in Silverlight. That's fine, MS is trying so hard to push Silverlight as the answer to the world's problems that it's probably a requirement that all new content from MS come out as Silverlight content. Whatever, I can cope.... normally.
However... today I couldn't see the content. Why? Because I got a message that looks like this:
Ok fine, I can accep that somehow my Silverlight plug-in has expired or is no longer valid. But, isn't part of the beauty of Silverlight that it automatically updates itself like Flash has always done??? Oh.. I guess not. So, I'll just copy the URL and paste it into my browser and be done....WHAT?! The text in the dialog box is uncopyable. I can't select it. So, I have to type. the url. manually.
Then when I get to the URL, guess what I see? An error message indicating that my version of Silverlight plug-in is no longer valid and I need to ... *drumroll* .... go to the following URL to fix it!
So now, I am stuck in a scenario in which any Silverlight content I view is simply not rendered (as if it was an unrecognized pile of Javascript by the browser), and I cannot update the plug-in. I realize that Silverlight is still an up and coming technology but... come on... If this is a foreshadowing of the user experience people are going to get when Silverlight makes it prime-time ... what's going to keep developers from just saying to hell with it and using Flex? Well, the fact that Silverlight is .NET but... It would just be nice if Microsoft actually got the user experience right for once. I don't care if it's beautiful, I don't care if it's even smooth, but dammit it should at least WORK.
I have the same problem....
WTF, you ask? Ain't that Windows Technology Foundation? ;-)
No jokes aside: Me too I'm waiting for the 1.1 and then we'll see.
Did you try uninstalling Silverlight from the Add/Remove Programs?
If you have to uninstall from add/remove programs, doesn't that negate the
whole "awesome automatic updater" piece? I went into add/remove programs,
uninstalled Silverlight, it failed but let me remove the installation entry
anyway. Then I had to go back to the Silverlight website and install the
1.0 (not 1.1!) Silverlight control. I could NOT get Silverlight 1.1 to
install after that. As I said in my blog, it would be nice if MS JUST ONCE
got User Experience right.
Why do people consistently jump up and down when something odd happens with
*beta* software? Why are people so consistently dumb? I put it down to
our limited attention society. Complain first, think later. (Or just
forget about the thinking bit altogether)
1.0 is not beta. Next time read more closely before casting stones
Nowhere in your post do you refer to the version. I am still not convinced
you were running version 1.0
Actually, what I stated was that suddenly my v1.0 component stopped
working. I had to un-install it and re-install it to get it to work again,
and that process was far too complex for a released, v1.0 product. After
everything was working, I tried to upgrade to the v1.1 component and
couldn't. The reason this is significant is that when 1.0 was a beta and
1.1 was still CTP, both of them worked together, both worked flawlessly,
and the installation method for both of them was quite simple. The problem
is that MS yet again screwed the user experience when they rolled build
numbers. That's the problem. If one of the huge selling points of
Silverlight 1.0 (not 1.1) is that it can be seamlessly upgraded in-place
(this is one thing MS has touted multiple times), then why is it that it
cannot be seamlessly upgraded in place? I was running the RTM version of
Silverlight 1.0 before - so obviously MS rolled a build number on the RTM
bits post-release to do an update, and that upgrade failed miserably.
