Release v. Next

[dblock]

Looks like people are still using this!

#22

@icnocop are you?

[icnocop]

Hi.

Unfortunately no, I'm not using this library anymore.

If there's no one else willing to, I can try to set up a CI pipeline.

[dblock]

If there's no one else willing to, I can try to set up a CI pipeline.

If you're bored, GHA now supports Windows so that would be pretty cool, but you know ...

[icnocop]

One issue I'm facing in order to get the CI/CD pipeline to successfully run is that a username and password is needed to login and download VMware VixCOM 1.11:
https://my.vmware.com/group/vmware/get-download?downloadGroup=VIX-API-1110

🤔

[dblock]

@icnocop Check-in a binary here or in a branch/fork/tree.

[icnocop]

The VMware VixCOM 1.11 exe is over 100 MB so I had to enable Git LFS to push it to the repo, and exceeded the 1 GB LFS bandwidth quota while testing and fixing the pipeline. 🤔

[dblock]

😡

I got a notification about that, was wondering where it came from. I could buy a $5 data pack for 50GB but that will lead to the same problem sooner than later. Dropbox basic 2GB or Google Drive are free, make an account?

Also please disable Git LFS, cause I think that DDoSed my account.

Also don't hesitate to just give up.

[icnocop]

Sorry about that.

I plan to disable Git LFS, split the exe file into smaller parts, and combine them back during a CI build.

[icnocop]

A GitHub release can be tested by manually running the Build workflow and setting "Create release in GitHub?" to true.