Reply to thread

Message

<blockquote data-quote="AbdulAlhazred" data-source="post: 5729547" data-attributes="member: 82106">Well, clearly 'dead', particularly with MS, doesn't mean &quot;poof it vanishes from existence&quot;. They're not going to supply new dev tools for it past SL5, and presumably they're not going to add new features etc and eventually they'll EOL the entire runtime. They're likely to continue to provide the existing tool support until then as well, or at least up to some release of MSVS in the same time frame. That could be 5 years from now, but likely it will be somewhat sooner. Clearly SL will remain an option for people that are determined to stick with what works for them for quite some time. It is just going to be in the same category with various older toolsets that will still WORK if you use them and that runtime support continues to possible for. It is just going to be a better idea to move on to whatever is next as soon as it becomes feasible. Really, my impression of MS's current development platform strategy is that it is a bit 'confused' at the moment. Clearly SL was envisaged as a long-term strategy and now it is equally clearly no longer so. It is even rather unclear exactly where they are positioning .NET and managed code in general going forward. From what we can tell it is likely to follow Java into the abyss of &quot;server side technology&quot; with some limited support for client facing apps if you're really determined. Whatever is coming next is hard to fathom, some mix of native code and HTML5 based tools. Maybe the IE10 runtime will become basically the runtime for 'managed' non-native type stuff going forward. Who really knows? I'm not sure MS knows.</blockquote>

[QUOTE="AbdulAlhazred, post: 5729547, member: 82106"] Well, clearly 'dead', particularly with MS, doesn't mean "poof it vanishes from existence". They're not going to supply new dev tools for it past SL5, and presumably they're not going to add new features etc and eventually they'll EOL the entire runtime. They're likely to continue to provide the existing tool support until then as well, or at least up to some release of MSVS in the same time frame. That could be 5 years from now, but likely it will be somewhat sooner. Clearly SL will remain an option for people that are determined to stick with what works for them for quite some time. It is just going to be in the same category with various older toolsets that will still WORK if you use them and that runtime support continues to possible for. It is just going to be a better idea to move on to whatever is next as soon as it becomes feasible. Really, my impression of MS's current development platform strategy is that it is a bit 'confused' at the moment. Clearly SL was envisaged as a long-term strategy and now it is equally clearly no longer so. It is even rather unclear exactly where they are positioning .NET and managed code in general going forward. From what we can tell it is likely to follow Java into the abyss of "server side technology" with some limited support for client facing apps if you're really determined. Whatever is coming next is hard to fathom, some mix of native code and HTML5 based tools. Maybe the IE10 runtime will become basically the runtime for 'managed' non-native type stuff going forward. Who really knows? I'm not sure MS knows. [/QUOTE]

Verification