.Net is cumbersome, and they are release-awkward. Unlike Java, you end up with multiple .NETs on the disk, more points of failure and contention.
And why is it needed on what should be a simple disk access and display utility. Can it really give much gain ? Doubtful. It is just that the programming house is used to programming other products under the same framework. Their gain (minor), our pain.
Conceptually, the idea is fine. The problem is implementation (as shown by the need to have multiple .NETs.) and usage where it is just another failure point, and extra resource consumption, for little purpose.
Example. It is likely my download and unpack problem was .NET related. I ended up with a folder of .NET somethings unpacked and the rest went haywire. Never able to install. Too much complexity for a simple utility.