Ripping a single file out of the installer isn't as easy as it sounds - it isn't a standard archive. Much easier (and quicker) to use the download link from curl, and drop it in from there. It's the same file.

Yeah, I just noticed that with the v7.16.7 installer. I thought 7-zip could to it, because I've done the same for individual files from other installers with 7-zip. However, in this case, the files are not possible to individually extract.
Case closed.

V 7.16.7 should be a sufficiently modern version I believe.

If you're as close as that, why not go the whole hog and update?

Because I'm a Grumpy Swede, who doesn't use any more modern OS than Windows 8.1, and even still use as old OS as XP and Windows 7. Also Grumpy enough
to refuse Facebook, Twitter, Instagram, and on top of that refuse to have a smartphone.

LOL

V 7.16.7 should be a sufficiently modern version I believe.

If you're as close as that, why not go the whole hog and update?

Because I'm a Grumpy Swede, who doesn't use any more modern OS than Windows 8.1, and even still use as old OS as XP and Windows 7. Also Grumpy enough
to refuse Facebook, Twitter, Instagram, and on top of that refuse to have a smartphone.

LOL

:-)

I’ll second that 👍

Thank you!

Well, look what the News thread brought in.

Edit - I've had a PM overnight from a user trying to build BOINC for the first time under VS2019. He says there are some error messages, perhaps relating to the changes for the ARM build, but doesn't go into details - he's going to try again later.

Does anyone here already have a known, working, VS2019 setup? If so, could they give it a try,.please - that might explain why there's no v7.16.20 build from Berkeley yet.

Well, look what the News thread brought in.

I've just written a how-to for actually saving the file into the directory, as just downloading it and immediately saving it to C:\Program Files\ will not work due to the protected nature of this directory.

I've started to prep up a spare Windows 10 partition that I may be able to use for VS2019. The app I built on VS2013 yesterday is still running fine, so there can't be too much wrong with the code: hopefully just the solution file 'boinc_vs2019.sln'. But I want to check Oliver's post about the order of certificates in the bundle not being a solution, first.

I've started to prep up a spare Windows 10 partition that I may be able to use for VS2019. The app I built on VS2013 yesterday is still running fine, so there can't be too much wrong with the code: hopefully just the solution file 'boinc_vs2019.sln'. But I want to check Oliver's post about the order of certificates in the bundle not being a solution, first.

Ugh - things have changed a bit since I first started programming for Windows 3.1!

But I got Windows 10 up-to-date, installed VS 2019, installed some more software it wouldn't work without (Git, TortoiseGit, Notepad++ - I'd use those anyway), downloaded the v7.16.20 branch source, and gave it a try.

boinc.exe compiled OK, but with lots of warning messages. It's running now, under Windows 7 - so that's a plus.
boinccmd.exe compiled OK, but I haven't tested it. The boinccmd solution compiles those two, but not much else, so it's a useful test.
boincmgr.exe failed completely. That's a show-stopper, and may be the reason we saw no progress except the emergency workround over the weekend.

I'll stop there for tonight. I've turned down my cache size, so it will be quicker to start experimental work tomorrow, if it's still needed.

since boincmgr is just a frontend GUI for the client (boinc.exe), do you even need a new version of this? can't you use the "old" boincmgr with the "new" boinc?

---

Yes, that's the way I tested it was working. But since that's a remote machine I don't usually spend time watching, it isn't important to me personally. The powers-that-be at UCB will not want to be forced into a kludge like that - it will offend their sense that they know how to manage this stuff. But since they self-evidently can't, it may be the least-worst temporary solution.