Re: [OT] WPF or Winforms?

[Stuart Kinnear]

As far as I am concerned you can toss WPF in the bin.  Our customer has
terminal server, supporting one of apps which is in WPF using remote
desktop can cause a blue screen of death - we can no longer support the
custoerm remotely when the app is running. The app will be rewritten back
to winforms.

All that fancy graphics stuff is all right for those who like the gimics,
but for business to business use give me something that will work all day
every day and doesn't require huge amounts of graphics and pc resource. The
way the web world is going, it might be hard for WPF to compete anyway.



- Stuart


On 25 September 2015 at 15:12, Corneliu I. Tusnea 
wrote:

> Nope. They are dead. (As far as I'm concerned) unless you really really
> really really need to go down that crazy path.
>
> If you really really want a desktop app I'd look into
> http://electron.atom.io/ to run a cross-platform "desktop" app build with
> web technologies on top of Chrome.
> Atom editor is build like that. Visual Studio Code is build in a similar
> fashion but not on top of electron but pretty much identical process.
>
> On Fri, Sep 25, 2015 at 2:57 PM, Tom Rutter  wrote:
>
>> Anyone here still using winforms? Any reason to start new projects in
>> winforms over WPF? How far has WPF come in the last several years?
>>
>
>


-- 
-
Stuart Kinnear
Mobile: 040 704 5686.   Office: 03 9589 6502

SK Pro-Active! Pty Ltd
acn. 81 072 778 262
PO Box 6082 Cromer, Vic 3193. Australia

Business software developers.
SQL Server, Visual Basic, C# , Asp.Net, Microsoft Office.
-

Re: [OT] WPF or Winforms?

[Scott Barnes]

As long as Windows is alive so is WPF and WinForms and while they are
"dead" in terms of roadmap advancements they are and will be supported for
20yrs  (or give or take a few years). Microsoft has certain rules about
killing tech like these and given there are military and govt contracts in
play killing "tech" is next to impossible until they sunset.

Transferring XAML skills to  is like
stating "I learnt C therefore i can do Java / C# right?" ..theory yes, but
its always the execution and debugging that gets you :)

