As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Is is reasonable to make a web application using Silverlight technology?
All elements on the page do this with Silverlight applications? (LOGIN, Chat, Search Users, etc.)
The application for a thousand users?
What are the disadvantages?
The number one disadvantage of Silverlight is that it requires browser support to run. So if your goal is to build a truly cross platform solution that needs to work in many Browsers, be very careful. For example, Mobile Safari has no support for it.
My company made the mistake of choosing Silverlight early and then had to redo much of the development because Silverlight does not work on iPad.
Also Microsoft might be dropping support for Silverlight in favor of WinRT.
On the plus side, if you already have WPF knowledge, you should have little problem moving into Silverlight. The development enviroment, tools and libraries are all top knotch and fun to work with.
Ultimately it all comes down to what you already know and what your requirements are. If your target environment is always going to be Windows and you already know .net or WPF, going with Silverlight makes a lot of sense.
Silverlight works really well for big applications.
Silverlight has all the ingredients for a web application.
One disadvantage I can think of is that Linux users might not be able to view your application, because the Silverlight client for Linux is less feature-rich.
From what I remember the biggest disadvantage would be if Microsoft drops support for Silverlight: Microsoft may halt development work on Silverlight plugin after next release
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I'm wondering to replace our WinForms technology to WPF.
Is WPF mature enough to migrate to?
What are the migration risks?
Is it tweaked and robust enough? Isn't there any plan to deprecate WPF like SilverLight?
I'm wondering to replace our WinForms technology to WPF. Is WPF mature
enough to migrate to?
Yes.
What are the migration risks?
Time and training to understand SOLID implementations of MVVM.
Is it tweaked and robust enough? Isn't there any plan to deprecate WPF
like SilverLight?
WPF is "depricated" in Windows 8... but all of the features are still there - it's hard to explain...
Metro Apps will still use XAML and DataBinding to describe the UI and interraction with the View Model. Applications can still be written in C#, and there is a .net framework dedicated to it (4.5). But instead of compiling to CLR - it compiles into Native Code.
So, while WPF is technically depricating, what we are left with (Metro) walks, talks, and otherwise behaves just like a WPF development effort.
That said, WPF apps can run on the "Classic Desktop" of a Windows 8 computer, and the .net framework 4.0 is still current technology.
P.S. This topic is likely to be closed - you might be able to get better answers at https://softwareengineering.stackexchange.com/
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
At work we have an application that we need to update. It is a fat client that is largely written in Windows Forms with newer parts of it being in WPF. The main section of this application is a form designer that is implemented with a Web Browser control using HTML.
We need to redesign a large portion of the application and need to generally improve the user experience. There's a good chance that I will be the one working on this project and I am very familiar with WPF and feel like it would be a very suitable technology to use. I would plan to remove the old windows forms portions and largely rewrite the application.
However, there has been some discussion of migrating this application to be a web application in a future release. My coworker was tossing around the idea of trying to redesign the dialogs and application using HTML while still being a fat client.
Does this seem like a reasonable idea? Is there any kind of design similar to this approach that would support this kind of hybrid application? Would we be able to realistically create the same kind of user experience using HTML5 / JS that WPF would offer?
The idea of making portable code is enticing, but I have serious concerns about the feasibility of this suggestion. I know that windows 8 apps support a variety of design options, but this application would be targeted for xp / windows 7.
This really depends on the application audience but I'd say go with Web if it's easy enough and it should be since you're starting from scratch.
I was faced with the same question 3 years ago and I still regret sticking to WPF because the app could have been deployed on tablets if it was a web app.
If your app contains abundant business logic make sure you split that out well, business logic in JS doesn't work well - crappy to debug, difficult to manage over the entire life of the app. Generally expect more difficult development when compared do WPF but with much larger potential audience.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I'm about to start a long term windows application project but not sure which way to go, i have to kept in mind due to long term project the technology i will choose must be supported in upcoming windows 8. The project can be created on any of these WINAPI MFC ALT WIN-FORMS WPF more of less a little but my main concern is a long support at least as long as windows 8 comes out and continue. I personally wanted to go with WPF but i'm kinda scared that everyone on internet is talking that WPF is going to dead because of Microsoft new HTML5/JS hype. I don't know why Microsoft has choose HTML5/JS as their PLATFORM for windows development in windows 8 (i personally don't think HTML5 is not capable enough to create AAA windows applications).
Which is most safe can any one tell me through his experience
WINAPI MFC ALT WIN-FORMS WPF ? Which one
we have choose wpf with mvvm pattern for our frontend technology.
at least the frontend technology depends on your application requirements :)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
Will WPF die out and be replaced by a silverlight that continues to be improved ? What is the direction of bothh ...i am asking as i have heard of MS possibly dumping WPF primarily because of percieved or actual performance impact on the snappyness etc of the UI.
http://www.zdnet.com/blog/microsoft/microsoft-our-strategy-with-silverlight-has-shifted/7834
WPF is for desktop applications, Silverlight for webbased (ala flash) ones, and also for the new Windows Phone 7, Silverlight is just a subset of wpf adjusted for different platforms.. Also - it really depends on the coding, as with everything. If you execute everything in the UI Thread, of course the UI won't be as responsive. I'm coding a wpf application and it is as snappy as a win forms one.
It's relatively unlikely that WPF will die out or be replaced by Silverlight any time soon. Silverlight can't create the kind of rich client applications that WPF can, and like it or not, desktop applications aren't going away any time soon.
Not to mention, Microsoft has written the interface for several of its major software packages in WPF (Visual Studio and Expression Studio). Many of the things these applications are required to do simply can't be done in the kind of sandboxed environment that Silverlight can provide.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
We are starting a big LOB application using Silverlight.
I was wondering if you have any experience with Testing Silverlight apps, what are the best solutions you found and if you encountered any pitfalls.
A stalwart individual named Jeff Wilcox has developed a unit test framework targeting Silverlight 2 specifically. It works well.
http://code.msdn.microsoft.com/silverlightut/
I also use Rhino Mocks 3.5 For Silverlight as my mocking framework, developed by Oren Eini. Rhino Mocks is free and excellent. It also offers Silverlight support:
http://ayende.com/projects/rhino-mocks.aspx
I use Prism 2.0, and Unity IoC, which help facilitate the MVVM pattern. This makes testing a breeze. One pitfall that I find, is that Silverlight unit tests run inside a web browser, which hampers continuous integration.
ib.
A "must have" debugging tool for SIlverlight is Silverlight Spy, available as a free download.
Probably not exactly what you're after, but I subscribe to Netflix and they use the following url
http://www.tinyurl.com/netflixsl
...to send subscribers to when they've got a problem. This is of course, at the end of things, and I'm assuming you're after something to test while you're actually developing. But, this might be something you could copy once you're product is released.
I use SilverUnit to unit test Silverlight, it is an open source tool that sits on top of Typemock Isolator