aloopkin / WinCertes

An ACMEv2 client for Windows
GNU General Public License v3.0
118 stars 28 forks source link

No EXE in the repo #5

Closed 300cpilot closed 5 years ago

300cpilot commented 5 years ago

A lot of people are not up to speed on compiling. You might want to explain enough to get a noob going.

brianedwards71 commented 5 years ago

Compile the software using Visual Studio to get the executable. Works fine.

rvschaffer commented 5 years ago

Please add a pre compiled version. It would make the life of those who don't use Visual Studio regularly much easier.

aloopkin commented 5 years ago

I don't understand: there is a pre-compiled version in https://github.com/aloopkin/WinCertes/releases

300cpilot commented 5 years ago

The problem is that no where in the readme or the instructions start where the compiled version is. This is more of a request to include the more basic instructions needed to run your program. Many see this and expect the exe to be sitting right there for download. Your not the only one that does this. I just felt that your project could be helped by allowing users with no programming knowledge to use your software without having to learn programming or searching the repo. Thanks,


From: Alexandre Aufrere notifications@github.com Sent: Saturday, November 3, 2018 12:01:24 PM To: aloopkin/WinCertes Cc: Dallas Crandall; Author Subject: Re: [aloopkin/WinCertes] No EXE in the repo (#5)

I don't understand: there is a pre-compiled version in https://github.com/aloopkin/WinCertes/releases

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/aloopkin/WinCertes/issues/5#issuecomment-435608325, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJK_z3ZwZTqIeqW6_HMpxiF7xxdLg7txks5urdn0gaJpZM4XKgM-.

aloopkin commented 5 years ago

Guys, sorry but that bugs me: you were able to find the standard Github menu entry to open a ticket, but you didn't find the also standard menu entry to download binaries... So maybe it's an issue with the Github UI, which isn't clear enough?

300cpilot commented 5 years ago

Sorry, I swear there was not a release showing when I got in there. I see it fine now. I had to compile via VS.


From: Alexandre Aufrere notifications@github.com Sent: Sunday, November 4, 2018 11:23:38 AM To: aloopkin/WinCertes Cc: Dallas Crandall; Author Subject: Re: [aloopkin/WinCertes] No EXE in the repo (#5)

Guys, sorry but that bugs me: you were able to find the standard Github menu entry to open a ticket, but you didn't find the also standard menu entry to download binaries... So maybe it's an issue with the Github UI, which isn't clear enough?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/aloopkin/WinCertes/issues/5#issuecomment-435693307, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJK_z0EPzADs4RZ7xufs0mf6lU7I-ZSwks5urzCqgaJpZM4XKgM-.

ElimAdmin commented 5 years ago

Thank you for your work on this @aloopkin. Like others, it took me time to work out where to download the exe from: [https://github.com/aloopkin/WinCertes/releases]. You are an expert. We are trying to make our way, a long way behind you. A simple link in the instructions for the noobs - that's all we ask. :) I don't think it's an issue of Github clarity - it's one of knowledge and understanding - and we're all trying to gain that. Today I have found where 'Releases' can be found. I'm moving forward. Thank you again.