It wouldn't hurt to go WPF if that's the only two choices you have and
depends on the context. I use WPF still and have seen many companies big
and small File-->WPF project still. Keep your hardcore business logic in
some PCL's as much as possible and assume your UI is disposable after say
1-5 years and you'll be fine. Downside is if you haven't got WPF devs on
staff and need to order in some (Consultancy or FTE's) the the $$ could be
an issue or the time to ramp up to WPF learning is painful. That being
said, you will suffer this fate going UWP anyway (maybe the blog posts are
fresher now but thats even a * conditions apply) moment.

Design surfaces are still the same crappy experience so if you want to
engage "designers" into your project be prepared to create what Jeremy Cade
and I are calling "Designer Ops" bloodlines into the team who's job is to
take pretty pixesl and not bend them into a distorted mess when injecting
them into the codebase?

Other than that...




---
Regards,
Scott Barnes
http://www.riagenic.com

On Fri, Sep 25, 2015 at 3:40 PM, Greg Keogh  wrote:

> I delayed going to WPF for years as I was so familiar with WinForms and it
> had a designer (which occasionally gets corrupted). If you want a
> reasonably standard UI then both WinForms and WPF produce similar results,
> but if you want a user "experience" then WPF has all the transformations
> and eye candy.
>
> Once you learn to write XAML by hand without a designer (it's just a
> preview window) and you create an MVVM pattern to use binding, then it's
> the choice for large desktop apps. Binding is fabulous.
>
> XAML continues to live and grow in Universal apps.
>
> *Greg K*
>
> On 25 September 2015 at 15:16, DotNet Dude  wrote:
>
>> Universal apps ad xaml are still getting quite a push from MS
>>
>> On Friday, 25 September 2015, Corneliu I. Tusnea 
>> wrote:
>>
>>> Nope. They are dead. (As far as I'm concerned) unless you really really
>>> really really need to go down that crazy path.
>>>
>>> If you really really want a desktop app I'd look into
>>> http://electron.atom.io/ to run a cross-platform "desktop" app build
>>> with web technologies on top of Chrome.
>>> Atom editor is build like that. Visual Studio Code is build in a similar
>>> fashion but not on top of electron but pretty much identical process.
>>>
>>> On Fri, Sep 25, 2015 at 2:57 PM, Tom Rutter  wrote:
>>>
 Anyone here still using winforms? Any reason to start new projects in
 winforms over WPF? How far has WPF come in the last several years?

>>>
>>>
>

Re: [OT] WPF or Winforms?

[Tom Rutter]

I hope electron is not the direction we go

On Fri, Sep 25, 2015 at 3:12 PM, Corneliu I. Tusnea 
wrote:

> Nope. They are dead. (As far as I'm concerned) unless you really really
> really really need to go down that crazy path.
>
> If you really really want a desktop app I'd look into
> http://electron.atom.io/ to run a cross-platform "desktop" app build with
> web technologies on top of Chrome.
> Atom editor is build like that. Visual Studio Code is build in a similar
> fashion but not on top of electron but pretty much identical process.
>
> On Fri, Sep 25, 2015 at 2:57 PM, Tom Rutter  wrote:
>
>> Anyone here still using winforms? Any reason to start new projects in
>> winforms over WPF? How far has WPF come in the last several years?
>>
>
>

Re: [OT] WPF or Winforms?

[William Luu]

I thought VS Code was built on top of Electron (which is just a shell)?

"Visual Studio Code (I call it VSCode, myself) is a new free developer
tool. It's a code editor, but a very smart one. It's cross-platform, built
with TypeScript and Electron, and runs on Windows, Mac, and Linux."
via:
http://www.hanselman.com/blog/IntroducingVisualStudioCodeForWindowsMacAndLinux.aspx

With the editor layer above that called Monaco (
http://weblogs.asp.net/jongalloway/a-quick-look-at-the-new-visual-studio-online-quot-monaco-quot-code-editor
).

And then you have OmniSharp  as the C#
intellisense provider (
https://code.visualstudio.com/updates#_languages-c35-on-omnisharp-111).

On 25 September 2015 at 15:12, Corneliu I. Tusnea 
wrote:

> Nope. They are dead. (As far as I'm concerned) unless you really really
> really really need to go down that crazy path.
>
> If you really really want a desktop app I'd look into
> http://electron.atom.io/ to run a cross-platform "desktop" app build with
> web technologies on top of Chrome.
> Atom editor is build like that. Visual Studio Code is build in a similar
> fashion but not on top of electron but pretty much identical process.
>
> On Fri, Sep 25, 2015 at 2:57 PM, Tom Rutter  wrote:
>
>> Anyone here still using winforms? Any reason to start new projects in
>> winforms over WPF? How far has WPF come in the last several years?
>>
>
>

Re: [OT] WPF or Winforms?

[Corneliu I. Tusnea]

Nope. They are dead. (As far as I'm concerned) unless you really really
really really need to go down that crazy path.

If you really really want a desktop app I'd look into
http://electron.atom.io/ to run a cross-platform "desktop" app build with
web technologies on top of Chrome.
Atom editor is build like that. Visual Studio Code is build in a similar
fashion but not on top of electron but pretty much identical process.

On Fri, Sep 25, 2015 at 2:57 PM, Tom Rutter  wrote:

> Anyone here still using winforms? Any reason to start new projects in
> winforms over WPF? How far has WPF come in the last several years?
>

Re: [OT] WPF or Winforms?

[DotNet Dude]

Universal apps ad xaml are still getting quite a push from MS

On Friday, 25 September 2015, Corneliu I. Tusnea 
wrote:

> Nope. They are dead. (As far as I'm concerned) unless you really really
> really really need to go down that crazy path.
>
> If you really really want a desktop app I'd look into
> http://electron.atom.io/ to run a cross-platform "desktop" app build with
> web technologies on top of Chrome.
> Atom editor is build like that. Visual Studio Code is build in a similar
> fashion but not on top of electron but pretty much identical process.
>
> On Fri, Sep 25, 2015 at 2:57 PM, Tom Rutter  > wrote:
>
>> Anyone here still using winforms? Any reason to start new projects in
>> winforms over WPF? How far has WPF come in the last several years?
>>
>
>

[OT] WPF or Winforms?

[Tom Rutter]

Anyone here still using winforms? Any reason to start new projects in
winforms over WPF? How far has WPF come in the last several years?

Re: [OT] WPF or Winforms?

[Greg Keogh]

I delayed going to WPF for years as I was so familiar with WinForms and it
had a designer (which occasionally gets corrupted). If you want a
reasonably standard UI then both WinForms and WPF produce similar results,
but if you want a user "experience" then WPF has all the transformations
and eye candy.

Once you learn to write XAML by hand without a designer (it's just a
preview window) and you create an MVVM pattern to use binding, then it's
the choice for large desktop apps. Binding is fabulous.

XAML continues to live and grow in Universal apps.

*Greg K*

On 25 September 2015 at 15:16, DotNet Dude  wrote:

> Universal apps ad xaml are still getting quite a push from MS
>
> On Friday, 25 September 2015, Corneliu I. Tusnea 
> wrote:
>
>> Nope. They are dead. (As far as I'm concerned) unless you really really
>> really really need to go down that crazy path.
>>
>> If you really really want a desktop app I'd look into
>> http://electron.atom.io/ to run a cross-platform "desktop" app build
>> with web technologies on top of Chrome.
>> Atom editor is build like that. Visual Studio Code is build in a similar
>> fashion but not on top of electron but pretty much identical process.
>>
>> On Fri, Sep 25, 2015 at 2:57 PM, Tom Rutter  wrote:
>>
>>> Anyone here still using winforms? Any reason to start new projects in
>>> winforms over WPF? How far has WPF come in the last several years?
>>>
>>
>>