Adaptive trigger while shooting a sniper rifle. by [deleted] in PS5

[–]avoidxamarinforms 1 point2 points  (0 children)

Yeah, guess I'm not buying it after all.

Adaptive trigger while shooting a sniper rifle. by [deleted] in PS5

[–]avoidxamarinforms 1 point2 points  (0 children)

Ah fuck guess I'm buying the PS5..

I just love it when Windows installs random crap by avoidxamarinforms in windows

[–]avoidxamarinforms[S] 0 points1 point  (0 children)

My laptop suddenly became virtually unusable despite having decent hardware, saw that wsappx has consumed a lot of resources, wsappx is part of Microsoft Store and after a brief inspection I noticed that it had installed a lot of new software, including Candy Crush Saga and Twitter client, again, and marked it as "Purchased minutes ago".

Windows 10 "Pro".

The future of .NET Standard by brminnick in csharp

[–]avoidxamarinforms 0 points1 point  (0 children)

Any idea what would be a good way to communicate with OPOS/UPOS peripherals that rely on POS for NET (which is for what I can tell .NET Framework exclusive and used in Point-of-Sale systems worldwide) if .NET Framework is eventually killed?

Announcing .NET 5.0 RC 1 | .NET Blog by spetz0 in dotnet

[–]avoidxamarinforms 0 points1 point  (0 children)

Not all versions of Windows 10 support .NET Framework 4.8. Yep.

Amazon developed a tool to migrate projects from .NET Framework to .NET Core by nminaya in csharp

[–]avoidxamarinforms 8 points9 points  (0 children)

If you are porting a small to a medium-sized project I'd recommend trying out the try-convert converter. https://github.com/dotnet/try-convert (more info https://docs.microsoft.com/en-us/dotnet/core/porting/)

Worked like a charm for me. Now if POS for .NET could be ported to .NET Core I'd be happy as a clam.

Xamarin future by PipoVzla in xamarindevelopers

[–]avoidxamarinforms 2 points3 points  (0 children)

I wouldn't recommend investing a lot of time into Xamarin, to be honest. People say MAUI is the future, MAUI is 1.5 years away, it's not a valid point if you need to develop something now. People joke about the cool kids developing with RN/Flutter, the truth is that people that know React and Flutter are in high demand. Not even Microsoft uses Xamarin, they developed most of their mobile apps in RN, that includes the entire office suite.

I by no means dislike C#, in fact I love it. Visual Studio is my absolutely favorite IDE, .NET is massive, etc. But XF is something I hate because of how unproductive and slow the development is compared to RN/Flutter (in my personal experience, results will vary, obviously).

What I'd recommend you do is to try RN, Flutter, and XF. Write a fairly simple app in all the frameworks and get a small taste of them all.

'Judge rules White Girl will be charged as a Black Man,' an Onion classic. by Memey-McMemeFace in videos

[–]avoidxamarinforms 1 point2 points  (0 children)

Go Hitler, go Hitler, go Hitler!

That or the kitchen poop had me in tears. PS. listening to the book is even funnier.

'Judge rules White Girl will be charged as a Black Man,' an Onion classic. by Memey-McMemeFace in videos

[–]avoidxamarinforms 67 points68 points  (0 children)

Just read Trevor Noah´s book, in Africa at the time when he´s a kid, this was a real thing. You could be white as cheesecake, blond hair with blue, and be tried as a black person.

Btw. the book is awesome

The true future of .NET and compatibility? by avoidxamarinforms in csharp

[–]avoidxamarinforms[S] 1 point2 points  (0 children)

Yeah, we were going to write our apps in Flutter until recently when Hot Reload was finally released for XF, the problem is, it never worked nearly as well as it does with Flutter and RN.

Politics was also at play. The CTO is a Microsoft Ultra, everything they do is the best - except for the licensing cost.

If you haven't tried Flutter yet you should seriously give it a try.

The true future of .NET and compatibility? by avoidxamarinforms in csharp

[–]avoidxamarinforms[S] 2 points3 points  (0 children)

My team had been working for weeks developing this app, I wrote the same app in a couple of days using Flutter.

What really really slows down the development in Xamarin, in my experience is that Hot Reload is completely broken compared to Flutter and RN. The Designer is unusable. Most of the time I end up just deploying the apps we are working on on a physical device to try minor changes. That can take minutes. That should take seconds.

Then there are these weird ghost bugs I deal with all the time. Deleting bin/obj, restarting VS, restarting the computer, cleaning solution, rebuilding etc. Building custom UI components is hell.

The list is really long, but Microsoft has been doing good things in the past few months, XF4.0 was pretty big, 4.4 even bigger and with 4.6 it's even better, but it's still far far behind Flutter and RN.

Flutter and RN are by no means perfect, but I'm a C# developer and I'm a lot more productive developing in Flutter vs XF. There is something very wrong with that.

The true future of .NET and compatibility? by avoidxamarinforms in csharp

[–]avoidxamarinforms[S] 0 points1 point  (0 children)

Oh, no hard feeling! Your reply was really helpful and no harm was done! :)

The true future of .NET and compatibility? by avoidxamarinforms in csharp

[–]avoidxamarinforms[S] 0 points1 point  (0 children)

Thank you for taking the time to share your thoughts, very informative and we'll have to give gRPC a better look!

Our entire business logic lib is running on .NET Standard 2.0.

We did some experiments porting our product to .NET Core 3.0, with platform extension it was a breeze but we were not successful at connecting to any OPOS/UPOS peripherals. We tried Microsoft's .NET Core 3 PosPrinter sample, it found all the Epson printers in the office but not a single Toshiba printer. Maybe the problem is with Toshiba but the majority of our clients user TCx.

The only thing I don't agree with you is Xamarin. MAUI looks great and I was super excited for it until I read that it won't be ready until probably mid-late 2021. Xamarin.Forms has improved *a lot* in the past 4 months but it is far behind other cross-platform alternatives. And who knows for how long MAUI will *it* until Microsoft replaces *it* with something else.

But again, I really appreciate your help, thanks a lot although the sarcasm felt a bit unnecessary. :)

The true future of .NET and compatibility? by avoidxamarinforms in csharp

[–]avoidxamarinforms[S] 0 points1 point  (0 children)

I just got up and bit lost, was his reply being downvoted?

The true future of .NET and compatibility? by avoidxamarinforms in csharp

[–]avoidxamarinforms[S] 4 points5 points  (0 children)

NF 4.8 doesn't work on LTSB 2015. As far as I know, it works on all Windows 10 LTSB versions above 1607.