ASP.Net <> HTA

[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

[Jon Paal]

what the heck is an "asp HTA website" ?

[Kevin Spencer]

Hi Tony,

You've already identified the major players in the argument: Cross-browser
support on the oned hand, and a nice "Windows Forms-Like" front-end on the
other hand. There are other reasons, though, to switch to ASP.Net.

First, on the negative-HTA side, you have some serious security issues with
HTA, as it doesn't run in the browser sandbox. Also, your users are
responsible for disabling any Service Pack settings, etc. that may prevent
the HTA from working in the client browser. This makes support more
expensive.

Second, as an ASP.Net app exists and runs on the server, you always have one
version and one copy of the app to work with. You can fix it, extend it, and
maintain it real-time. This simplifies things a good bit.

Third, ASP.Net is .Net. That alone, with all of its implications (too many
to list), makes it worthwhile to use.

If you need a nice-looking front-end, consider using a SWF.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Big things are made up of
lots of little things.

"Tony Yums" <ra*******@sorynospam.com> wrote in message
news:43***********************@news.skynet.be...

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

[Kevin Spencer]

http://msdn.microsoft.com/library/de...taoverview.asp

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Big things are made up of
lots of little things.

"Jon Paal" <Jon nospam Paal @ everywhere dot com> wrote in message
news:O2*************@TK2MSFTNGP10.phx.gbl...

what the heck is an "asp HTA website" ?

[Tony Yums]

Jon Paal wrote:

what the heck is an "asp HTA website" ?

Hi Jon,

here's an explenation of HTA :

Using HTA (Hypertext Application) with asp pages.
Full info @
http://msdn.microsoft.com/workshop/a...taoverview.asp

Greets
Tony

[Tony Yums]

Hi Kevin,

thanks for the argumentation.
This seems supporting my point of view :)

Thanks

Tony
Kevin Spencer wrote:

Hi Tony,

You've already identified the major players in the argument: Cross-browser
support on the oned hand, and a nice "Windows Forms-Like" front-end on the
other hand. There are other reasons, though, to switch to ASP.Net.

First, on the negative-HTA side, you have some serious security issues with
HTA, as it doesn't run in the browser sandbox. Also, your users are
responsible for disabling any Service Pack settings, etc. that may prevent
the HTA from working in the client browser. This makes support more
expensive.

Second, as an ASP.Net app exists and runs on the server, you always have one
version and one copy of the app to work with. You can fix it, extend it, and
maintain it real-time. This simplifies things a good bit.

Third, ASP.Net is .Net. That alone, with all of its implications (too many
to list), makes it worthwhile to use.

If you need a nice-looking front-end, consider using a SWF.

[Jon Paal]

I know what HTA is and I know what ASP is.
These are independent tools and I see no such definition of anything as an "ASP-HTA website".

--------------------------------------------------------
Politicians,like underwear,should be changed often and for the same reasons.

[Kevin Spencer]

That would be a web site that employs ASP on the server, and HTA on the
client.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Big things are made up of
lots of little things.

"Jon Paal" <Jon nospam Paal @ everywhere dot com> wrote in message
news:uM****************@TK2MSFTNGP12.phx.gbl...

I know what HTA is and I know what ASP is.
These are independent tools and I see no such definition of anything as an
"ASP-HTA website".

--------------------------------------------------------
Politicians,like underwear,should be changed often and for the same
reasons.

[Jon Paal]

A web site can't employ HTA.
That has to be installed on the client by the user.

Not to mention the incredible security risk....
--------------------------------------------
I would rather chew on tinfoil than code in C#.