Well, I hope they have insurance.

Thanks, I’ll see myself out.

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.

“Copilot I’m losing this match, aim for me”

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.

#FF00FF

In terms of physiology, the color is stimulated in the brain when the eye reports input from short wave blue cone cells along with a sub-sensitivity of the long wave cones which respond secondarily to that same deep blue color, but with little or no input from the middle wave cones. The brain interprets that combination as some hue of magenta or purple, depending on the relative strengths of the cone responses.

In other words, our brains are like “🤷‍♂️, here’s a thing”

Terminal is life!

But also, easy mode Linux distro for the technically challenged would be great

Windows 98 -> Slackware dual boot (with big ol’ red grub screen) -> windows up to win 10 -> debian(laptop) win10 (pc)

Gonna try getting a new m.2 drive and dual booting soon to test playing the games I like on Linux. If all goes well, I’ll be moving away from windows

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

(theres a mac version but isn’t the same)

There was a mac version. But it is hitting EOL in August

After using AI chat stuff like this and chatgpt, ive come to the conclusion that building prompts is akin to building search queries for search engines. Wherein using the right terms leads to better results.

command! -range -nargs=1 PadColumns call PadColumns(<line1>, <line2>, <args>)

function! PadColumns(start, end, columns)
    execute a:start.','.a:end.'s/\(.*\)\zs\s*$/\='.'repeat(" ", a:columns - len(submatch(1)))'
endfunction

Use by typing in Normal mode :PadColumns 20. This will add spaces after the line or selected lines to the column you specify (in this case, 20).

You could probably improve this by getting the length of the longest line and so you dont need to specify the specific column to add spaces to (20), and instead just add say 5 spaces after longest line for all lines.

I do not think that this is an existing feature in neovim, however this seems to work :%s/\(.*\)\zs\s*$/\=repeat(' ', 15 - len(submatch(1)))

Change 15 to the column desired. You could probably create a function where you pass the column number you want so that you dont have to type this string all the time.

Reminds me of the “Op” wars on IRC. All users would be given @ status and the point was to kick everyone before you got kicked. Writing scripts for this was my first “taste” at programming.

Changing links to add their affiliate codes was enough of a shady thing for me to swear off this browser. No telling what kind of a fast one the company will try to pull in the future.

Have you tried setting a breakpoint and seeing if it hits? Assuming the app you are debugging is just a Console.WriteLine("Hello World"); and no breakpoints are set, the app will execute, output hello world, and terminate. Which means you wouldn’t see anything happen in VS Code.

If you are super new to all this, I would suggest you look for videos/articles on how to debug using visual studio code as they may provide some insights or concepts you may not already know.