As slackmoehrle suggested, use an installer. A great installer that I’ve personally used in the past is Inno Setup, which you can find here: http://jrsoftware.org/isinfo.php
Inno Setup has a scripting language that isn’t hard to learn, and very quick to create setup files.
An installer will package everything into a single EXE/MSI file if you want that, depending on what you require, and you can then distribute that file to users.
The exact files you need to include in the package would be all relevant files in the output build folder for your application, and you should already know what they are.
As for the Visual Studio 2015 or 2017 run-times etc (which ever your app requires), you should include the installers with your package, and you can write the script in Inno Setup to check for them and install them if required. Here’s some info on how to do that:
https://www.codeproject.com/Articles/20868/NET-Framework-Installer-for-InnoSetup