We've been building a large Silverlight application using CSLA 3.8 (I know, it's a tad old but hey, if it aint broke...) to a great deal of success for the last 6 years.
The business is now a little concerned about continuing to invest in Silverlight given that Microsoft have pulled it from their roadmap. The thought of Microsoft saying "the next version of Internet explorer will not support plugins" gives us chills.
We went down the path of Silverlight because at the time we thought a web based system was the way to go. However, in retrospect, what we should have gone with was not a browser based system but rather a system which was deployed via the browser, but run locally on the user's PC.
So our thinking now is, if we don't keep building functionality in Silverlight, what do we build it in? We can't go with Win8 apps as our customers don't use Windows 8. We want to stick with .Net because of our huge investment in CSLA. So we feel that our best bet is to create a three tier system in WPF and transition our Silverlight code base into that. We'd then deploy the exes via ClickOnce.
Before we start prototyping, I was wondering if you can alert me to any challenges in relation to CSLA that you can immediately think of in this endeavour?
Many thanks
Damien