As I've mentioned multiple times before, the installer is necessary to make sure people have .NET 3.5 SP1. As is people are already messing that step up and ending up with problems (even though I've mentioned hundreds of times, .NET 3.5 SP1!). Without an installer I'm pretty sure the number of people with just .NET 3.5 and not .NET 3.5 SP1 or even without .NET FW would be ten times its current ratio, and that many more people would be having problems. Also, installations are better than unzip and run because any changes made to the OS can easily be undone by uninstalling. It also helps keep track of what you have and where.Knocks said:The author needs to realize that people really hate installers. This is not Microsoft Office, its' a freaking Wii utility.

AlexDP said:As I've mentioned multiple times before, the installer is necessary to make sure people have .NET 3.5 SP1. As is people are already messing that step up and ending up with problems (even though I've mentioned hundreds of times, .NET 3.5 SP1!). Without an installer I'm pretty sure the number of people with just .NET 3.5 and not .NET 3.5 SP1 or even without .NET FW would be ten times its current ratio, and that many more people would be having problems. Also, installations are better than unzip and run because any changes made to the OS can easily be undone by uninstalling. It also helps keep track of what you have and where.
In short, the installers going nowhere.
I'm sorry but you clearly don't understand much about runtime libraries. I can't do a check for the right version of .NET in the program itself, because if you don't have the right version you wouldn't be able to LAUNCH the program. The same goes for MFC, Java and all the other runtime libraries. HENCE, why people invented installers. Whatsmore, distributing programs without installers is contrary to the recommended practices for software distribution on Windows. Also, Firefox is a horrible example of whats good practice with software and software distribution. The only reason some of those programs are distributed without installers is because someone made the (stupid) assumption that the user would already have the same envirnoment that the developer has, or the version of the runtime libraries they're using are distributed with Windows (and hence they can safely assume that people will at least have that.)Knocks said:AlexDP said:As I've mentioned multiple times before, the installer is necessary to make sure people have .NET 3.5 SP1. As is people are already messing that step up and ending up with problems (even though I've mentioned hundreds of times, .NET 3.5 SP1!). Without an installer I'm pretty sure the number of people with just .NET 3.5 and not .NET 3.5 SP1 or even without .NET FW would be ten times its current ratio, and that many more people would be having problems. Also, installations are better than unzip and run because any changes made to the OS can easily be undone by uninstalling. It also helps keep track of what you have and where.
In short, the installers going nowhere.
If you want to idiot-proof it, it's as easy as enabling a simple check for the right version of .NET. The installer is slow, it clutters the installation menu, and is completely unnecessary. Look around WiiBrew and see how much software is distributed with installers (hint: almost none). For pete's sakes, Firefox can run without an installer and a tiny utility can't? Give me a break.

AlexDP said:I'm sorry but you clearly don't understand much about runtime libraries. I can't do a check for the right version of .NET in the program itself, because if you don't have the right version you wouldn't be able to LAUNCH the program. The same goes for MFC, Java and all the other runtime libraries. HENCE, why people invented installers. Whatsmore, distributing programs without installers is contrary to the recommended practices for software distribution on Windows. Also, Firefox is a horrible example of whats good practice with software and software distribution. The only reason some of those programs are distributed without installers is because someone made the (stupid) assumption that the user would already have the same envirnoment that the developer has, or the version of the runtime libraries they're using are distributed with Windows (and hence they can safely assume that people will at least have that.)
Lastly, no ones forcing you to use this software. By all means, use other software, it's not like your paying me. If you've got issues with installers and runtime libraries (.NET in this case), this isn't the software for you.
I never said there's anything wrong with whats on WiiBrew. The stuff that's available on WiiBrew is generally either code, a Wii app, or a console program and it's generally targeted at developers, who can most likely figure out what they need to do. Loose files and archives are a perfectly valid distribution method for what they're distributing on WiiBrew and who it's for.Knocks said:AlexDP said:I'm sorry but you clearly don't understand much about runtime libraries. I can't do a check for the right version of .NET in the program itself, because if you don't have the right version you wouldn't be able to LAUNCH the program. The same goes for MFC, Java and all the other runtime libraries. HENCE, why people invented installers. Whatsmore, distributing programs without installers is contrary to the recommended practices for software distribution on Windows. Also, Firefox is a horrible example of whats good practice with software and software distribution. The only reason some of those programs are distributed without installers is because someone made the (stupid) assumption that the user would already have the same envirnoment that the developer has, or the version of the runtime libraries they're using are distributed with Windows (and hence they can safely assume that people will at least have that.)
Lastly, no ones forcing you to use this software. By all means, use other software, it's not like your paying me. If you've got issues with installers and runtime libraries (.NET in this case), this isn't the software for you.
If somebody can't read and understand the message that .NET is required, they have no business formatting their drives in obscure file systems or hacking their consoles to begin with.
And if you think Mozilla Firefox and everything on WiiBrew are bad examples of software distribution, then you need to get off your high horse. You coded a GUI for a hacking tool, not a supercomputing package.
AlexDP said:Finally, as far as I'm concerned Firefox is a terrible application done by a company I have no faith in. They do so many things against best practices that Firefox doesn't even qualify as a proper application for me.
I don't know how old you are, but the Mozilla Foundation and its predecessors have probably done more for personal computing than the entire software industry put together. They're a big part of the reason Microsoft is finally accepting open standards and people have better operating systems today.
QUOTEDo you see IE being distributed as zip files? How about WinZip? Windows Live Messenger?


AlexDP said:I'll be releasing the source code soon after I release the next (and most likely my last) version (2.5) and you can do whatever you like with it.
if you don't like it, DONT USE IT but do NOT come here and spew this crap around. He's worked his ass of for free for this program, and we all love it. If you don't like it then move along.Knocks said:I am perfectly happy with the command tool, but I do try different homebrew and wasn't happy when this program took a good 6-7 minutes to upgrade my .NET version without my permission. That is NOT a good programming practice.
I also find it necessary to correct idiotic statements like "IE is better than Firefox" from time to time.
Edit for geographical clarity with apologies to all offended. Other points still stand.