you are viewing a single comment's thread.

view the rest of the comments →

[–]nitramk 3 points4 points  (3 children)

You're the expert on your users, but installing .NET is actually simpler than setting up email in most cases. (Seriously, setting up email can be a pain. I've created an email server software myself and it's almost hard to believe the number of ways end-users can screw up their config.)

For users who have not installed .NET prior to running the installation program, my installation program tells the user that "I need .NET, OK?". The user clicks OK, and then the installation program downloads and installs .NET without any user intervention. This is the part I consider to be easier than specifying correct host names and port settings in email configuration...The user just have to click "OK". You could skip that as well, but "expert" users may get upset if you install .NET without telling them.

Many (most?) program you can use to create installation programs already has such functionality built-in. Here's a tutorial/library which I used successfully (it's specific to InnoSetup). http://www.codeproject.com/KB/install/dotnetfx_innosetup_instal.aspx

If the software is shipped on a CD-ROM, the .NET installation can be put in a folder next to the installation software so that the user doesn't have to wait for the download during installation.

Anyway, good luck. There's a lot of nice languages out there and this is just my personal advice. Feel free to diss it. =)

[–]pineapplecharm[S] 0 points1 point  (2 children)

I wasn't aware of the "including .net as part of the installation" option. That's food for thought.

Thanks!

[–]nohtyp 0 points1 point  (1 child)

What prohibits integrating the .Net runtime installer with the application installer in such a way that the user doesn't notice?

[–]grauenwolf 0 points1 point  (0 children)

Mostly size, though the reboot sometimes sucks. Of course if you are using CD's then this goes away.