Yeah, unfortunately that stuff is almost impossible to estimate. Inform your client that fixing the build will be a game of whack-a-mole where you’ll fix one thing and 5 new errors will show up. I would give yourself lots of time since you’ve never worked on Maui (? You didn’t say that in your post but if you’ve never heard of xamarin, i’ll assume maui is new).

I would break your work down into two milestones: a) compile and run, b) fix all the busted views. It should come to no surprise that a) will be hard to estimate so give yourself lots of time, and b) will be easier to estimate because you’ll be able to review each View and determine what kind of fixes you need to make.

Good luck

Yes. The transition from Xamarin to Maui has been similar to transition from .net framework to .net core.

A few things you will run into:

• namespaces have changed
• certain things will be deprecated but still currently work (ie FillAndExpand)
• platform specific setup has changed (you’ll need to convert to the new way, but code will likely remain the same)
• upgrade your nuget packages to the Maui equivalents (the ones we used had Maui versions so we didn’t have to change any of them)
• certain ways of doing things have change slightly, like how to run things on the main UI thread (you’ll see warnings)
• your xaml code will remain mostly unchanged but your layout may need to be fixed (especially if your dependencies changed their interfaces)

That’s all I can think of right now. There’s no easy way to do it and it’s going to suck. Focus on getting it to build with all your dependencies upgraded and then go from there.

Kind of a nothing burger.

These repositories, belonging to more than 16,000 organizations, were originally posted to GitHub as public, but were later set to private, often after the developers responsible realized they contained authentication credentials allowing unauthorized access or other types of confidential data. Even months later, however, the private pages remain available in their entirety through Copilot.

The repo was listed as public and archived. It’s not clear from the article but I suspect that the “private” information is just a copy of what was made public and not the information added after it was made private.

So why would Valve do this? It may be a response to several law firms’ attempt to file “mass arbitrations,” wherein “hundreds or thousands of consumers bringing individual arbitration claims against the same company at the same time and over the same issue,” according to ClassAction.org. It’s essentially a loophole for class action waivers and arbitration clauses, though it still won’t end up in court.

Hit em right in the pocket book.

It’s a feature, not a bug

Man visits childhood home to reconcile with himself after being forced to harm coworkers.

It’s the computer’s job up to the point where you get on Picard’s “shit list”. That’s when the person being punished is responsible for beaming the poop out.

Good one, let me try!

Knock knock

Who’s there?

Race Condition

If you immediately know the candlelight is fire, the meal was cooked a long time ago.

Wait a minute, that’s not star trek!