Page 1 of 1

HELP with .NET 2.0

Posted: Mon Mar 09, 2009 4:57 pm
by rstraub
Ok, so we've established that the check script for the .NET 2.0 SP1 runtimes is incorrect according to the latest information from Microsoft. Here is my problem... My application requires the .NET 2.0 runtimes or higher. I have 100+ clients with Windows 2000 machines. I either need to be able to edit the script to allow 2000 SP4 installs or use .NET 2.0 without SP1. I had never created an installer before InstallAware7 so I'm not experienced enough to know how to edit that checknet21 script to include Windows 2000 SP4 and with InstallAware8, you cannot add .NET 2.0, only SP1. I need some help here as I have several clients waiting (very impatiently) for this installer.

Posted: Mon Mar 09, 2009 7:34 pm
by MichaelNesmith
Please do not cross post the same topic to multiple places. Would you be so kind as to post the reply I already gave you in your duplicated posting here for everybody to see? Thank you.

I would be glad to!

Posted: Tue Mar 10, 2009 4:30 am
by rstraub
Here is the official reply from Mr. Nesmith to the same question submitted to InstallAware "support". Keep in mind that I paid for this software, I am not using the free evaluation version.

"You will need to edit the runtime installer script to add Windows 2000 support. Its very easy. If you want us to do it for you, you will need to purchase a support incident package at www.installaware.com/support-service-options.htm. We regret we cannot edit customer projects for free.

InstallAware Software Corporation
Home of the Next Generation MSI Installer
336 Guerrero, San Francisco, CA 94103
415 839 5017 (voice)
415 358 4094 (fax)
www.installaware.com"
So, because a script that is included with InstallAware is INCORRECT, I need to pay InstallAware if I would like it fixed? The script that I created is just fine. The problem is with a script included in your program and there is no support for that? On top of that, you make a condescending post to a PAYING customer in your own forum? I realize that you will immediately take this post down, so I have copied it for my employer and yours as well.

Posted: Tue Mar 10, 2009 9:18 am
by eugen.cocalea
Oh, the drama!

If you found out that that checknet2sp1 script is incorrect, I bet you asked 'what is incorrect about it' and then, using just a bit of programming skills, you could modify that script.

Anyway, drama aside, what is wrong with that script? I am not using that framework, but maybe I will / others are.

Posted: Tue Mar 10, 2009 9:31 am
by MichaelNesmith
Nobody is going to take your post down - at least not yet.

As I have already explained to you, at the time our runtime installer scripts were made, all Microsoft documentation indicated that Windows XP was the minimum OS for these target frameworks.

If Microsoft has now upgraded that documentation and you have verified it to work on Windows 2000 with Service Pack 4, this will be taken into consideration by InstallAware R&D for inclusion in the next InstallAware update. Or, they may elect to not do this for a variety of reasons, it is up to R&D where and when they will include this enhancement in the product.

Now what we're selling as part of the InstallAware product you have purchased is the setup compiler - and not the service of building or customizing your installers for you. If you don't understand that, that's really unfortunate; do a reality check and just ask yourself if you would harass Microsoft support to edit your C# programs for you, guess what they will say?

As the programmer of your own installation it is your job to make this change to your scripts instead of harassing InstallAware support about it - people on this forum can tell you how easy it is to make this change; in fact if you had even bothered to look at your setup scripts, you would have seen how easy it is to implement. I know for a fact you didn't even spend one second to look at the scripts of your own installation and instead are spending days harassing support.

This is your only (and public) warning - any further harassment will result in permanent and immediate termination of all your InstallAware support privileges. We're all working very hard here and we don't appreciate customers like you who have this unfounded belief of having purchased a slave coder along with their InstallAware product.