Silverlight in Enterprise App
-
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.
I think you should make it clear to your employer that you are planning on implementing this in a technology you don't know. Odds are it will take you longer (thus cost more) and it won't be put together quite right the first time through as you don't have the needed experience with it. Generally employers pay you for what you already know and have experience with, not so you can play with the latest and greatest technology. I think if you want to pursue silverlight, you need to make a case for it beyond just eye candy. Where does it add value? If you can convince whoever is paying you that the value added is beyond the additional cost... go for it.
-
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
Read this after my reply... Completly agree though.
-
The targeted platform is not other than Windows so deployment restrictions will be less. :-) By the way what YMMV means??
Be careful, there is no Undo Button(Ctrl+Z) in life.
-
What databinding support are you referring to?
I didn't get any requirements for the signature
-
Pete O'Hanlon wrote:
Succinct, but I'd have to agree.
Heh. I just got back from a great counseling session, and I guess I'm in the "I need to tell people more what I really think" space, hahaha. John Simmons, look out! :-D Marc
Available for consulting and full time employment. Contact me. Interacx
Marc Clifton wrote:
just got back from a great counseling session
How's that going for you? BTW - I passed your details onto Mark Jose, hopefully he should be getting in touch with you soon.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
-
OK. Thanks for replying. It would be a hard sell to get my company to do any non browser based applications, so I'm not sure I could implement WPF. But those samples do look pretty neat.
I didn't get any requirements for the signature
-
Marc Clifton wrote:
just got back from a great counseling session
How's that going for you? BTW - I passed your details onto Mark Jose, hopefully he should be getting in touch with you soon.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
Pete O'Hanlon wrote:
How's that going for you?
Well, it was only my second session, but the shrink is great--he's the kind of guy who will say, flat out "Marc, that's BS!" which is really good to hear. :)
Pete O'Hanlon wrote:
I passed your details onto Mark Jose, hopefully he should be getting in touch with you soon.
Cool. I was going to ask about that. :) Marc
Available for consulting and full time employment. Contact me. Interacx
-
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.
crudeCodeYogi wrote:
some persons in the team wants to develop it in Silverlight. That way they can learn a new technology.
That sounds like putting the developer's agenda ahead of the users'. WTF!? /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
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.
All I read was "new project ... a new technology". Run. RUN! Do a little side project in Silverlight to test the waters, but starting a new project with a new technology that noone has experience in is asking for trouble. WinForms for the win.
Cheers, Simon > company:: Broken Keyboards Software > VS add for delicious BKS-Delicious > skype :: SimonMStewart > CV :: PDF
-
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.
Go for WPF + Prism + MVVM! The time spent learning would be more than offset by the increased simplicity and robustness!! :-D Asome people said... if no one knows anything of WPF / Prism / etc.. that might be a problem. That's a good point. But, as a person who knows WPF, WinForm, CaB, Prism, etc... As far as I'm concerned, WinForm is just a waste of time. Even simple thing are so much more time consuming. And complex things are so much more complicated! You could always hire someone who knows WPF or let one developer play on its own with WPF for 1~2 weeks...
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
modified on Thursday, February 5, 2009 12:33 AM
-
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.
It's a new project ! if your environment give you the possibility to work with WPF and Silverlight2, go ! May be it's the good project to let the team learn new technologies ? May be not ? If your strategy is to use Microsoft technologies go directly to WPF/Silverlight2. Of course your team will take some times to learn this 2 new technologies but if they know well .NET code, learning XAML will not be so hard. I had the same problem a few times ago. For some reasons I decided to choose WPF for my office application : > Powerfull way to build rich interface. You can do what you want depending on your imagination. > Powerfull way to represent and to manage Data (DataBinding, nothing to do with WindowsForm) > XAML is used in Silverlight2 and WPF application. Whith small changes your office application could become a web application. Your work is divided by 2. If you go to WPF and Silverlight 2 you will never come back to WindowsForm (sometimes I did nightmares).
-
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.
Basically, you are talking about the presentation layer of your application. The backend would probably be about the same for Winform, WPF or Silverlight if designed properly. If you dump the legacy technology of Winforms and move to a Silverlight/WPF technology for the front end, you should be able to handle web/desktop needs with minimal recoding over the coming years. Most developers will be doing Silverlight and possibly WPF over the coming three years as that is where the market is moving. With a new project, that might be just the time to bring the shop into into the technology they will probably be using for the next 7 - 10 years :) At this point, it is not that much in front of the wave, the swelling is here and by the time Silverlight 4 hits next year and VS 2010 has everything built in along with Azure, the wave will be in full force.
Rocky <>< Recent Blog Post: Doughboy – R.I.P. Thinking about Silverlight? www.SilverlightCity.com
-
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
-
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.