Yes, of course!
In most cases you should be able to simply copying your executable (found in that bin
directory) to the target machine. There may also be a couple of other required / useful files in that folder that you might also want to copy (such as a .exe.config or .pdb file, or possibly even a .dll file if your program is split over multiple projects). If in doubt copying everything will probably work - at worst some of those files are just unneccessary (such as the .vshost files).
Your target machine will need to have the the .Net framework for the version that you are targetting (e.g. 2.0, 3.5, 4.0 etc...) installed. In many cases this will already be installed (especially so in the case of .Net 2.0), in the case that it isn't then generally these can be installed through Windows update, alternatively a quick search for ".Net version X installer" should do the trick. You should get a reasonably straightforward error messages if you try and run your application on machine that doesn't have the required .Net framework version installed.
If you feel up to it then are extra things that you might want to do when distributing software to a client, such as
- Building in Release mode
- Creating an instaler
- Deploying using ClickOnce
However the above should get you started.