File associations and DOCICON.XML

How do I get SharePoint to open non-office documents in their client
application?

I can change the icon in DOCICON.XML/iisreset, but do I need to write my own
ActiveX control to load it?

Here's how I change the icon for vb projects:

<Mapping Key="vbproj" Value="icvbs.gif" EditText="Visual Studio"
OpenControl="SharePoint.OpenDocuments" />

The icon changes fine and "Edit in Visual Studio" shows up on the drop-down,
but (obviously) SharePoint.OpenDocuments doesn't know what to do with the
file type.

Thanks,

Jeff

Jeff,

Yes, you can do this, but it's not as easy as you'd want it to be.   The
DOCICON.XML file identifies the "OpenControl" value which is the ActiveX
component that needs to be uploaded to the users browser when they are
browsing a document library that contains a file of the type you're trying t
o
edit.  By default, Sharepoint installs "OpenDocuments" ActiveX control that
has the object named "Sharepoint.OpenDocuments".

I haven't done this, but I believe you'll have to write your own ActiveX DLL
that implements the same methods that the default Sharepoint OpenDocuments
control provides.  Then you need to create your same entry in DOCICON.XML bu
t
replace the OpenControl= statement with the name of your custom ActiveX
control that launches the editing application.

Search on Google for "OpenDocuments Control Sharepoint" and I believe you'll
find the documentation you'll need to get started.

This is not well documented, so if you have any luck please provide us with
your outcome.  I'm curious to see how difficult this is.

--Jim


"Jeff Webb" wrote:

> How do I get SharePoint to open non-office documents in their client
> application?
>
> I can change the icon in DOCICON.XML/iisreset, but do I need to write my o
wn
> ActiveX control to load it?
>
> Here's how I change the icon for vb projects:
>
>         <Mapping Key="vbproj" Value="icvbs.gif" EditText="Visual Studio"
> OpenControl="SharePoint.OpenDocuments" />
>
> The icon changes fine and "Edit in Visual Studio" shows up on the drop-dow
n,
> but (obviously) SharePoint.OpenDocuments doesn't know what to do with the
> file type.
>
> Thanks,
>
> Jeff
>
>
>

Thanks -- the best link from that search (MSDN) yields page not found when I
try to go there...

I think "not well documented" is an understatement. It's almost as if
Microsoft doesn't want other file types to open from SP. Ah, there I go
being cynical. I'll keep searching and re-post if I find a spec on the
control requirements.

-- Jeff

"Jim McCusker" <JimMcCusker@discussions.microsoft.com> wrote in message
news:E48F0209-E3AA-471F-886F-028C4524B351@microsoft.com...
> Jeff,
>
> Yes, you can do this, but it's not as easy as you'd want it to be.   The
> DOCICON.XML file identifies the "OpenControl" value which is the ActiveX
> component that needs to be uploaded to the users browser when they are
> browsing a document library that contains a file of the type you're trying
> to
> edit.  By default, Sharepoint installs "OpenDocuments" ActiveX control
> that
> has the object named "Sharepoint.OpenDocuments".
>
> I haven't done this, but I believe you'll have to write your own ActiveX
> DLL
> that implements the same methods that the default Sharepoint OpenDocuments
> control provides.  Then you need to create your same entry in DOCICON.XML
> but
> replace the OpenControl= statement with the name of your custom ActiveX
> control that launches the editing application.
>
> Search on Google for "OpenDocuments Control Sharepoint" and I believe
> you'll
> find the documentation you'll need to get started.
>
> This is not well documented, so if you have any luck please provide us
> with
> your outcome.  I'm curious to see how difficult this is.
>
>  --Jim
>
>
> "Jeff Webb" wrote:
> 

Let me now, if you find a solution,... I want to be able to enable Edit in
PDF for users with Acrobat Professional,

friendly greetings,

Joris

http://jopx.blogspot.com

"Jeff Webb" wrote:

> Thanks -- the best link from that search (MSDN) yields page not found when
 I
> try to go there...
>
> I think "not well documented" is an understatement. It's almost as if
> Microsoft doesn't want other file types to open from SP. Ah, there I go
> being cynical. I'll keep searching and re-post if I find a spec on the
> control requirements.
>
> -- Jeff
>
> "Jim McCusker" <JimMcCusker@discussions.microsoft.com> wrote in message
> news:E48F0209-E3AA-471F-886F-028C4524B351@microsoft.com... 
>
>
>

Looks like Microsoft is updating their website again.  Google's links to MS
content are all goofed up right now... hmmm.... I wonder if you go to
http://beta.search.msn.com and search for the same terms you'll get good
links?  MS is beta testing their new Search engine there... ;-)   Call me
conspiratorial....

Anyway, you should download the WSS SDK help file.  This file gives you all
the information on the WSS API as well as information regarding creating you
r
own OpenDocuments ActiveX control.

You definately have to write your own ActiveX component.  This object must
be loaded locally on the client's local PC becase the component name is
passed to the local JavaScript which in turn creates the "???.OpenDocuments"
object when you selct the Edit menu item.  This is just a small program that
passes the URL of the document to the application.

One HUGE caviat... If your software does not speak WebDAV (unlike Office
2003) then you will not be able to edit the documents directly on the
Sharepoint site.  The only workaround for this that I've found is to access
the documents using a product called WebDrive which maps the WebDAV folders
to local drives on your PC.  This is kind of a step backwards, but it works
if you're in a bind and need the functionality with legacy applications.

Bottom line, if your application can't open a document using WebDAV then
you're barking up the wrong tree...and you're only option for now is WebDriv
e.

--Jim


"Jeff Webb" wrote:

> Thanks -- the best link from that search (MSDN) yields page not found when
 I
> try to go there...
>
> I think "not well documented" is an understatement. It's almost as if
> Microsoft doesn't want other file types to open from SP. Ah, there I go
> being cynical. I'll keep searching and re-post if I find a spec on the
> control requirements.
>
> -- Jeff
>
> "Jim McCusker" <JimMcCusker@discussions.microsoft.com> wrote in message
> news:E48F0209-E3AA-471F-886F-028C4524B351@microsoft.com... 
>
>
>