Roger, sorry I can't be more specific, but as I recall from some posts on
the MSN forums, this problem exists because the web server has no file
associations for .application and .manifest. Instead of actually trying to
"run" the .application file, it just displays it. You may want to do a
search there for more details.
As a quick aside, I had high hopes for the OneClick delployment. On the
surface, it seemed to satisfy my needs for a basic installation package.
But I just ran into too many roadblocks. Take your issue, for example.
Apparently OneClick is designed for "hobbyist" developers (or at least
developers who just need a fraction of the features that the full Setup
project allows). But you apparently have to have admin rights to the web
server that is hosting your application's page if you want to use the web
deployment features of OneClick. I'm sorry, but I don't run my own web
server nor do I think it's very likely that my ISP is going to jump at my
request to change their web server settings. So, OneClick is out for
me...and likely many of the "hobbyist" developers that are ostensibly the
targets of OneClick.
- Mitchell S. Honnert
"Roger Allen" <ro***@alti-2.com> wrote in message
news:uL**************@TK2MSFTNGP15.phx.gbl...
I have created a very simple test app.
When I publish to a local drive it runs without a problem
It seems to publish to our internet website without a problem, but when i
try to execute the setup file from the website, after downloading the app
it just displays the .application XML file in IE.
What am I doing wrong?
