ClickOnce, File Extensions

  • Thread starter Thread starter Ken Lemieux
  • Start date Start date
K

Ken Lemieux

Does the released version of .Net Framework 3.5 now support file extension
association using ClickOnce deployment model?

If so, how do I implement the associations?
 
I've found part of the answer myself. The application manifest now contains a
<fileAssociation> element which has four required attributes to support file
association.

The only question that remains now is where on the project's property pages
does this information get entered?
 
Hi Kenneth,

This is a quick note to let you know that I'm performing research on this
issue and will get back to you ASAP.

I appreciate your patience!

Sincerely,
Linda Liu
Microsoft Online Community Support

==================================================
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.
 
Hi Kenneth,

.NET Framwork 3.5 supports file associations in a ClickOnce application.
The requirements are as follows:

1) File associations are only supported for Orcas apps and up (look for an
assembly dependency on system.core.dll or greater in the manifest)
2) Your app must request Full Trust Permissions and be Offline Capable
(deployment generates shortcuts/ARP entry)
3) Only stand-alone apps are supported. File associations are not supported
for WPF browser hosted apps or VSTO plugins

For each file association you want your app to support, add xml similar to
the following to the application manifest (.exe.manifest)

<fileAssociation xmlns="urn:schemas-microsoft-com:clickonce.v1"
extension=".nyt"
description="New York Times Document"
progid="NYT.Document"
defaultIcon="nyt.ico"
/>

Currently, we can't either set file associations from the Properties
Designer of a project or use Shell Set File Assocations UI to manage
ClickOnce file associations. We can only add the above xml to the
application manifest manually. We are working with the Shell team to
provide better support for this in the future.

For more information about ClickOnce file associations, please refer to the
following MSDN document:
http://msdn2.microsoft.com/en-us/library/bb882599(VS.90).aspx

Hope this helps.
If you have any question, please feel free to let me know.

Sincerely,
Linda Liu
Microsoft Online Community Support
 
Back
Top