Click Once - dead links - Process.Start

[Scott]

I have deployed several small .net clickonce applications on vista 64
bit/vs2008 and for the most part these work fine.

In order to navigate between these applications we have developed a program
that calls these programs by Process.Start( "\\unc\publish\app.application").

On Vista, where this was developed, everything works has expected. But once
this was deployed to XP the ClickOnce applications just will not run/install.

Navigating from XP to the publish directory and double clicking the
app.application files yields no response. No events logs, nothing.

I have checked the file association for .application and that is correct. If
I deploy these apps to a web site I can install and run them on XP, I just
can't programmatically start them from XP.

Any ideas where to start?

 

[Linda Liu[MSFT]]

Hi Scott,

Are the ClickOnce applications 32-bit or 64-bit applications?

For more information on 64-bit applications, visit the following link:
"64-bit Applications"
http://msdn.microsoft.com/en-us/library/ms241064.aspx

If they're 64-bit applications, you may refer to the following MSDN
document on how to publish these application:
"How to: Deploy a 64-bit Application Using ClickOnce"
http://msdn.microsoft.com/en-us/library/ms165430.aspx

Navigating from XP to the publish directory and double clicking the

app.application files yields no response. No events logs, nothing.

Do you mean that web server that contains the ClickOnce applications are
Vista 64-bit machine and you try to install the applications to a Window XP
client machine by double clicking the .application files?

If so, you should not be able to launch the ClickOnce applications
programmatically from Window XP machines.

Sincerely,
Linda Liu
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Scott]

The applications are C#/CPUANY.These applications work on XP when deployed to
a web server. I can not get them to work when deployed to a share point.

I am in the process of moving my build environment back to XP to attempt to
narrow this down a bit.

 

[Scott]

I moved by build environment to XP/SP2/VS2008 32 bit. Rebuilt and redeployed
a simple clickonce application to a second sever (UNC path), 2003 server 32
bit.

Then I tried to launch that application from the deployment directory with
the same results. So this is not a vista vs xp thing. It looks like clickonce
from a unc path just does not work on XP.

My question then, is this functionality supported on XP/SP2? If it is, how
do we go about finding out what is wrong. The property/Publish tab for the
project sure indicates that file path is a valid destination.

"Opens with:" for the .application extension is set to "Application
Deployment Support Library", which is the same on the vista machines where
this works correctly.

By the way, these clickonce apps work on all copies of vista that we have
installed here, both 32 and 64 bit.

 

[Scott]

I went to a new install of XP/SP2/32 bit workstation with all windows
updates, and .net 3.5 runtime.

This machine runs all the applications just fine.

So I guess the problem is with that specific machine.

 

[Linda Liu[MSFT]]

Hi Scott,

Thank you for your feedback!

I performed a test deploying a ClickOnce application built in VS2008 to a
Windows Vista 32 bit machine. The publishing folder is a UNC path.

Then I navigate to the UNC path from a Windows XP machine and double-click
the .application file. The ClickOnce application is installed on the
Windows XP machine and is run properly.

This machine runs all the applications just fine. So I guess the problem

is with that specific machine.

Do you mean that you can install the ClickOnce application from a UNC path
to other Window XP machines? If so, the problem may only exists on this
particular client machine. You may have a try restoring/reinstalling .NET
Framework on the XP machine in question to see if the problem can be fixed.

Sincerely,
Linda Liu
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

This posting is provided "AS IS" with no warranties, and confers no rights.