I am after advice on 'life after Silverlight' (2021) and the preparation beforehand.
Scenario:
Sole developer (currently with 1 main commercial application (50 clients) (1 one other), using csla 4.5.3 and Silverlight, MS SQL)
My assumption is:
1) I will need to rewrite my application(s) to be ready around 10/12/2012 (I'm assuming there will be a 12-18 month time lag on this to take this date to say 10/21/2022)
Due to limited time between now and then I need to consider the above questions soon.
I would like to keep CSLA.net so am after advice on which development technology to use.
2) I am sure I will need a web-based solution (users are schools and teachers - ICT skills are poor (sorry teachers) and so I need a solution that can be deployed remotely without (minimal) user intervention)
3) I don't particularly like html (or should I say CSS), however at the age of 51 I would be prepared for one final push to learn/become expert at this.
I think some of you may suggest WPF as it is close to Silverlight - my concern is... can WPF be guaranteed to be strong post 2021. I need a solution that is good for at least 15-20 years (my application is subscription based and will provide my pension to 65 and beyond - hopefully!! - hence why I am leaning to html5 etc.).
There are so many current frameworks etc. that I'm getting a little bogged down and confused.
I am thinking of using MVC6 (I've not done mvc before previously using win forms but not a lot and am happy to switch as I like the pattern [MVVM/MVC])
If I use MVC6 should I also learn Web API? Is this a better fit for CSLA?
Which front end / binding framework? Angular, Knockout etc and are these compatible with CSLA? - can these of other frameworks 'bind' to CSLA objects?
Any views on this would be warmly welcome - and I hope benefit others in this scenario.
One final thought might be to wait to say 2019 and hope that MS (or others) may have come up with a more streamlined (html) technology that is as good and as easy as Silverlight.