RE: Develop Microsoft Office solutions with Visual Studio .NET

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello IamZhao,

For general Office Solution Development:
http://msdn2.microsoft.com/en-us/library/ms400535.aspx

For object modals
They should be located in the Office installation dir.
C:\Program Files\Microsoft Office\Office12\1033\*.CHM

OWC Object Modal
http://support.microsoft.com/kb/319793

Office 2003 Smart Document Software Development Kit (SDK)
http://www.microsoft.com/downloads/details.aspx?familyid=24a557f7-eb06-4a2c-
8f6c-2767b174126f&displaylang=en

Smart Tags Developer Portal
http://msdn2.microsoft.com/en-us/office/aa905532.aspx

For VSTO:
http://msdn2.microsoft.com/en-us/library/d2tx7z6d(VS.80).aspx

Because the development of Office solution is usually related to COM,
Automation, COM and .NET interoperability, I recommend the following book
for your reference.

COM and COM Automation:
Book 'Inside COM' by Dale Rogerson
Book 'Essential COM' by Don Box

COM and .NET Interoperability:
Book '.NET and COM: The Complete Interoperability Guide' by Adam Nathan
Book 'Professional Visual Basic Interoperability - COM and VB6 to .NET) by
Billy Hollis

Last but not least, newsgroup is also a good resource you can leverage. We
will be more than happy to be of assistance when you encounter any problem
on how to develop Microsoft Office solutions.

Sincerely,
Jialiang Ge (jialge@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support

==================================================
For MSDN subscribers whose posts are left unanswered, please check this
document: http://blogs.msdn.com/msdnts/pages/postingAlias.aspx

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications. If you are using Outlook Express/Windows Mail, please make sure
you clear the check box "Tools/Options/Read: Get 300 headers at a time" to
see your reply promptly.

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.

.

Relevant Pages

  • RE: Develop Microsoft Office solutions with Visual Studio .NET
    ... Because the development of Office solution is usually related to COM, ... Microsoft Online Community Support ... For MSDN subscribers whose posts are left unanswered, ...
    (microsoft.public.office.developer.automation)
  • RE: Office Assembly shared usage
    ... deploy an Office solution based on Office PIA ... solution only wants to support Office XP and above. ... to use the Office 2003 Update: Redistributable Primary Interop Assemblies ...
    (microsoft.public.vsnet.general)
  • RE: Office Assembly shared usage
    ... deploy an Office solution based on Office PIA ... Develop the Office solution with late binding without PIA. ... solution only wants to support Office XP and above. ...
    (microsoft.public.vsnet.general)