Home Dashboard Directory Help
Search

ClickOnce does not register file associations for 32bit apps on 64bit system by Miroslav Bajtoš


Status: 

Resolved
 as Won't Fix Help for as Won't Fix


7
0
Sign in
to vote
Type: Bug
ID: 772457
Opened: 11/27/2012 11:22:41 PM
Access Restriction: Public
2
Workaround(s)
view
3
User(s) can reproduce this bug

Description

After a ClickOnce application with file association is installed on a 64bit system (e.g. Windows 7 64bit), the file associations are working in 64bit applications only.

See StackOverflow's answer for technical details: http://stackoverflow.com/a/1901412/69868
Details
Sign in to post a comment.
Posted by bsee08 on 11/11/2013 at 6:45 AM
Struggling to understand why this was marked as "won't fix". Clickonce is Microsoft's recommended way to deploy a program and keep it up to date on an internal network. This is a reproducible bug with a number of concerned followers, as evidenced by the Stackoverflow post. What was the reasoning behind marking as "won't fix"?
Posted by Sqdw on 1/24/2013 at 1:34 AM
Hi, is there any update on this issue?
Posted by Miroslav Bajtoš on 12/4/2012 at 11:24 PM
Hello

Is there any update on this issues? Will Microsoft provide a fix or patch?
Posted by Microsoft on 11/29/2012 at 12:30 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Miroslav Bajtoš on 11/28/2012 at 5:00 AM

Thank you for a quick reply.

I am little bit confused, what do you need from me to help you track down the issue?

Please note that it is important to install the application on 64bit system and then open .xyz file from a 32bit application running on this 64bit system.
Posted by Microsoft on 11/28/2012 at 2:23 AM
Sorry for the preview reply, not dmp file, it's a video or something. I published the app in win8(x64), i also can luanch the .xyz file in win7(x32), it's ok in my case.
Posted by Microsoft on 11/28/2012 at 1:40 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting a dmp file. Please submit this information to us within 3 business days. We look forward to hearing from you with this information.
Posted by Eugene Baranov on 11/28/2012 at 1:31 AM
There was a ticket on this already at https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=521282 but why it doesn't work anymore?
Posted by Microsoft on 11/27/2012 at 11:50 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 ivl on 4/15/2014 at 1:26 AM
I cannot verify that this issue is resolved in .NET 4.5 or 4.5.1. On a 64bit machine, the 64bit CLSID entry is created, but a CLSID entry under the Wow6432Node is NOT created. This issue therefore still exists, for me at least.
Posted by Soumitra Mondal on 4/7/2014 at 10:16 AM
This issue was already resolved in .Net 4.5 release.