Oleksii Lozovskyi

Wow, @pzhlkj6612, thanks for a detailed analysis! (And the one in the other issue as well). Somehow it did not occur to me that @kwhat's issue might be caused by...

(GitHub should provide a way to opt out of automatically closing issues mentioned in a PR. The fact that something has been merged does not mean that it was released....

@kwhat, I've just released **v1.8.0** which should allow reconfiguration. Could you please try it out? `ilammy/msvc-dev-cmd@v1` should already point to that release.

@pzhlkj6612, > > GitHub should provide a way to opt out of automatically closing issues mentioned in a PR > > Well, you used the "Resolves" keyword to link this...

> What if we set the value of those variables to empty? Then they will be empty. A variable with "empty string" as a value. This is different from "not...

Uh-huh... Thanks for a report, @constantinpape! I'm able to reproduce the issue with both `windows-2016` and `windows-2019` environments so that's not it. The real reason seems to be related to...

Hm... I admit this action was not maintained well. For example, it lacked scheduled builds to verify that it's still working, and lacked ‘integration’ testing of the released versions. I’ll...

Oh!.. Yeah... You are right: this action is just a thin wrapper over Visual Studio's batch file. It can only activate the environment already included in GitHub Action runner. It...

@ajfriend, @exarkun, I've published a new version which could probably support some older versions of Visual Studio. Could you please try it out? ```yaml - uses: ilammy/[email protected] ``` Unfortunately, I...

I believe those are separate issues here... Removing public symbols from a shared library without changing soname is... not nice. @ashinn does not do this, and it's great. And it's...