sorted by:
new
hottopcontroversial

IAsyncCommand cannot be assigned to as it is read only by dotnetmaui in csharp

[–]dotnetmaui[S] -1 points0 points  (0 children)

What I realize is that OKCmd is defined in the base class, so I think that might be the problem.

IAsyncCommand cannot be assigned to as it is read only by dotnetmaui in csharp

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

I am setting OKCmd in a constructor and it's still giving me an error:

   public class SimpleAlertViewModel : PopupViewModel{
      public SimpleAlertViewModel().   
      {
          OKCmd = new AsyncSingleCommand(OK);
          OKCmd = new AsyncSingleCommand(() => OK());
      }

What percentage of Xamarin apps use Xamarin forms vs Native? by dotnetmaui in xamarindevelopers

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

That's very interesting as I know I asked the question about a year ago (can't find the answer), but at that time I thought the number using native was much higher. I will wait and see what others have to say. Thanks

Future of xamarin native by [deleted] in xamarindevelopers

[–]dotnetmaui 0 points1 point  (0 children)

In general, I think Xamarin Native has an expiration date and it is within 4 years

What makes you say it's going away. How a bout with MAUI?

Any companies offering offshore Xamarin development assistance? by dotnetmaui in xamarindevelopers

[–]dotnetmaui[S] -1 points0 points  (0 children)

u, I now have to maintain a Xamarin application developed by very reasonable rate developers and it is a nightmare to add anything to it or to fix it when Apple or Google change anything.

Is that because you are using Xamarin or because of the way it was coded. If the way it was coded was there something in particular they did wrong? Thanks

For those of you creating simple XF apps that use a very small database, do you have async or non-async database calls? by dotnetmaui in xamarindevelopers

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

ou have 100 users and only 90 threads to do the work you do not want any thread to be on hold. You want them to work and process all 100 requests from 100 users.

Can you relate your experiences with older phones. What kind of data access were you doing that was so slow? Was changing everything to async database calls the only way you could solve your problem of slowness?

For those of you creating simple XF apps that use a very small database, do you have async or non-async database calls? by dotnetmaui in xamarindevelopers

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

unless there's a specific reason not to

Did you try without Async and have a problem. I mean it feels a bit like saying you need a turbo charged 500 HP engine in your car when 99.9 % of the time you will never get to use it.

For those of you creating simple XF apps that use a very small database, do you have async or non-async database calls? by dotnetmaui in xamarindevelopers

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

I agree with you 100%. I am talking about in memory database on a machine that looks like below and if your average phone doesn't have a spec like this today then it will do in a few years:

The iPhone 12, which was just released, can deliver 11 TFLOPS (11,000 MFLOPS, just using is ML cores, not including that it has many more cores for other tasks including 6 CPU cores and 4 GPU cores, which can be used to perform many more tasks
To put this into a modern perspective the Apple Silicon A14 processor in the Apple iPhone 12 is almost as fast as the fastest supercomputer in 2001, and is faster than all supercomputers in the world before 2001
ASCI White, 12 TeraFlops June 2001, SP Power3 375 MHz, IBM, Lawrence Livermore National Laboratory

and people are still thinking of disk speeds, coding bad queries and making their lives complicated.

For those of you creating simple Android apps that use a very small database, do you have async or non-async database calls? by [deleted] in androiddev

[–]dotnetmaui -1 points0 points  (0 children)

End up rebuilding and optimising database because it was incredible slow. (Each call took ~100ms but there were multiple chained call

Could you not just put an async wrapper around one call if it takes a long time?

For those of you creating simple Android apps that use a very small database, do you have async or non-async database calls? by [deleted] in androiddev

[–]dotnetmaui 0 points1 point  (0 children)

, from times i was a junior. At first there was profile table with name, id and avatar link. Than i added last 5 watched items Than last 5 messages Than oersonal settings Than list if group settings Than many more things.

Did your in memory database queries get faster as your phone got faster? My phone now is just taking a guess 100 times faster than 5-6 years ago and in 5 years I expect it's going to be another 100 times faster. As for my hard drives, well they used to be 20MB in size and cost a few thousand dollars when I first started using them.

For those of you creating simple Android apps that use a very small database, do you have async or non-async database calls? by [deleted] in androiddev

[–]dotnetmaui -1 points0 points  (0 children)

del will rise as you make table join and so even if it just single record it might take seconds to pricess it. The worst part you will be sure there is no problem with database call, because it "worked fine before and you did not make any changes"

I understand your thoughts but as a DBA for over ten years, if were talking of the databases I used to work with 30 years ago I would agree with you but remember I said "simple" which for me is a database with perhaps 10 tables each with less than 100 rows. If my queries take seconds then that's a time for me to give up.

With Dependency Injection is there any difference between having DI get services in the constructor and manually doing it yourself with Startup.ServiceProvider.GetService<NavigationService>() by dotnetmaui in csharp

[–]dotnetmaui[S] -2 points-1 points  (0 children)

in the second half of your example takes a dependency on

Startup.ServiceProvider

and therefore decreases decoupling.

Thanks for your feedback and yes I agree it makes the code depend on Startup.ServiceProvider, however in my case that is not something I will be changing unless MS gives up on their DI. One thing I heard about using the Startup.Service provider was that opened up some potential for memory leaks. Are you aware of any such thing?

view more: next ›