ClickOnce: incomplete file association in Windows 7 x64 - by Eugene Baranov

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 521282 Comments
Status Closed Workarounds
Type Bug Repros 7
Opened 12/18/2009 3:04:42 PM
Access Restriction Public


ClickOnce does not create file association's registry keys for x32 registry branch.

From "":

"I investigated some further and found that ClickOnce installer creates the following open verb for any associated file extension (GUID is unique per application):

rundll32.exe dfshim.dll, ShOpenVerbExtension {dce01888-35e8-4df3-af35-cd971f520d8d} %1
Using Process Monitor I found that x32 bit version fails to open HKCU\Software\Classes\Wow6432Node\CLSID\{dce01888-35e8-4df3-af35-cd971f520d8d} registry key. (x64 version successfully opens it at HKCU\Software\Classes\CLSID\{dce01888-35e8-4df3-af35-cd971f520d8d}.)"
Sign in to post a comment.
Posted by Håkan Olsen on 10/12/2011 at 1:42 AM
To many developers it is likely to make sense that ClickOnce applications actually work as intended. Are there other technologies and features that do not make sense to Microsoft whether they work as intended?

Should we abandon ClickOnce, or does it make sense to solve this issue? If it makes sense, when can we expect to see a solution?
Posted by Lee [MSFT] on 4/28/2011 at 2:00 PM
We have fixed this issue for the next version of .NET. As mentioned in an earlier post, it has not yet been fixed in 4.0 but we're looking for a release in which it might make sense to include this.
Posted by Jay Clayton1 on 3/21/2011 at 12:06 PM
Has anymore work been done on this issue?


Jay Clayton
Posted by Microsoft on 10/5/2010 at 11:01 AM
This issue has not been fixed in .NET 4.0.

Posted by Dan Frias on 10/1/2010 at 10:16 AM
Is it known whether this problem still exists, or if a new version of ClickOnce has been deployed that addresses this issue? I am currently experiencing the same issue with a program I am building and this will be a major stumbling block if deployed to customers in this non-working state.

Thank you,
Posted by Microsoft on 1/11/2010 at 11:09 AM
Thank you for taking time to report this bug.

We have been able to reproduce the issue on our test machines. This issue seems to be related because of changes in the way file associations are handled in windows7 and not due to changes in ClickOnce. I am investigating the issue and would like to assure you that this issue will be fixed in a future release of ClickOnce.

Software Development Engineer, ClickOnce.
Posted by Microsoft on 12/22/2009 at 12:16 AM
Thanks for your feedback. We were able to reproduce the issue you are seeing. We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 12/21/2009 at 3:19 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(