|
Not to worry, I attended a stand up for the project and have been and have been given a monumental task....
|
|
|
|
|
|
Well from the point of view that it gives me a task, so I'm not googling random stuff & I will be employed next week, yes, from the point of view that I am not getting to Google random stuff, no
|
|
|
|
|
glennPattonWork wrote: and I don't have to fix it Joke in German:
That's TEAM-Work (Toll Ein Anderer Macht --> Nice, someone else does)
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
|
Show off Snake Street (5)
98.4% of statistics are made up on the spot.
modified 25-Aug-17 5:17am.
|
|
|
|
|
Show off
Snake BOA
Street ST
BOAST
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
We have a winner!
98.4% of statistics are made up on the spot.
|
|
|
|
|
D'oh! I was trying to work out how BOARD meant show off. Some days you just know things aren't going well.
|
|
|
|
|
That's round the corner on Snake Road!
98.4% of statistics are made up on the spot.
|
|
|
|
|
I want to know that why c# developer choose WPF
|
|
|
|
|
Because you can do things in WPF that aren't easily achievable in Windows Forms. For instance, restyling a TextBox in WPF is incredibly trivial (say, you want it to have rounded edges). Oh, and the binding engine is vastly superior in WPF to Windows Forms.
This space for rent
|
|
|
|
|
can i shift from Win Forms to WPF, if i dont have working knowledge of WPF
|
|
|
|
|
Yes, start by learning WPF.
|
|
|
|
|
How to successfully turn into WPF if i don't know the WPF but i know Win Forms, both are similar to learn or totally new?
|
|
|
|
|
WPF uses XAML, which is a declarative language (similar to HTML) to handle the UI. It is vastly different to WinForms.
This space for rent
|
|
|
|
|
@Pete O'Hanlon can you give Code Project WPF article link, Thanks For Taking interest.
|
|
|
|
|
To show you what WPF looks like, and to get you in the declarative mindset, try this[^] article. The excellent @sacha-barber also wrote a fantastic series starting here[^].
This space for rent
|
|
|
|
|
Apart from what Pete suggested, you can have a look at WPF related stuff here on Codeproject[^]
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning
|
|
|
|
|
But the learning curve is something akin to photoshop.
If they would upgrade GDI+ and allow it to use graphic card capability, now that would back awesome.
|
|
|
|
|
windows forms vs wpf[^]
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning
|
|
|
|
|
|
My experience of WPF as others have previously commented is that it makes what seems complicated easy and what seems easy as complicated.
There are some real advantages when it comes to design of the UI and how the UI binds to the data.
Some things are not straightforward.
It's a steep learning curve and it's not something you can pick up from scratch without doing a fair amount of reading first.
That said when things go well with WPF you can design some really nice applications.
I would also add that I think that as an exercise in itself it's worth learning, because it will introduce you to MVP within a non web environment and the challenge of learning new architectural patterns can in itself have its own value.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Dunno. I use WinForms when I need a GUI. I'm more about function than form.
|
|
|
|
|
I don't. Partly because WPF has, and continues to be, voodoo to me.
That said, if I'm going to learn something obtuse, confusing, and poorly documented, I might as well dive straight into web development, which IMHO is where everything is going (or has gone), so that's where I've focused my learning energies.
If I ever end up doing mobile development, yeah, there's XAML and Xamarin, but at the moment, any work there hasn't escaped the event horizon.
|
|
|
|