How Do I Package and install a Released compiled version version of my .Net Framework?

Question

This might be a simple question. I searched online and there was a lot of information that seemed to be just a distraction. How Do I Package and install a Released compiled version version of my .Net Framework? Do I just need to pass along the compiled .exe?

Do I bundle the contents of the Release folder or just the EXE's and DLL's? Do I need to include the app.config and packages.config?

Do I need to create an installer somehow?

I have heard of Squirrel

Answer 1

you need to deploy all the contents of the release folder. you can use the publish PublishSingleFile option to get just one file to distribute. how this works depends on the o/s

• for windows, it a self extracting app, that is expanded in a temp location, than ran from the temp location
• for MacOs it just an Mac application bundle which contains internal folders (basically an executable zip file).
• not sure the linux implementation.

note: you still have the option to include the runtime files, or require .net already be installed on host machine.

Answer 2

Sounds like you have a Windows app (console, Winforms, WPF, etc) so you can just xcopy the contents of the output directory to any machine that has a copy of .NET Framework installed on it and then run your app. Note that this will generally be the exe, dlls, your app.exe.config file and possibly some .pdb files. These are all that are needed to run your app. But if you have additional file system dependencies (like images or something you are expecting to be in subdirectories of your app) then you would need to mark them as content (Build Actions in Solution Explorer) and then those folders would show up in the output directory as well.

On Windows machines, if you xcopy the folder, then the files are likely to be blocked since it is coming from an untrusted source. You would need to unblock the exe in Windows Explorer.

If you want something more like an installer or a single binary to share then look at ClickOnce for a simple case of bundling up an app. If you need more complex installation options like file extensions or registry entries then you'll want to look at a formal installer like WiX, InstallShield or Install Anywhere.

Answer 3

Here is what I have done, as this youtube video demonstrates (mostly)

https://www.youtube.com/watch?v=U5YlBv3dDlI

In Microsoft Visual Studio 2022 Click Project --> Then click the project name Properties...

On the menu on the left, click "Signing" and click to sign the ClickOnce menifests.

Then click on "Security" on the menu on the left and enable ClickOnce security settings

Then click on "Publish" and then, what I did is select as the publishing folder to be a location on my company OneDrive.

And I clicked on Publish.

THen, as you can with OneDrive, I shared the folder with the application and setup executables with my boss.

But, in the future, I suppose I will have to use the FTP to do this.

I managed to create a Setup.exe through publishing but I do not know if this covers for the fact that the end user might not have .Net Framework installed on their computer.

Does it?

I understand it is on most windows OS's.