Silverlight in Enterprise App
-
If you want to justify it quantify the risk. Determine the known cost in development time in Winforms that has a low likliehood of failure, excluding the time to develop any logic and rules and other back-end code, and then double the estimate for the Siverlight application portion. Now total the time to develop including back-end, Windows Forms Front-End, and Siverlight Front-End and see if the total time is under budget or over budget. If it is under budget the decision is easy. If it is over, then you have to make a best guess. If you estimate the Siverlight UI portion to take more than 30% of development time then I would say you have a big risk. If you want to mitigate the risk, take into account the teams training budget for the year and see if the training budget is enough to cover the risk for a total wash. If it is, then you have a way to justify a failure as training as well.
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.Well depending upon the current requirement we don't see that much risk. Because basically what the app will do is - it will display an image portion and the fields from the database, user has to just verify that the other application has read the corrected values. So the UI part for silverlight is very less. But the thing is lets say we develop this in Silvelight, after few months client has asked for few more features OR MS no longer supports Silverlight then our app might be at risk. That's why I want to know whether there are people using silverlight for entreprise application or not. This has happened when we first used XPF which is not so much popular now and we are migrating the application to output xml.
Be careful, there is no Undo Button(Ctrl+Z) in life.
-
Well depending upon the current requirement we don't see that much risk. Because basically what the app will do is - it will display an image portion and the fields from the database, user has to just verify that the other application has read the corrected values. So the UI part for silverlight is very less. But the thing is lets say we develop this in Silvelight, after few months client has asked for few more features OR MS no longer supports Silverlight then our app might be at risk. That's why I want to know whether there are people using silverlight for entreprise application or not. This has happened when we first used XPF which is not so much popular now and we are migrating the application to output xml.
Be careful, there is no Undo Button(Ctrl+Z) in life.
Hold on then, http://web.ics.purdue.edu/~ssanty/cgi-bin/eightball.cgi[^]
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.
I would suggest go for WPF (which is meant for Desktop applications) Silverlight is not a technology for desktop app (yet)
Omit Needless Words - Strunk, William, Jr.
Vista Gadget Book: Creating Vista Gadgets using HTML, CSS, & JavaScript. Sample chapter here Selling Your Gadget
-
Hold on then, http://web.ics.purdue.edu/~ssanty/cgi-bin/eightball.cgi[^]
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.:laugh: :laugh: :laugh:
Be careful, there is no Undo Button(Ctrl+Z) in life.
-
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 wouldn't let any of my team loose on a project with new technologies based on a live application. There are too many risks with dead ends and learning curves to justify affecting your clients.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
-
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.
Figure out what your deployment restrictions are. Obviously, you're gonna need the WPF or Silverlight runtime installed wherever this will need to run. We briefly considered using WPF a while back, but the need to support Citrix clients shot that down quickly; YMMV...
-
I wouldn't let any of my team loose on a project with new technologies based on a live application. There are too many risks with dead ends and learning curves to justify affecting your clients.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
Yes I totally agree with you. And just to mention that I and other team members don't have rights to decide which technology to use for live project. But we are just going to propose them to use new technology. You know as a developer we feel award when everybody is using new technology and you are still stuck to the old one with fear of risk.
Be careful, there is no Undo Button(Ctrl+Z) in life.
-
Figure out what your deployment restrictions are. Obviously, you're gonna need the WPF or Silverlight runtime installed wherever this will need to run. We briefly considered using WPF a while back, but the need to support Citrix clients shot that down quickly; YMMV...
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.
-
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 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
-
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:
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
-
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
ToddHileHoffer wrote:
WPF / Silverlight has not added any value for regular data driven business applications.
Errm, sorry but I'd have to disagree with you. The databinding support alone makes it a more than attractive option. If you want to develop a LOB application, then I suggest you download Karl Shifflett's XAML Power Toys[^] which has a really handy LOB generator.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
-
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
Marc Clifton wrote:
WTF are you thinking?
Succinct, but I'd have to agree.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
-
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
Hey Thanks for your valuable comments :-)
Marc Clifton wrote:
a) developers that drive new technologies to learn something new get projects and companies in deep sh*t
I agree. That's why I asking for suggestion.
Marc Clifton wrote:
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
I like this suggestion. I have to pass it onto my seniors.
Marc Clifton wrote:
c) since nobody knows the new technology, nobody can adequately evaluate whether it'll meet the requirements
But people who have adopted new technology and faced problems can help others.
Marc Clifton wrote:
d) web development (Silverlight) is very different from WinForm. WTF are you thinking?
Currently the requirement is flexible and I also know WinForm will give more power than Web.
Marc Clifton wrote:
you are doing a WPF WinForm app, expect a huge rampup cost to learn the technology.
As I said in my reply to Pete that's something company and/or project manager has to decide.
Be careful, there is no Undo Button(Ctrl+Z) in life.
-
ToddHileHoffer wrote:
WPF / Silverlight has not added any value for regular data driven business applications.
Errm, sorry but I'd have to disagree with you. The databinding support alone makes it a more than attractive option. If you want to develop a LOB application, then I suggest you download Karl Shifflett's XAML Power Toys[^] which has a really handy LOB generator.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
What databinding support are you referring to?
I didn't get any requirements for the signature
-
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
Marc Clifton wrote:
d) web development (Silverlight) is very different from WinForm. WTF are you thinking?
MS marketing at work...
I didn't get any requirements for the signature
-
Marc Clifton wrote:
WTF are you thinking?
Succinct, but I'd have to agree.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
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
-
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