exe???
???Path???=???C:\\fdm.exe %user-id% %contact-id%???
???SessionType???=???REG_DWORD:00000001???
???ExtensibleMenu???=???ConversationWindowActions;MainWindowRightClick???
Figure A.8 Menu Items from a Default MOC Installation
416 Appendix A ??? Customizing the MOC Client
7. Save it as custommenu.reg.
8. Double-click to execute the Registry fi le.
9. Start MOC.
10. Initiate a conversation with another user in your Contacts list.
11. Click on the Down arrow on the top left of the Conversation window.
12. Click on Actions. Now you will see a new menu command, NewApplication,
on the menu (see Figure A.9).
Figure A.9 Menu Items after Adding Custom Menu Commands
Let??™s look at the Registry fi le closely to understand the codes we used (see Table A.3).
Customizing the MOC Client ??? Appendix A 417
Table A.3 Custom Menu Commands Registry File
Code Description
Windows Registry Editor Version 5.00 Indicates the Registry version
[HKEY_LOCAL_MACHINE\Software\ Series of hexadecimal characters
Microsoft\Communicator\Session- that denote the application??™s
Manager\Apps\{1F9F07C6- globally unique identifi er (GUID).
7E0B-462B-AAD7-98C6DBEA8F69}] Windows uses the GUID to identify
applications or its components.
???Name???=???NewApplication??? Name of the application
???HelpMessage???=???This is to add a Additional help message
custom menu on Microsoft Offi ce
Communicator 2007???
???ApplicationType???=???REG_DWORD: 0 denotes that it??™s an executable
00000000??? application.
Pages:
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420