AW: Trouble with new lo-build

[Juergen Funk]

Hi Christian,

> IANAL, but all the documents I read about that read about intranet or
> a share in your company or something like that, even if there's a
> network based method, it still doesn't sound to me like it could be
> offered over the internet.
Yes, you're right, I confused that with the “offline layout via web server,” which is not what we have.

But you can also install it using the command line.
for example (can not found the .vsconfig)
vs_community.exe --quiet --wait --norestart --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.VisualStudio.Workload.NetWeb
or
winget install --id Microsoft.VisualStudio.2022.Community --override "--quiet --add Microsoft.VisualStudio.Workload.ManagedDesktop --includeRecommended"

In the documentation, we could include a note about installing
vs_community --quiet --wait --norestart --add Microsoft.VisualStudio.Workload.ManagedDesktop --add ...
as an alternative to manual installation.

> "winget configure -f .config/configuration.winget" – that will install
> visual studio with the required packages
Where can I find the document?

best
juergen

________________________________________
Von: LibreOffice <libreoffice-bounces at lists.freedesktop.org> im Auftrag von Ilmari Lauhakangas <ilmari.lauhakangas at libreoffice.org>
Gesendet: Mittwoch, 23. Juli 2025 18:47
An: libreoffice at lists.freedesktop.org
Betreff: Re: Trouble with new lo-build

On 7/23/25 15:21, Christian Lohmaier wrote:
> On Tue, Jul 8, 2025 at 4:01 PM Juergen Funk <j-funk at outlook.de> wrote:
>>> Yeah, But that is not a lightweight installer you can offer people to
>>> download to get "the necessary stuff".
>>> I don't think there's an easy way for that/none that's easier than a
>>> winget configuration file
>>> and re latest version I meant the latest release of VS2022 for
>>> example, while there are dedicated LTS channels to use e.g. 17.10.x
>>> instead of 17.14.x, those also require additional commandline flags to
>>> run, so again not easier than to run the installer and pass the
>>> vsconfig file..
>> Ne, I give up, it seems that I am too stupid to convey this to you in an understandable way.
>> I just wanted to point out a way how we could have control over VS, despite the license agreement from MS,
>
> IANAL, but all the documents I read about that read about intranet or
> a share in your company or something like that, even if there's a
> network based method, it still doesn't sound to me like it could be
> offered over the internet.
>
> and from the other mail:
>
> "This is only relevant for the first installation, we could make a
> script that installs VS and cygwin or wsl for example."
>
> That already exists, that is the winget configuration method. But that
> suffers from the mentioned chicken-and-egg problem. the files for that
> are in the repo, thus you need git, and git-bash is provided by Visual
> Studio...
>
> "winget configure -f .config/configuration.winget" – that will install
> visual studio with the required packages
>
> And to install the other deps as well there's the
> .config/admin_java_and_deps.winget and .config/user_steps.winget files
> - those aren't part of the default config (but could be) since not
> everyone wants to install JDK or use wsl for example, so those steps
> can be tweaked before running them. Unfortunately there's no include
> mechansim for winget config files, but the steps can be split up to be
> more modular – balancing "runnning more winget configure commands"
> with "no need to edit the config files to adjust"

Today for the first time I proposed to a new contributor to try setup
with the winget commands and as a solution to the chicken-and-egg issue
I asked to download the first needed configs via opengrok:

https://opengrok.libreoffice.org/download/core/.config/2022.vsconfig?r=b01838cce57508c216da3b8f728854019160f8db
https://opengrok.libreoffice.org/download/core/.config/configuration.winget?r=b4fd0468f62cfe7c4a2b2ed1208e6e3b1e16c06b

Ilmari