Should winform programs package. Net framework into the installation package? what is the mainstream practice?

recently developed a winform program with C-sharp, using .net framework 4.0, because some users use XP, so they chose this .net version, but some users still do not have .net on their computers, so in order to let all users install smoothly, package .net into the installation package.

the installation package itself is only about 10m, but the .net package has become more than 70m. I want to know, is this packaging good? what is the mainstream practice?

then the program is quite stable on my computer, but there will be some conditions on win10. Later, I also did some processing, and it is basically good. But there are still a lot of problems on xp. Excuse me, is it OK to make a winform program compatible with XP,win7,win8,win10, at the same time? How to improve compatibility? How to make the program more stable?

I am self-taught C-sharp winform development. I have a language foundation, and my development is relatively fast, but after all, my experience is limited.

May.13,2021

may be OK, but it is not recommended. Let users download it themselves.
in fact, this is a product thinking problem, according to the principle of minimum permissions, our software can only do the smallest range of things, framework this allows users to download, so that users do not doubt why our software is so big.


the mainstream practice is to leave the package unpackaged and let the user install it himself. Personally, I don't think it makes much sense to package Framework. If you want to pack, pack as you like.
as for xp compatibility. I didn't do this.


70m is not big. After the first installation, you can automatically update


try

in two versions.
Menu