Re: Silverlight and Visual Studio 2017

[David Richards]

Umm, I still have customers using Windows Mobile.  I still have to use VS
2008.

David

"If we can hit that bullseye, the rest of the dominoes
 will fall like a house of cards... checkmate!"
 -Zapp Brannigan, Futurama

On 13 March 2017 at 17:48, Greg Keogh  wrote:

> Folks, a warning: I was just experimenting with VS2017 in a VM to be sure
> that all of my existing projects will work, before I upgrade on my real PC.
> It was going quite well until I couldn't load a Silverlight 5 project. I
> installed the developer runtime and fiddled around a bit and it still
> wasn't working, so on a whim I ran a web search and found this
> :
>
> *Silverlight projects are not supported in this version of Visual Studio.
> To maintain Silverlight applications, continue to use Visual Studio 2015.*
>
> Really! I'm shocked. That's a pain for me, as I've got SL5 apps still out
> live. And I'm not too keen on running VS 15 and 17 side-by-side. Anyway,
> just a heads-up -- *Greg K*
>

Re: Silverlight and Visual Studio 2017

[Scott Barnes]

Yeah it was never really meant to live past HD video disruption. We used to
joke there was a secret envelope that said "open when you reach 95%
ubiquity" and when you opened, it would say "delete silverlight"

But .. the actual reason was due to JavaScript arms race. Google bait and
switched IE team into a race to fastest JIT in the land and It also agreed
with Sinofskys belief system that there are just two types of devs -
scriptable apps and native. Factor in at the time Apple was getting
momentum behind apps being written in ObjectiveC and Steve Jobs taking a
huge dump on flash, simply put the conditions were ripe to kill a Plugin ..
not to mention we also went way off charter when we started to make
Silverlight standalone (out of browser is what pushed the Win vs Devdiv
battle of wills to hearing point)

So it was a combination of those factors and of course the big sticky issue
of making WPF and Silverlight arrive at some sort of parity point - which
id strongly argue is the end result of why you have the Xaml Runtime today.
In that had the windows team swallowed some of their arrogance and called
the Xaml runtime "Silverlight 8" you'd have likely had a stronger swing
back to the xaml / c# fold instead of this form of development repetive
historical cycle known as "react / angularjs".. so today all devs just shot
gunned in all different development directions resulting in a fragmented
much more disjointed developer state.

No, there isn't a single reason just lots of little cuts that are filled
with enormous amounts of distraction and little or to no coherent focused
strategy .. even today Silverlight / WPF is still in a better shape of
development potential than the crap that's being dumped in our laps. In
fact you could even take the .xap rename it to "web assembly" and reboot it
all.

But any who back to the let's write JavaScript in such a way that it
obsfucates the actual existence of JavaScript.. that or Xamarin which is a
shallow attempt at regaining the past dev experience.




On Mon., 13 Mar. 2017 at 5:39 pm, Arjang Assadi 
wrote:

> Was there ever a reason given why silver light was abandoned ? It was
> doing well at the time , just abandoning it because html 5 was popular
> seemed not a sufficient reason .
> On Mon, 13 Mar 2017 at 6:04 pm Greg Keogh  wrote:
>
> And there it is... the memorial service announcement...
>
>
> Yeah, I felt like I'd stumbled through a cemetery and tripped over a fresh
> grave with *Silverlight 2007-2017* engraved on the tombstone (like that
> scene in Back To The Future II).
>
> I'm sure it wouldn't have been too hard to leave SL project support in
> VS2017, it seems a bit cruel.
>
> *GK*
>
> --
---
Regards,
Scott Barnes
http://www.riagenic.com

Re: Silverlight and Visual Studio 2017

[Scott Barnes]

And there it is... the memorial service announcement...

"We're not saying its dead, and we're not saying its a life, what we are
saying is - it depends"... you hear those words "it depends" its the unsaid
"Its time you moved on.."


---
Regards,
Scott Barnes
http://www.riagenic.com

On Mon, Mar 13, 2017 at 4:48 PM, Greg Keogh  wrote:

> Folks, a warning: I was just experimenting with VS2017 in a VM to be sure
> that all of my existing projects will work, before I upgrade on my real PC.
> It was going quite well until I couldn't load a Silverlight 5 project. I
> installed the developer runtime and fiddled around a bit and it still
> wasn't working, so on a whim I ran a web search and found this
> :
>
> *Silverlight projects are not supported in this version of Visual Studio.
> To maintain Silverlight applications, continue to use Visual Studio 2015.*
>
> Really! I'm shocked. That's a pain for me, as I've got SL5 apps still out
> live. And I'm not too keen on running VS 15 and 17 side-by-side. Anyway,
> just a heads-up -- *Greg K*
>