1

Topic: WinForms in.Net Core 3

2

Re: WinForms in.Net Core 3

3

Re: WinForms in.Net Core 3

Hello, BlackEric, you wrote: BE> Is not present, while will be only under Windows. In WinXP will work?

4

Re: WinForms in.Net Core 3

Hello, BlackEric, you wrote: BE> In quitting next year.net core 3 promise support  development: WinForms, WPF and UWP. BE> If it will be valid  it will be very much and very much cool! About "" already answered, well and in remaining will be just as integration WPF in WinForms or on the contrary works. I.e. "Hello World" show, and in remaining all will be very sad.

5

Re: WinForms in.Net Core 3

Hello, BlackEric, you wrote: BE> Is not present, while will be only under Windows. Here only wanted to write that they tear navels, copying the CODE of ALL  in a crust-3 but you the good fellow, was corrected. There is a reasonable question: and what for sitting under normal , with normal working Windows.NET generally somewhere to go?? What, in life it is not enough "crusts"? (=) Actually, this nonsense I also do not like EVERYTHING that is now created in  a lobby - from impudent  type azure to absolutely confused plans "we ours, we new", but thus on old . And thus they continue something to shout about ""! Slightly reminds  about the Jew:-Rebe, tell, here "black" is a color? - Colour! - "white" - color? - Colour! - Well here you see, Izja, I to you sold the COLOR TV set! I.e.  like also "sells"  (as I  to write this word!) But again everywhere  in the form of impudent lies and innuendoes.  - it as an oak cultivated on chernozem which grew in an adult tree with acorns and which now unfortunate  try to transplant in asphalt, in passing changing a gene of acorns for oranges. Whether it seems .NET team what now a little late to recall about fruit when all is used for a long time already by acorns and what the whole acorn industry cannot simply stop and begin to do all to a forfeit?? It without speaking about change in asphalt (),  it is a little suitable for life generally. And passage to a marsh ground (iOS) generally seems  for there and the plants suffice. Somehow all of them ... The Internet - overslept, mobile phones - *,  - ... Well there for people such stupid work??  at all the "", just for this reason has conclusive plus - all everywhere identical. There are no "profiles", SDK-versions and other vedroid-circus. And that unequal always it is possible . The main thing - to facilitate life and to users, and  under  that.NET in 2002 and made - deduced  on human level. And we even are ready on.NET which Windows-only, allow to work easy only! But is not present itches at  , simpletons innocent in "" did not play enough yet! , this  the freak, easier god-send for such ! Here also all was got it core' a soup - a stench all around, but desperate Hindus continue to knead intensively the boiler, hoping to weld porridge. Only here it him also should be guzzled - people around do not have any desire in it to be got involved. We sit on the Win7 and silently we go nuts on "madness and courage" any Nadell, dared  money of investors. Wildness...

6

Re: WinForms in.Net Core 3

Hello, kov_serg, you wrote: BE>> Is not present, while will be only under Windows. _> in WinXP will work? UWP it is launched only on Win10. And you would want that "the new technology" Core 3 on  was launched?

7

Re: WinForms in.Net Core 3

Whether K> it seems .NET team what now a little late to recall about fruit when all is used for a long time already by acorns and what the whole acorn industry cannot simply stop and begin to do all to a forfeit?? It is possible to roll out the cross-platform version and to wait, wait and wait while  fatally  - that during this moment to bite off the detuned market. Yes, it is possible and not to wait. But at their resources unless it is not necessary to try?

8

Re: WinForms in.Net Core 3

Hello, HotDog, you wrote: BE>>> Is not present, while will be only under Windows. _>> in WinXP will work? HD> UWP it is launched only on Win10. And you would want that "the new technology" Core 3 on  was launched? That is and under windows will not work.

9

Re: WinForms in.Net Core 3

Hello, _, you wrote: _> Hello, kov_serg, you wrote: _>> In WinXP will work? _> to give to you  from all nonsense, yes there is no sense - will take offense, the foot will be ill, and changes nothing. It is spent Pads short.  such  which not on all platforms works.

10

Re: WinForms in.Net Core 3

11

Re: WinForms in.Net Core 3

A> 1. Framework there can be one, and versions Net Core of the old and new can stand a little different parallely. It is possible to use the new version, without influencing old operating applications. In 2005 it it was able . But then any Hindus-managers from MS wanted substituting setting of updates with saving of reverse compatibility. A> 2. Core can not stand, go at all with application in a set. In 2002 it promised-promised, and that turned out that turned out. A> 3. CLR/BCL at Core faster  and  and generally faster. And it too promised. Grief. And after all only it was necessary to hold on till today , and hastily to fasten it to that cross-platform. net Framework which promised from the very beginning. A fuck-up what difficult way the industry went.

