I’ve made a few mad libs projects for fun, and I want to share them with some people.
I’m using Visual Studio 2019, if that’s important
(im new to c#, sorry)
Normally when you debug or run using VS, the compiled assembly would be in bin folder inside the project folder.
If you want the optimized binaries, like the other comment suggested, publish (package) the project by right click on it in the solution explorer and click publish.
By the sounds of it, they aren’t looking for a super polished deployment, therefore I think pulling the compiled assembly out of the bin folder is the better choice.
Publish the project.
If you’re targeting .NET Framework, remember that the Windows PC must have installed a version that’s at least equal to your project target. Automatically updated Windows should’ve already get .NET Framework 4.8 (the last version Microsoft will ever release), so you’re covered if your friends are using supported OS & allow Windows Update. Otherwise, consult this lengthy list .
If you’re targeting .NET Core (including .NET 5), you can bundle the runtime with your app
It does that when you build it. The executable will be in the bin folder under your project folder. That will have other artifacts in so you can use publish to get only the required files.
Right click on the project in solution explorer, click publish, adjust setting to suit.
C# devs
null reference exceptions