Issues with the deployment Manifest

Our application is built with VS2005 Beta 2. We uses ClickOnce to deploy the
application. Here is the issues we have experienced on some client machine.
When we click the install button from the publish page, the deployement
manifest is open in the browser instead of lauching the application manifest
On other machine, every is fine, the install button lauch the installation
sequence on the client.

Any idea what could the problem.

Regards,

Answer this question

Issues with the deployment Manifest

Ed Mercado
This has happened to me at least 20 times on at least 10 computers when trying to install. If the pc has fresh OS install it works perfect. But it seems that if it has been up for a while or if I have already installed ~~the~~ a ClickOnce app it reads the XML instead of executing the setup.

Kind of wondering why it did this myself. The only way I could get around it was to either grab your publish folder in your project folder or download the files from where you published the app.

After it is installed it will update w/o error or obiously not opening the xml file again.

Hopefully this can hold you over till someone has the real way to do it.

Zac
Arti.Desai
Dany,

One of the great features of ClickOnce is the prereqs. One of which is .net 2.0. I have had many installs work perfect from scrach installing 2.0 as a prereq right off the publish site. Half of those then ran the XML and the other half read it.
bholemaharaj
Zac,

Does it mean that, as of now, there is no fix to this problem

Dany C.
Bermychild
Dear Zac,

I found the solution to this issue. Have a look, that might also help you.

http://msdn2.microsoft.com/en-us/library/ms165433(en-us,vs.80).aspx#

Regards,

Dany C.
Tami
To be honist I haven't really looked to hard. Been real busy with updates and those nullable dataset changes. I just used the work-around and use my own app update methods. Anywhere I looked I had responses like I gave you: "Yea I've seen that before..."

I'm heading to that VSLive! confrence next week and I figured I would find out what the deal is when I'm there.
SoftArea51
Sounds like .NET 2.0 is not installed on the client machine, so the MIME extension mappings have not been set up to launch the app with ClickOnce.
dboone
Dany,

Thanks, there is some good info on this page. It does have an answer to IE showing xml but it is kind of an all or none answer. It's really wierd that it works some times and other times it doesn't.

For example 2 days ago I opened the publish site with a fresh pc and clicked install which launched the .net2 framework installer. After installed and restarted it would just pull xml. Just for kicks two seconds ago I pulled it up on this pc and up pops the install app dialog box. I know there is a method going on somewhere in this madness, I just can't find it, gotta love it!

I will probably just stick to one of the servers that have the .net2 framework installed. Perhapse it will get rid of the fluxuations. Thanks again,

Zac
NielO
Thanks Brian for your comment.

I think you might be right. It might have something to do with the mime type. In fact machines who failed was testing machine with a brand new XP installation without .Net 2.0. Those who worked, was our development machines. In our deployment scenario, it is assume that almost all machine won’t have .Net 2.0 pre-install, so what is the solution < xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Regards

Dany C.
Issues with the deployment Manifest

Answer this question