12

Re: WinForms in.Net Core 3

13

Re: WinForms in.Net Core 3

Hello, hi_octane, you wrote: _> In 2005 it it was able . But then any Hindus-managers from MS wanted substituting setting of updates with saving of reverse compatibility.... _> in 2002 it promised-promised, and that turned out that turned out.... _> and it too promised. Well here also fulfill. Do not fulfill - badly, fulfill - too badly. Whether to be killed about a wall that?

14

Re: WinForms in.Net Core 3

Hello, kov_serg, you wrote: _> Pads short.  such  which not on all platforms works. WinXP it is not supported any more as a platform. And on clients who sit till now on WinXP, money you will not earn - neither you, nor Microsoft. The sense any is not present . If you sit on Windows XP - that and itself can .NET Core on Windows XP. But anybody for you this operation will not do another.

15

Re: WinForms in.Net Core 3

Hello, Vladek, you wrote: V> WinXP it is not supported any more as a platform. And on clients who sit till now on WinXP, money you will not earn - neither you, nor Microsoft. The sense any is not present . Who to you told that clients which use winxp without money? Terminals on xp here work and 10 there it be no point to put generally. V> If you sit on Windows XP - that and itself can .NET Core on Windows XP. But anybody for you this operation will not do another. Well here  to the healthy person this.net core is asked, if in half a year next $ at a microsoftware and appears.net quad core? Which will work on new 10 which will be is put only on processors of monthly prescription which to you do not sell because of sanctions.

16

Re: WinForms in.Net Core 3

Hello, kov_serg, you wrote: _> Hello, Vladek, you wrote: V>> WinXP it is not supported any more as a platform. And on clients who sit till now on WinXP, money you will not earn - neither you, nor Microsoft. The sense any is not present . _> Who to you told that clients which use winxp without money? Terminals on xp here work and 10 there it be no point to put generally. Where licenses on WinXP for those terminals have been bought? Them it is simply impossible to buy or activate copies from old stores. With  it is downloaded? Means, there is no money. V>> if you sit on Windows XP - that and itself can .NET Core on Windows XP. But anybody for you this operation will not do another. _> well here  to the healthy person this.net core is asked, if in half a year next $ at a microsoftware and appears.net quad core? Which will work on new 10 which will be is put only on processors of monthly prescription which to you do not sell because of sanctions. The healthy person will not rewrite a software to use the freshest tools. And generally - it is necessary to be able to write the code so that it was ready to platform change in the future minimum efforts. It not always is necessary, and when it is necessary - it is necessary still to be able to do it.

17

Re: WinForms in.Net Core 3

Hello, Vladek, you wrote: V> Where licenses on WinXP for those terminals have been bought? Them it is simply impossible to buy or activate copies from old stores. With  it is downloaded? Means, there is no money. Do not mix soft with the warm. If the client does not wish to pay for that that twice it does not mean at all that it does not have money. Licenses are taken together with iron on which these terminals work There iron very much second-hand. V> the Healthy person will not rewrite a software to use the freshest tools. And generally - it is necessary to be able to write the code so that it was ready to platform change in the future minimum efforts. It not always is necessary, and when it is necessary - it is necessary still to be able to do it. On it.net core goes wood.

18

Re: WinForms in.Net Core 3

Hello, alexzzzz, you wrote: Kolesiki> There is a reasonable question: and what for sitting under normal , with normal working Windows.NET generally somewhere to go?? A> can want to go for the several reasons: A> 1. Framework there can be one, and versions Net Core of the old and new there can be a little different parallely It does not answer my question. It is possible both  to deliver, and  with  to a heap, but what for it is all to put, if already is.NET?? A> 2. Core can not stand, go at all with application in a set. Yes for God's sake! Again there is no answer to a question: what for it is necessary to the Bark if works.NET? A> 3. CLR/BCL at Core faster  and  and generally faster. Well throw out this to the Bark, yes direct all resources on.NET - here to you too "faster"! And if about speed of execution so besides, in the MSEC too stupid managers, to guess idea separately compiled JIT'. You download as usual MSIL, and then ALL  long, but it is optimal  in x64 (in normal ) - here to you too quickly! Generally, at all "monoaxial ".NET, for a long time it was already possible to make " C#" - directly in . Especially if there is no reflection and  dynamic.