On Wednesday, 6 January 2021 at 03:28:45 UTC, 12345swordy wrote:
> On Wednesday, 6 January 2021 at 03:13:56 UTC, Basile B. wrote:
>> On Wednesday, 6 January 2021 at 02:57:50 UTC, 12345swordy wrote:
>>> On Wednesday, 6 January 2021 at 02:17:50 UTC, Basile B. wrote:
>>>> On Wednesday, 6 January 2021 at 01:51:04 UTC, 12345swordy wrote:
>>>>> [...]
>>>>
>>>> ???
>>>>
>>>> To avoid building manually run.d use directly rdmd as "Command", then tweak the "Arguments" fields.
>>>>
>>>> Command: rdmd.exe
>>>> Arguments: <path to>\run.d
>>>> Initial Directory: <path to run.d>
>>>>
>>>> and check "Prompt for Arguments" and then in the prompt you type the particular test to run. This step in unavoidable.
>>> I am using this currently.
>>> https://github.com/rainers/dlangvs/blob/master/vcbuild/dmd/dmd_test.vcxproj
>>
>> I don't follow you. What's wrong with the use of a tool ? Use the VS solution to build dmd and then use the external tool to run the the test suite. I mean it can be launched from the IDE, even with a shortcut so the fact that is is external is not blocker.
>
> It is much easier for me to explain what the problem is if you managed to run visual studio on your local window machine.

Yes and sorry, there is something not clear. I hope someone on Win could help.
To be clear, run.d is used by the different CIs, incl. those running Windows tests that's why I have not hesitated to reply even if I'm not a Windows user.