Home Dashboard Directory Help
Search

.Net ClickOnce deployment not working as RemoteApp or Citrix XenApp on Server 2008 / Server 2008 R2 by Wendell W. Pinegar


Status: 

Closed
 as Won't Fix Help for as Won't Fix


7
0
Sign in
to vote
Type: Bug
ID: 653362
Opened: 3/24/2011 10:51:32 AM
Access Restriction: Public
5
Workaround(s)
view
7
User(s) can reproduce this bug

Description

We have attempted to deploy a commercial application that chose to use .Net ClickOnce as the deployment model. Due to network latency issues we would like to deploy the application onto a Windows Server 2008 RDP server as a RemoteApp published application. After working with application we found that we can easily install the application for a single user by running the ClickOnce installer from a full RDP session on the server, however when we attempt to start the application by publishing the deployment startup through a RemoteApp, the found that the application won't start and that no ClickOnce deployment error log file is created. We have confirmed this behavior exists on Server 2008 and Server 2008 R2 but ClickOnce operates correctly when running as a published application on Server 2003 running Citrix Presentation Server 4.5. We found that we could easily duplicate the issue by publishing Internet Explorer as a RemoteApp and attempting to run a ClickOnce sample application available on the Internet. Attempting to find information on this limitation has been difficult. Is this a known issue or limitation with .Net ClickOnce deployment on Server 2008 (and higher) that would prevent ClickOnce from working as RemoteApp?

Duplicating the issue is very easy. Simply publish Internet Explorer in Server 2008 (or 2008 R2 w/SP1) and visit the website below. Attempt to launch the sample ClickOnce application. It will fail to launch and will not generate any information on why it failed. Now logon to the console of the server, open Internet Explorer, and try the operation again. This time it will succeed and you can launch the ClickOnce application. This appears to be a bug in the .Net framework when running a ClickOnce on Server 2008 (and higher) and is only present when running the ClickOnce application as a RemoteApp or as a Citrix published application (on XenApp 5.0 or higher).

Sample Click-Once Sample Application
http://www.lescasse.com/ClickOnce/plus/plus.aspx
Details
Sign in to post a comment.
Posted by Ravi Kishore Chandrupatla on 6/19/2013 at 3:55 AM
I too having the same issue. Any update on this? I am having problem on Windows Server 2008 R2 (64-bit).
Posted by AlunJ on 6/27/2012 at 4:48 AM
Still an issue in 2012
Posted by AaronJRich1 on 5/24/2011 at 7:57 AM
I am having this same issue. Any updated on this?
Posted by Microsoft on 4/26/2011 at 12:45 PM
This scenario is not supported, see the following KB article - http://support.microsoft.com/kb/2020945

While many have found ways to get this working, especially on older OS versions, there is no guarantee for Windows 2008 or R2.
Posted by Wendell W. Pinegar on 4/5/2011 at 11:35 AM
I've added a post-back to the original MSDN forum discussion on this issue.

http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/7f41667d-287a-4157-be71-d408751358d9/#a59b1615-8e65-43f7-be2e-0b7b60af7a49
Posted by Wendell W. Pinegar on 4/5/2011 at 11:29 AM
The URL to a click-once sample application is included in the problem description. We have used this sample application to reproduce the problem. We have included the URL again below. Let us know if you need anything else!

Click-Once Sample Application
http://www.lescasse.com/ClickOnce/plus/plus.aspx
Posted by Microsoft on 4/5/2011 at 3:04 AM
Hello,
We need a working repro provided in order to investigate.
Could you please provide us with a sample project zip?

we need a working repro provided in order to investigate.

Posted by Microsoft on 3/25/2011 at 3:23 AM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by Microsoft on 3/24/2011 at 5:15 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by AlunJ on 6/27/2012 at 4:50 AM
when you build change the exe to be an exe not exe.application then point at the application file.

bit of a pain when you do an update as you still point tot he old version.
Posted by z0iid on 6/13/2011 at 1:09 PM
**EDIT** __COMPAT_LAYER may not work in 2008 and above, I haven't tested it.
Posted by z0iid on 6/13/2011 at 1:06 PM
Compatibility mode is an acceptable workaround. You can either set compatibility settings directly to IE (XP SP2), or create a batch file, vbs, or autoit that calls IE with the URL (direct to the .application) as a parameter, then set compatibility mode to that batch file.

We were able to verify that it never works without compatibility mode, and always works with compatibility mode with 2 separate ClickOnce apps.

One caveat is that the batch file has to live locally, unless you either use the SET __COMPAT_LAYER command

http://support.microsoft.com/kb/286705

or the Compatibility Administrator

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=en

-c
Posted by Patrick Gunerud on 4/6/2011 at 7:17 AM
I was able to get this to successfully working on a 2008 R2 Terminal Server by configuring the Remote App as "C:\windows\explorer.exe" then setting the command-line arguments to be the path to the .application manifest. This will launch explorer which will then launch the ClickOnce application. Explorer will disappear after the ClickOnce application is launched.
Posted by Wendell W. Pinegar on 3/30/2011 at 3:44 PM
Some applications may be configured to run locally from an RDP server once they have been deployed to the server using standard ClickOnce deployment. After the deployment has occurred with a specific account, open the contents of the ClickOnce deployment cache for the user, locate the files for the application and copy the files to an alternate "global" location outside of the user's profile. Publish the already deployed .Net application as a RemoteApp. If you are very fortunate the application will execute correctly or if not additional "application specific" setup may be required for each user.