Do I want to publish or publish an assembly on VB.net?

I wrote a small application (for example, 40 lines) of Winforms with VB.net in Visual Studio 2010. Now I released the code as a Google Code project. It is easy for the developer to get the source code, but I would also like to simplify its installation.

What I did was build the releases, and then consolidate what it created, including the setup.exe file. There was also the opportunity to “publish” my project, which looks so that it may include checks for updates and other materials.

In my case, I just want to make it easier for the casual user who happens to need to try this app with as few clicks as necessary. Has release set to build a better way to do this?

+3
source share
1 answer

I think the “Best” method is subjective. However, there is nothing wrong with how you did it. How I would do it.

If you plan to provide updates, you can also look at ClickOnce (which is the Publish option), but I like how you did it better.

With ClickOnce, you probably need to purchase a certificate from a CA and sign a code. If you do not, anyone who tries to use your application will receive a terrible security warning. They can get around him, but it will prevent anyone who is not familiar with him.

+3
source

Source: https://habr.com/ru/post/1722465/


All Articles