T
Tony Yums
Hi,
I was wondering if someone had any ideas on the following :
What is the reason to use HTA (HTML application) in stead off (or visa
versa) ASP. NET ?
We have an asp HTA website, but want to move to asp.net.
I don't see any reason to keep HTA. Especially, if you check that on
other platforms (Mac, etc) HTA is not recognized.
Ok, we know that HTA gives the ability to a nice front end application
behavior, feeded by server communication, and allows to have full access
to the client computers environment (no security stuff).
Which is cool to check for any prerequisites...But is not necessary for us.
As we can have all our functionality using plain ASP.Net, I proposed to
my colleagues to skip the HTA approach. But they are convinced yet.
Are there any caveats ?
Thanks for any comment or ideas on this,
Greets
Tony Yums
I was wondering if someone had any ideas on the following :
What is the reason to use HTA (HTML application) in stead off (or visa
versa) ASP. NET ?
We have an asp HTA website, but want to move to asp.net.
I don't see any reason to keep HTA. Especially, if you check that on
other platforms (Mac, etc) HTA is not recognized.
Ok, we know that HTA gives the ability to a nice front end application
behavior, feeded by server communication, and allows to have full access
to the client computers environment (no security stuff).
Which is cool to check for any prerequisites...But is not necessary for us.
As we can have all our functionality using plain ASP.Net, I proposed to
my colleagues to skip the HTA approach. But they are convinced yet.
Are there any caveats ?
Thanks for any comment or ideas on this,
Greets
Tony Yums