Silverlight in Enterprise App
-
It's still in beta?? Have I missed something? We started using XPO a couple of years ago. The product you linked to doesn't take care of the UI binding, which is the point of the posts above.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
-
Cool. Thanks for the link.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
-
Cool. Thanks for the link.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
The only thing i dont like is with their samples they use ThreadPool.QueueUserWorkItem delegate as its impossible to know the status of your data sending / retrieving, which is why i use BackgroundWorkers to achieve all databinding and retrieving.
-
If the application is properly designed the User Interface portion should consist of a very small portion of programming and should present a minimal risk so I would say go for it.
Need software developed? Offering C# development all over the United States, ERL GLOBAL, Inc is the only call you will have to make.
If you don't ask questions the answers won't stand in your way.
Most of this sig is for Google, not ego. -
So we got a new project. :-) The requirements are pretty straight forward and can be easily implemented in Windows Desktop Application. But there are some persons in the team wants to develop it in Silverlight. That way they can learn a new technology. But nobody is sure that our team should take this risk or not. What do you say depending on your experience? Should we go for WPF/Silverlight or Windows Forms Technology is fine?
Be careful, there is no Undo Button(Ctrl+Z) in life.
MSDN mag has enterprise app code in Silverlight http://msdn.microsoft.com/en-gb/magazine/dd434653.aspx
-
crudeCodeYogi wrote:
What do you say depending on your experience? Should we go for WPF/Silverlight or Windows Forms Technology is fine?
Experience has shown that: a) developers that drive new technologies to learn something new get projects and companies in deep sh*t b) if the developer wants to learn something new, the company should either set up an R&D budget or the developer should learn it on their own nickel c) since nobody knows the new technology, nobody can adequately evaluate whether it'll meet the requirements d) web development (Silverlight) is very different from WinForm. WTF are you thinking? e) you are doing a WPF WinForm app, expect a huge rampup cost to learn the technology. Marc
Available for consulting and full time employment. Contact me. Interacx
To be fair, Silverlight does bring web development a bit closer to WinForms since the need to manage state isn't as big of an issue. But as a guy stuck in "post-production support" (read: app is in the shitter) of an application that decided to lead the way and use Windows Workflow even though no one knew anything about it, I agree with the intent of this post 100%. There is sooo much I wish I had known back when the decision was made. I still can't decide if I like WF as a tech but our implementation sucks, or if the tech sucks as well.
-
MSDN mag has enterprise app code in Silverlight http://msdn.microsoft.com/en-gb/magazine/dd434653.aspx
Thanks for the link :-)
Be careful, there is no Undo Button(Ctrl+Z) in life.
-
Think again, business logic is easy to implement. Most isues come from the GUI implementaion, no matter what the technology
:laugh:
Need software developed? Offering C# development all over the United States, ERL GLOBAL, Inc is the only call you will have to make.
If you don't ask questions the answers won't stand in your way.
Most of this sig is for Google, not ego. -
I would not use silverlight for a standard enterprise business application. I have implemented WCF Services and I am fond of them. They provide actual value to the company I work for. WPF / Silverlight has not added any value for regular data driven business applications. That being said, if MS integrates expression blend / Silverlight projects in the next iteration of Visual Studio I will consider using these tools. If it were me, I would use a standard ASP.Net or WinForm application along with a nice set of UI Controls such as Telerik or Infragistics. You will still be able to provide an excellent UI to your users and it will be easier to develop.
I didn't get any requirements for the signature
-
Thanks for the tip. My company purchased Telerik's ASPNet AJAX controls for me. They're excellent as well. It is just my opinion that it is always a good idea to use 3rd party controls for a slick UI. That way, you (the developer) can focus on meeting the needs of the client without having to worry about extra coding for a nice presentation.
I didn't get any requirements for the signature
-
So we got a new project. :-) The requirements are pretty straight forward and can be easily implemented in Windows Desktop Application. But there are some persons in the team wants to develop it in Silverlight. That way they can learn a new technology. But nobody is sure that our team should take this risk or not. What do you say depending on your experience? Should we go for WPF/Silverlight or Windows Forms Technology is fine?
Be careful, there is no Undo Button(Ctrl+Z) in life.
If your new to Silverlight/WPF then there is a steep learning curve. However once you are over that hump Silverlight is the best of both worlds(web and winforms)!