I was looking for a list for all ActiveX controls used by Microsoft Office SharePoint Server (MOSS) 2007, but it seems like this list is not available at this time. The best references I could find was the SharePoint team blog post on web browser compatibility at http://blogs.msdn.com/sharepoint/archive/2006/07/19/671735.aspx, the documentation on browser compatibility at http://technet2.microsoft.com/Office/en-us/library/ff6c5b8c-59bd-4079-8f0b-de4f8b4e0a861033.mspx and the Client Side API reference at http://msdn2.microsoft.com/en-us/library/ms440037.aspx. However, each one of those misses at least a few of the controls.
MOSS2007에서 사용되는 ActiveX 컨트롤 리스트를 찾아봤지만, 현재로선 아직 제공이 안되는 것 같다. 내가 찾을수 있었던 가장좋은 레퍼런스는 쉐어포인트 팀 블로그에 있는 웹브라우저 호환성, 브라우저 호환성 (techNet) 문서, 그리고 Client Side API 레퍼런스였다. 그러나, 각사이트들은 몇몇 컨트롤들을 빼먹었다.
Web browser compatibility is, by the way, was my main motivation to working on this list. I need to figure out what features would be missing if you're running Firefox or Safari. For this reason, I am also trying to list what happens in those clients that do not support these ActiveX controls and what possible workarounds exist. I also wanted to have a better understanding of how these features are implemented in SharePoint.
암튼 웹브라우저 호환성은 내가 이 리스트를 만들게 된 주요인이었다. 여러분들이 Firefox나 Safari를 쓴다면 어떤 기능들이 빠졌는지 난 알고 싶었다. 그런 이유때문에, 또한 나는 ActiveX 컨트롤을 지원하지 않는 클라이언트 (프로그램)에서 어떤일이 일어날는지 그리고 (그런 문제들을 해결하는) 어떤 가능한 대안들이 있는지 리스트를 만들고자 했다. 또한 SharePoint 내에 그런 기능들이 어떻게 구현되었는지 보다 이해를 돕고자 했다.
To create this list, I started with a search for ActiveX-related keywords like "object" and "classid" in all files under "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12". I cut off some of the unrelated items, group them by the name of the control and edited the results. With that, I looked for specific references to these controls on the web. The last piece was to understand the non-IE behavior and look for any workarounds.
이런 리스트를 만들기 위해, 나는 "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12" 폴더내에 "Object" 와 "classid"같은 ActiveX 관련 키워드를 검색하기 시작했다. 관련없는 것들은 삭제하고, 컨트롤의 이름들로 묶고 결과를 편집했다. 그것들을 가지고 웹(인터넷)에서 그 컨트롤에 대한 세부적인 레퍼런스를 찾았다. 마지막으로 IE가 아닐때의 동작을 이해하고 그것들에 대한 어떤 대안이 있는지 찾았다.
It was interesting to see how a good amount of SharePoint is implemented in scripts that you can actually look at. You also can verify that the team put a lot of effort into browser compatibility... Here are my findings, in alphabetical order by the name of the ActiveX control.
여러분들이 실제적으로 보는 SharePoint 에서 얼마나 많은 양의 스크립트들이 구현되었는지 알게 되는것이 흥미로웠다. (이에) 여러분들이 (SharePoint 개발)팀이 브라우저 호환성에 얼마나 많은 노력을 기울였는지 확인 할 수 있다. 이게 내가 찾은 ActiveX 컨트롤 명을 알파벳 순으로 정렬한 것이다.
DiagramLauncher
Server Files: TEMPLATE\LAYOUTS\1033\BFORM.JS, TEMPLATE\LAYOUTS\1033\CORE.JS, TEMPLATE\LAYOUTS\1033\INIT.JS, TEMPLATE\LAYOUTS\1033\OWS.JS
Client File: DGRMLNCH.DLL
Function: Launch Microsoft Office Visio to open diagrams
Non-IE behavior: The browser will offer to save the file locally instead of launching the application. The option to "Open with Visio" will not show.
DigitalSignatures
Server Files: TEMPLATE\LAYOUTS\INC\1033\IntlCoreStrings.js, TEMPLATE\LAYOUTS\INC\Core.js, TEMPLATE\LAYOUTS\INC\intlcorestrings.js, TEMPLATE\LAYOUTS\SignatureDetails.FormServer.aspx
Function: Digital Signature for Microsoft Office clients
Non-IE behavior: You cannot sign documents, but you can view signatures.
ExportDatabase
Server Files: TEMPLATE\LAYOUTS\1033\CORE.JS, TEMPLATE\LAYOUTS\viewtype.aspx, TEMPLATE\LAYOUTS\1033\OWS.JS
Client File: OWSSUPP.DLL
Also Known As: SharePoint Export Database Launcher
Function: Export list to a Microsoft Office Access database
Non-IE behavior: Option to "Open with Access" will not show.
ListNet
Server Files: TEMPLATE\LAYOUTS\1033\CORE.JS, TEMPLATE\LAYOUTS\1033\CORE.JS, TEMPLATE\LAYOUTS\1033\OWS.JS, TEMPLATE\LAYOUTS\1033\OWS.JS
Client File: STSLIST.DLL
Also Known As: Microsoft Office List 12.0
Function: Edit list in Datasheet view
Reference: http://msdn2.microsoft.com/en-us/library/ms416795.aspx
Non-IE behavior: The option to "Edit in Datasheet" will not show.
NameCtrl
Server Files: TEMPLATE\LAYOUTS\1033\INIT.JS, TEMPLATE\LAYOUTS\1033\OWS.JS
Client File: NAME.DLL
Also Known As: NameCtrl Class
Function: Display presence information for people, integrating with Outlook (mail, calendar) and Communicator (instant messaging)
Reference: http://msdn2.microsoft.com/en-us/library/ms455335.aspx
Non-IE behavior: Presence information will not show.
OISClientLauncher
Server Files: TEMPLATE\LAYOUTS\1033\IMGLIB.JS, TEMPLATE\LAYOUTS\upload.aspx
Client File: OISCTRL.DLL
Also Known As: OSIClientLauncher Class
Function: Integration with the Office Picture Manager
Reference: http://msdn2.microsoft.com/en-us/library/ms954038.aspx
Non-IE behavior: Integration with Picture Manager will not show.
OpenDocuments
Server Files: TEMPLATE\LAYOUTS\1033\HtmlEditor.js, TEMPLATE\XML\DOCICON.XML
Client File: OWSSUPP.DLL
Also Known As: SharePoint OpenDocuments Class
Function: Launch Office applications to open documents
Reference: http://msdn2.microsoft.com/en-us/library/ms454230.aspx
Non-IE behavior: The browser will offer to save the file locally instead of launching the application. The option to "Edit In (Microsoft Office application)" will not show.
OpenXMLDocuments
Server Files: TEMPLATE\LAYOUTS\1033\HtmlEditor.js, TEMPLATE\LAYOUTS\INC\Core.js, TEMPLATE\LAYOUTS\ctdmsettings.aspx, TEMPLATE\XML\DOCICON.XML
Client File: INLAUNCH.DLL
Also Known As: SharePointOpenXMLDocuments
Function: Launch InfoPath to open forms
Reference: http://msdn2.microsoft.com/en-us/library/ms452435.aspx
Non-IE behavior: The browser will offer to save the file locally instead of launching the application. The option to "Open with InfoPath" will not show.
PersonalSite
Server Files: None?
Client File: PORTAL~1.DLL
Also Known As: PersonalSite Class, PortalConnect.PersonalSite
Function: Adds your my site to a list of SharePoint sites maintained by the Office client
Non-IE behavior: No client-side knowledge of where your mysite is located.
Ppactivex
Server Files: TEMPLATE\CONTROLTEMPLATES\sldlibtemplates.ascx, TEMPLATE\FEATURES\SlideLibrary\SldLib\schema.xml, TEMPLATE\LAYOUTS\1033\SLDLIB.JS
Function: Integration with PowerPoint for Slide Library Templates
Non-IE behavior: The Slide Library integration with PowerPoint will not work.
RTEDialogHelper
Server Files: TEMPLATE\LAYOUTS\1033\BFORM.JS, TEMPLATE\LAYOUTS\1033\FONTDLG.HTM, TEMPLATE\LAYOUTS\1033\HtmlEditor.js
Client File: MSHTMLED.DLL
Also Known As: Rich Text Editor, DlgHelper, HtmlDldSafeHelper Class
Function: Rich Text Editor used to edit wikis, rich text web part
References: http://msdn2.microsoft.com/en-us/library/ms535238.aspx, http://msdn.microsoft.com/workshop/author/editing/tutorials/html_editor.asp
Non-IE behavior: A simpler multi-line text editor with no Rich Text capabilities will show. Consider using the Telerik control, which is available for free download at http://www.telerik.com/sharepoint and works with non-IE browsers.
SpreadsheetLauncher
Server Files: TEMPLATE\LAYOUTS\1033\BFORM.JS, TEMPLATE\LAYOUTS\1033\INIT.JS, TEMPLATE\LAYOUTS\NewTranslationManagement.aspx, TEMPLATE\LAYOUTS\lstsetng.aspx, TEMPLATE\LAYOUTS\new.aspx, TEMPLATE\LAYOUTS\sledit.aspx, TEMPLATE\LAYOUTS\slnew.aspx, TEMPLATE\LAYOUTS\1033\INIT.JS
Client Files: OWSSUPP.DLL, OWSCLT.DLL
Also Known As: SharePoint SpreadSheet Launcher
Function: Integration with Excel to import and export lists
Reference: http://msdn2.microsoft.com/en-us/library/ms427792.aspx
Non-IE behavior: Options to Export to Excel and Import Spreadsheet will not show. If you register an application to handle the .iqy extension, you might be able to export spreadsheets.
Stssync
Server Files: TEMPLATE\LAYOUTS\1033\BFORM.JS, TEMPLATE\LAYOUTS\1033\INIT.JS
Client File: OWSSUPP.DLL
Also Known As: SharePoint Stssynch Handler
Function: Connect to Outlook to synchronize lists
Reference: http://msdn2.microsoft.com/en-us/library/ms456225.aspx
Non-IE behavior: Option to "Connect to Outlook" will not show. You should be able register a client application to handle the stssync:// protocol.
UploadCtl
Server Files: TEMPLATE\CONTROLTEMPLATES\DefaultTemplates.ascx, TEMPLATE\LAYOUTS\1033\BFORM.JS, TEMPLATE\LAYOUTS\1033\INIT.JS, TEMPLATE\LAYOUTS\copy.aspx, TEMPLATE\LAYOUTS\updatecopies.aspx, TEMPLATE\LAYOUTS\upload.aspx, TEMPLATE\XML\FLDTYPES.XML,
Client File: STSUPLD.DLL
Also Known As: STSUpld UploadCtl Class
Function: Multiple File Upload
Reference: http://msdn2.microsoft.com/en-us/library/ms456628.aspx
Non-IE behavior: Only single file upload is available. Option for "Multiple File Upload" will not show.
Disclaimer: Please note that this list might be incomplete. Also, unless supported by one of the reference links to microsoft.com, these are my conclusions based on the data I could gather. Some of these findings could be specific to my install of MOSS 2007 Enterprise (RTM, complete install, no updates) and Windows Vista client with Office 2007 (RTM, no updates). Your results may vary and your specific configuration might lead to a different set of results.
P.S.: Duray Akar from Microsoft Premier Support just reminded me that there is an umbrella link on Client Side API covering most of those reference links I mentioned and I added that link to the top paragraph on this post. He was kind enough to include a reference back to this blog post in the community section of the page.
P.P.S.: In environments where only pre-installed ActiveX controle are allowed, you might need to package and deploy these ActiveX controls to your clients. However, to my knowledge, there are no downloadable packages that provide these controls in a form they could be pre-installed on a client. However, most of them will be installed if you deploy Office 2007 or Office 2003 on the client.
원문
http://blogs.technet.com/josebda/archive/2007/03/26/searching-the-visible-moss-2007-code-for-activex-references.aspx


