netoffice Wiki Rss Feed

Updated Wiki: DeveloperToolbox_Russian

artnib — Thu, 21 Feb 2013 03:02:31 GMT

Developer Toolbox

Developer Toolbox - это программа для разработчиков .NET, создающих решения на базе Microsoft Office. Программа содержит следующие средства:

Office Compatibility	Проверка совместимости ваших сборок с разными версиями MS Office
Application Observer	Обозреватель запущенных приложений MS Office
Registry Editor	Клон "Редактора реестра" для разделов приложений MS Office
Addin Guard	Параметры загрузки надстроек COM
Outlook Security	Скрытие диалога безопасности Outlook
Office UI	Поиск и удаление нерабочих элементов интерфейса приложений Office
Project Wizard	Мастер создания проекта Visual Studio Express

Updated Wiki: RegistryEditor_Russian

artnib — Thu, 21 Feb 2013 03:01:19 GMT

Registry editor

Это средство внешне и технически является копией редактора реестра Windows, но работает лишь с разделами приложений Office. NetOffice Registry Editor позволяет быстрее и проще проверить или изменить параметры приложения Office.

Все диалоги и функции работают так же, как и в редакторе реестра Windows. Если у вас нет прав администратора, NetOffice Registry editor не даёт возможности изменять разделы или параметры в корневом разделе HKEYLOCALMACHINE.

Updated Wiki: DeveloperToolbox_Russian

artnib — Thu, 21 Feb 2013 02:47:28 GMT

Developer Toolbox

Office Compatibility	Проверка совместимости ваших сборок с разными версиями MS Office
Application Observer	Обозреватель запущенных приложений MS Office
Registry Editor	Клон "Редактора реестра" для разделов приложений MS Office
Addin Guard	Параметры загрузки надстроек COM
Outlook Security	Скрытие диалога безопасности Outlook
Office UI	Поиск и удаление нерабочих элементов интерфейса приложений Office
Project Wizard	Мастер создания проекта Visual Studio Express

Updated Wiki: Home_Russian

artnib — Thu, 21 Feb 2013 02:44:52 GMT

NetOffice предлагает решения на базе .NETдля разработчиков Office english | deutsch

Сборки .NET для доступа к приложениями MS Office:

■ Office, Excel, Word, Outlook, PowerPoint, Access, Project, Visio

Особенности

Интеграция с Office без ограничений по версиям
Включены все возможности Office 2000, 2002, 2003, 2007, 2010, 2013
Поддержка разработок, не зависящих от версии приложения
Синтаксическая и семантическая идентичность сборкам взаимодействия от Microsoft (PIA)
Не требуется обучение, если вы знаете объектную модель Office, применяйте существующий код с использованием PIA
Более читаемый код меньшего объёма с автоматическим управлением заместителями объектов COM
Поддержка .NET 2.0 и более поздних версий
Лёгкая разработка надстроек
Простое развёртывание
Отсутствуют внешние зависимости, не требуются сборки взаимодействия и VSTO
Шаблоны и мастера создания проектов Visual Studio

Документация и ЧаВО

Незаменимый помощник

С какими версиями Office совместимо ваше решение?
Всегда ли загружается ваша надстройка?

Вам поможет NetOffice Developer Toolbox.

Updated Wiki: DeveloperToolbox_Russian

artnib — Tue, 19 Feb 2013 16:14:02 GMT

Developer Toolbox

Developer Toolbox - это программа для разработчиков .NET, создающих на базе Microsoft Office. Программа содержит следующие средства:

Office Compatibility	Проверка совместимости ваших сборок с разными версиями MS Office
Application Observer	Обозреватель запущенных приложений MS Office
Registry Editor	Клон "Редактора реестра" для разделов приложений MS Office
Addin Guard	Параметры загрузки надстроек COM
Outlook Security	Скрытие диалога безопасности Outlook
Office UI	Поиск и удаление нерабочих элементов интерфейса приложений Office
Project Wizard	Мастер создания проекта Visual Studio Express

Updated Wiki: ProjectWizard_RU

artnib — Tue, 19 Feb 2013 15:55:52 GMT

Мастер создания проекта

NetOffice предлагает мастер создания проектов в виде расширения Visual Studio. Visual Studio Express не поддерживает расширения. Пользователи VS Express могут воспользоваться «Мастером создания проекта», входящего в состав отдельного приложения «Developer Toolbox». Программа генерирует решение в формате VS Express.

Нажмите на кнопку "New Project" и выберите язык программирования и версию Visual Studio Expess.

После завершения работы "Мастер создания проекта" откроет папку решения в Проводнике. Это решение можно открыть в Visual Studio Express.

Updated Wiki: DeveloperToolbox_Russian

artnib — Tue, 19 Feb 2013 15:55:18 GMT

Developer Toolbox

Developer Toolbox - это программа для разработчиков .NET, создающих на базе Microsoft Office.

Updated Wiki: ProjectWizard_RU

artnib — Tue, 19 Feb 2013 15:43:10 GMT

Мастер создания проекта

Updated Wiki: Home_Russian

artnib — Tue, 19 Feb 2013 15:11:52 GMT

■ Office, Excel, Word, Outlook, PowerPoint, Access, Project, Visio

Особенности

Интеграция с Office без ограничений по версиям
Включены все возможности Office 2000, 2002, 2003, 2007, 2010, 2013
Поддержка разработок, не зависящих от версии приложения
Синтаксическая и семантическая идентичность сборкам взаимодействия от Microsoft (PIA)
Не требуется обучение, если вы знаете объектную модель Office, применяйте существующий код с использованием PIA
Более читаемый код меньшего объёма с автоматическим управлением заместителями объектов COM
Поддержка .NET 2.0 и более поздних версий
Лёгкая разработка надстроек
Простое развёртывание
Отсутствуют внешние зависимости, не требуются сборки взаимодействия и VSTO
Шаблоны и мастера создания проектов Visual Studio

Документация и ЧаВО

Незаменимый помощник

С какими версиями Office совместимо ваше решение?
Всегда ли загружается ваша надстройка?

Вам поможет NetOffice Developer Toolbox.

Updated Wiki: Home_Russian

artnib — Sat, 29 Dec 2012 13:21:02 GMT

■ Office, Excel, Word, Outlook, PowerPoint, Access, Project, Visio

Особенности

Интеграция с Office без ограничений по версиям
Включены все возможности Office 2000, 2002, 2003, 2007, 2010, 2013
Поддержка разработок, не зависящих от версии приложения
Синтаксическая и семантическая идентичность сборкам взаимодействия от Microsoft (PIA)
Не требуется обучение, если вы знаете объектную модель Office, применяйте существующий код с использованием PIA
Более читаемый код меньшего объёма с автоматическим управлением заместителями объектов COM
Поддержка .NET 2.0 и более поздних версий
Лёгкая разработка надстроек
Простое развёртывание
Отсутствуют внешние зависимости, не требуются сборки взаимодействия и VSTO
Шаблоны и мастера создания проектов Visual Studio

Документация и ЧаВО

Updated Wiki: Documentation_Russian

artnib — Sat, 29 Dec 2012 13:17:44 GMT

Почему NetOffice? english | deutsch

Обычно для доступа к Microsoft Office в .NET используются основные сборки взаимодействия (PIA) и VSTO. Оба метода имеют недостатки.

Привязка к одной или определённым версиям Office
При переносе или установке на другой компьютер могут возникнуть проблемы
Не предоставляются защитные механизмы управления заместителями объектов COM

NetOffice устраняет эти недостатки и является средством, синтаксически и семантически идентичным сборкам взаимодействия.

Как работает NetOffice?

NetOffice использует лишь "позднее связывание" COM Interop, но с удобством и простотой "раннего связывания". Изящная архитектура и эффективный дизайн лишь незначительно замедляют работу по сравнению с "ранним связыванием" (не более, чем на 10%). События в NetOffice реализованы посредством техники, которую автор называет "динамическое раннее связывание".

NetOffice содержит 16 сборок. Какие из них нужны для конкретного приложения Office?

Все приложения Office используют типы, которые определены в библиотеках компонентов/типов. Библиотеки типов предсталены отдельной сборкой. Каждая сборка зависит от сборки NetOffice.dll.

Таблица развёртывания

Приложение Office	Зависимости
ExcelApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll
WordApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll
OutlookApi.dll
	OfficeApi.dll
	NetOffice.dll
PowerPointApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll
AccessApi.dll
	OfficeApi.dll
	DAOApi.dll
	VBIDEApi.dll
	ADODBApi.dll
	OWC10Api.dll
	MSDATASRCApi.dll
	MSComctlLibApi.dll
	NetOffice.dll
MSProjectApi.dll
	OfficeApi.dll
	MSHTMLApi.dll
	NetOffice.dll
VisioApi.dll
	NetOffice.dll

Что нужно для распространения программы на базе NetOffice?

Только скопировать сборки на целевой комьпютер. Регистрация требуется лишь для дополнений COM. Управляемые дополнения COM обычно регистрируются посредством утилиты RegAsm.exe или Windows Installer.

Зависят ли дополнения COM от версии Office?

Нет, и в этом достоинство NetOffice. Доступны примеры для дополнений всех приложений Office. Для поддержки 32- и 64-разрядных приложений понадобятся 2 версии дополнений соответственно.

Updated Wiki: Documentation_Russian

artnib — Sat, 29 Dec 2012 13:12:21 GMT

Привязка к одной или определённым версиям Office
При переносе или установке на другой компьютер могут возникнуть проблемы
Не предоставляются защитные механизмы управления заместителями объектов COM

Как работает NetOffice?

NetOffice содержит 16 сборок. Какие из них нужны для конкретного приложения Office?

Приложение Office	Зависимости
ExcelApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll
WordApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll
OutlookApi.dll
	OfficeApi.dll
	NetOffice.dll
PowerPointApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll
AccessApi.dll
	OfficeApi.dll
	DAOApi.dll
	VBIDEApi.dll
	ADODBApi.dll
	OWC10Api.dll
	MSDATASRCApi.dll
	MSComctlLibApi.dll
	NetOffice.dll
MSProjectApi.dll
	OfficeApi.dll
	MSHTMLApi.dll
	NetOffice.dll
VisioApi.dll
	NetOffice.dll

Что нужно для распространения программы на базе NetOffice?

Зависят ли дополнения COM от версии Office?

Updated Wiki: Documentation_Russian

artnib — Sat, 29 Dec 2012 13:07:49 GMT

Привязка к одной или определённым версиям Office
При переносе или установке на другой компьютер могут возникнуть проблемы
Не предоставляются защитные механизмы управления заместителями объектов COM

Как работает NetOffice?

NetOffice содержит 16 сборок. Какие из них нужны для конкретного приложения Office?

Приложение Office	Зависимости
ExcelApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll
WordApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll
OutlookApi.dll
	OfficeApi.dll
	NetOffice.dll
PowerPointApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll
AccessApi.dll
	OfficeApi.dll
	DAOApi.dll
	VBIDEApi.dll
	ADODBApi.dll
	OWC10Api.dll
	MSDATASRCApi.dll
	MSComctlLibApi.dll
	NetOffice.dll
MSProjectApi.dll
	OfficeApi.dll
	MSHTMLApi.dll
	NetOffice.dll
VisioApi.dll
	NetOffice.dll

Что нужно для распространения программы на базе NetOffice?

Зависят ли дополнения COM от версии Office?

Updated Wiki: Documentation

SebastianDotNet — Fri, 28 Dec 2012 20:56:35 GMT

Why NetOffice? english | deutsch| русский

The usual methods for accessing Microsoft Office. NET are the Primary Interop Assemblies and VSTO. Both access methods involve various disadvantages.

They are limited to a version, i.e. they only work with one or certain versions of Office
They cause problems while transferring or installation on other systems
They offer no protection mechanism in the management of COM proxies

NetOffice eliminates these disadvantages and remains a 1:1 wrapper that is syntactically and semantically identical to the interop assemblies.

How does NetOffice work?

NetOffice used to access only LateBinding Calls via COM Interop, but without sacrificing the convenience and simplicity of EarlyBind calls. The slim architecture and efficient design makes this only slightly slower than so-called EarlyBind calls in .NET (max. 10%). Events in NetOffice are implemented with a technique the author calls Dynamic EarlyBinding. Learn more about this in the technical documentation.

NetOffice contains 16 assemblies. Why and which assemblies do I need for my desired Office application?

All Office applications use types which are defined in other components/type libraries. These dependent type libraries are therefore given as an independent assembly. Each assembly also requires the NetOffice.dll assembly. An overview which Office application integrates which additional assemblies can be found here.

Deployment Table:

Office applications	Dependencies
ExcelApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll

WordApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll

OutlookApi.dll
	OfficeApi.dll
	NetOffice.dll

PowerPointApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll

AccessApi.dll
	OfficeApi.dll
	DAOApi.dll
	VBIDEApi.dll
	ADODBApi.dll
	OWC10Api.dll
	MSDATASRCApi.dll
	MSComctlLibApi.dll
	NetOffice.dll

MSProjectApi.dll
	OfficeApi.dll
	MSHTMLApi.dll
	NetOffice.dll

VisioApi.dll
	NetOffice.dll

What do I have to do to deliver my application with NetOffice?

Nothing except copying the needed assemblies to the target system. You don't need a registration or something like that with the exception of COMAddIns. Managed COMAddins generally have to be registered via the .Net Utility RegAsm.exe or the Windows Installer do that or you.

Do COMAddins also work version independent?

Yes, of course. This is a particular strength of NetOffice. See the code examples for example project for all Office applications but you have to create 2 Addins for 32/64 Bit support.

Is NetOffice ready for multiple platforms(32/64 Bit)?

You can use the NetOffice AnyCPU assemblies in all scenarios. his is true regardless wether you develop for a 32Bit Office application or a 64Bit Office application, even independent on which platform these are installed. If your assembly is a standalone application (.exe) or is being loaded by one, you can compile your assembly as AnyCPU without worries.

If your assembly is a COMAddin that is being loaded by a 32Bit Office application, you can still compile it as AnyCPU. If you develop a COMAddin that is being used by a 64Bit Office application, you have to compile your assembly as x64. If you wart to support 32Bit and 64Bit Office applications, you may need to provide a second x64-compiled COMAddin. This behaviour is the same in all scenarios(interop,vsto or netoffice). A 64Bit application can only load 64Bit Dll's.If you use a 64Bit Office for testing on your development system and you want to register your COMAddin while compiling (Register for COM Interop), you need to keep in mind that some older versions of Visual Studio call the 32Bit registration in that case. In this case, you get the following error:

"File <path to assembly> is not a valid assembly".
You can read a workarround by Microsoft here:
http://support.microsoft.com/kb/956933

How do I migrate my solution to NetOffice?

Interop Solutions: Change the references and the using(imports in vb) statements. Occasionally, you need to make some adjustments to event triggers. You have to replace all Marshall.ReleaseComObject calls with Dispose. you can also delete the most ReleaseComObject calls because NetOffice manages COM proxies for you. Read more about in the technical documentation: Understanding COM Proxy Management

VBA Solutions: Developers there want changing a VBA solution to VB.NET and NetOffice has to know that VB.NET is syntactical similar to VBA but has also some different concepts. If you have good VB.NET skills then you have no problems to migrate your solution to NetOffice.

COM proxy management

If you call Office applications (COM servers) .NET returns instead of real objects so-called COM proxies. In order to signal the COM server that you no longer need this, you have to free it with a special method. This applies to VSTO as well as to interop assemblies.

Due to this fact, you must not use no objects implicitly or use Enumerator directly because it then can no longer be released. In NetOffice each object provides the method Dispose() for when you do not need it anymore. All classes in NetOffice implement the IDisposable interface and also provide the Dispose() method. However, you do not have to call Dispose() for every used object and you may also use objects implicitly and Enumerator directly without having to worry about releasing ti afterwards. NetOffice generated proxies stored in a separate table and frees when you request it or a parent object is being released. More on that in the technical documentation and Tutorial01.

Unknown and Variant Types

Many office applications include Properties, return values or parameter whose type is not known at design time and which can change at run time, depending on context. There is a difference between unknown COM proxies and the variant data type which has its roots in the Visual Basic for Applications (VBA).

Unknown COM proxies in NetOffice have the type COMObject. Each class in NetOffice also inherits from this type. The declaration of unkown proxies is Object since NetOffice 1.5.1 as special service for VB developers to use the integrated late binding feature. You can also convert an anonymous COM proxy at run-time into the actual type without problems.

The variant data type is used in VBA for any type to accept both a COM proxy and a scalar data type such as bool or int. In NetOffice that type is replaced by the type object. If a Variant Property is a COM proxy at run time you get an object of the corresponding NetOffice wrapper class, otherwise the the corresponding scalar data type. More on that in the technical documentation and Tutorial06.

If NetOffice supports all versions of Office, how do I know which Office version offers which functionality?

All classes, properties, methods, enums, etc. come with XML Documentation and have a special attribute that identifies which office version(s) this entity support. You get this information displayed during development also through IntelliSense. Moreover, it is possible to examine an assembly (created with NetOffice) with NetOffice.DeveloperToolbox which Office versions are used practically. Use this opportunity before shipping your assembly to make sure that your program works with the Office versions that you (or your customers) have specified.

Screenshot: IntelliSense support in C # for version information of a property.

Updated Wiki: Documentation

SebastianDotNet — Fri, 28 Dec 2012 20:54:41 GMT

They are limited to a version, i.e. they only work with one or certain versions of Office
They cause problems while transferring or installation on other systems
They offer no protection mechanism in the management of COM proxies

NetOffice eliminates these disadvantages and remains a 1:1 wrapper that is syntactically and semantically identical to the interop assemblies.

Office applications	Dependencies
ExcelApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll

WordApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll

OutlookApi.dll
	OfficeApi.dll
	NetOffice.dll

PowerPointApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll

AccessApi.dll
	OfficeApi.dll
	DAOApi.dll
	VBIDEApi.dll
	ADODBApi.dll
	OWC10Api.dll
	MSDATASRCApi.dll
	MSComctlLibApi.dll
	NetOffice.dll

MSProjectApi.dll
	OfficeApi.dll
	MSHTMLApi.dll
	NetOffice.dll

VisioApi.dll
	NetOffice.dll

"File <path to assembly> is not a valid assembly".
You can read a workarround by Microsoft here:
http://support.microsoft.com/kb/956933

Unknown and Variant Types

Updated Wiki: Home

SebastianDotNet — Fri, 28 Dec 2012 20:39:29 GMT

NetOffice offers solutions for Office Developers in .NET Select a Language:
english | deutsch | russian

.NET Wrapper Assemblies for accessing the following MS Office applications:

Office, Excel, Word, Outlook, PowerPoint, Access, Project, Visio

Features

Office integration without version limitations
All features of the Office versions 2000, 2002, 2003, 2007, 2010, 2013 are included
Active support in version independent development (please scroll down)
Syntactically and semantically identical to the Microsoft Interop Assemblies
No training if you already know the Office object model, use your existing PIA code
Reduced and more readable code with automatic management of COM proxies
Usable with .NET version 2.0 or higher
Easy Addin Development
No deployment hurdles, no registration
No dependencies, no interop assemblies, no need for VSTO
Visual Studio Project Templates and Wizards available Photo Gallery

Visual Basic and C# Example Code Online

1	Tutorials currently under construction for Release 1.5
2	Excel
3	Word
4	Outlook
5	PowerPoint
6	Access
7	Misc

An indispensable helper

How compatible is your solution with all the office versions ?
You are not sure if your Addin is already loaded?

The NetOffice Developer Toolbox helps you.

Active support in version independent developement

XML source documentation for information which version are offering the particular entity
check at runtime your specified entity is available in current version (Tutorial 08 C# VB)
check your solution with the Toolbox which Office version are compatible with your code

Documentation and FAQ

1	Why NetOffice?
2	How does NetOffice work?
3	Which NetOffice assemblies do I need for my desired Office application?
4	What do I have to do to deliver my application with NetOffice?
5	Do COMAddins also work version independent?
6	NetOffice is ready for multiple platforms(32/64 Bit)?
7	How do I migrate my solution to NetOffice?
8	COM proxy management
9	Unknown and Variant Types
10	How do I know which Office version offers which functionality?

Technical Documentation and Ressources

1	Technical Documentation (Reference, Performance) under construction
2	Technical FAQ
3	NetOffice.DeveloperToolbox
4	Visual Studio Project Wizard

Roadmap

1	NetOffice.DeveloperToolbox Done!
2	Extended Linq Support
3	Support Microsoft Exchange, Microsoft Visio, Microsoft Project completly
4	Enumerators for collections without native enumerator support Done!
5	Additional overloads for methods with optional parameters Done!
6	FxCop approved Sourcecode
7	Visual UI designer

Questions or Comments?

1	E-Mail
2	Disscusion Board
3	Sebastians Blog about NetOffice

Stay informed

Follow NetOffice on Twitter for actual infos about updates and issues

Updated Wiki: Home

SebastianDotNet — Fri, 28 Dec 2012 20:39:00 GMT

NetOffice offers solutions for Office Developers in .NET Select a Language:
english | deutsch | russian

.NET Wrapper Assemblies for accessing the following MS Office applications:

Office, Excel, Word, Outlook, PowerPoint, Access, Project, Visio

Features

Office integration without version limitations
All features of the Office versions 2000, 2002, 2003, 2007, 2010, 2013 are included
Active support in version independent development (please scroll down)
Syntactically and semantically identical to the Microsoft Interop Assemblies
No training if you already know the Office object model, use your existing PIA code
Reduced and more readable code with automatic management of COM proxies
Usable with .NET version 2.0 or higher
Easy Addin Development
No deployment hurdles, no registration
No dependencies, no interop assemblies, no need for VSTO
Visual Studio Project Templates and Wizards available Photo Gallery

Visual Basic and C# Example Code Online

1	Tutorials currently under construction for Release 1.5
2	Excel
3	Word
4	Outlook
5	PowerPoint
6	Access
7	Misc

An indispensable helper

How compatible is your solution with all the office versions ?
You are not sure if your Addin is already loaded?

The NetOffice Developer Toolbox helps you.

Active support in version independent developement

XML source documentation for information which version are offering the particular entity
check at runtime your specified entity is available in current version (Tutorial 08 C# VB)
check your solution with the Toolbox which Office version are compatible with your code

Documentation and FAQ

1	Why NetOffice?
2	How does NetOffice work?
3	Which NetOffice assemblies do I need for my desired Office application?
4	What do I have to do to deliver my application with NetOffice?
5	Do COMAddins also work version independent?
6	NetOffice is ready for multiple platforms(32/64 Bit)?
7	How do I migrate my solution to NetOffice?
8	COM proxy management
9	Unknown and Variant Types
10	How do I know which Office version offers which functionality?

Technical Documentation and Ressources

1	Technical Documentation (Reference, Performance) under construction
2	Technical FAQ
3	NetOffice.DeveloperToolbox
4	Visual Studio Project Wizard

Roadmap

1	NetOffice.DeveloperToolbox Done!
2	Extended Linq Support
3	Support Microsoft Exchange, Microsoft Visio, Microsoft Project completly
4	Enumerators for collections without native enumerator support Done!
5	Additional overloads for methods with optional parameters Done!
6	FxCop approved Sourcecode
7	Visual UI designer

Questions or Comments?

1	E-Mail
2	Disscusion Board
3	Sebastians Blog about NetOffice

Stay informed

Follow NetOffice on Twitter for actual infos about updates and issues

Updated Wiki: Home

SebastianDotNet — Fri, 28 Dec 2012 20:38:27 GMT

NetOffice offers solutions for Office Developers in .NET Select a Language:
english | deutsch | russian

.NET Wrapper Assemblies for accessing the following MS Office applications:

Office, Excel, Word, Outlook, PowerPoint, Access, Project, Visio

Features

Office integration without version limitations
All features of the Office versions 2000, 2002, 2003, 2007, 2010, 2013 are included
Active support in version independent development (please scroll down)
Syntactically and semantically identical to the Microsoft Interop Assemblies
No training if you already know the Office object model, use your existing PIA code
Reduced and more readable code with automatic management of COM proxies
Usable with .NET version 2.0 or higher
Easy Addin Development
No deployment hurdles, no registration
No dependencies, no interop assemblies, no need for VSTO
Visual Studio Project Templates and Wizards available Photo Gallery

Visual Basic and C# Example Code Online

1	Tutorials currently under construction for Release 1.5
2	Excel
3	Word
4	Outlook
5	PowerPoint
6	Access
7	Misc

An indispensable helper

How compatible is your solution with all the office versions ?
You are not sure if your Addin is already loaded?

The NetOffice Developer Toolbox helps you.

Active support in version independent developement

XML source documentation for information which version are offering the particular entity
check at runtime your specified entity is available in current version (Tutorial 08 C# VB)
check your solution with the Toolbox which Office version are compatible with your code

Documentation and FAQ

1	Why NetOffice?
2	How does NetOffice work?
3	Which NetOffice assemblies do I need for my desired Office application?
4	What do I have to do to deliver my application with NetOffice?
5	Do COMAddins also work version independent?
6	NetOffice is ready for multiple platforms(32/64 Bit)?
7	How do I migrate my solution to NetOffice?
8	COM proxy management
9	Unknown and Variant Types
10	How do I know which Office version offers which functionality?

Technical Documentation and Ressources

1	Technical Documentation (Reference, Performance) under construction
2	Technical FAQ
3	NetOffice.DeveloperToolbox
4	Visual Studio Project Wizard

Roadmap

1	NetOffice.DeveloperToolbox Done!
2	Extended Linq Support
3	Support Microsoft Exchange, Microsoft Visio, Microsoft Project completly
4	Enumerators for collections without native enumerator support Done!
5	Additional overloads for methods with optional parameters Done!
6	FxCop approved Sourcecode
7	Visual UI designer

Questions or Comments?

1	E-Mail
2	Disscusion Board
3	Sebastians Blog about NetOffice

Stay informed

Follow NetOffice on Twitter for actual infos about updates and issues

Updated Wiki: Home

SebastianDotNet — Fri, 28 Dec 2012 20:37:56 GMT

NetOffice offers solutions for Office Developers in .NET Select a Language:
english | deutsch | russian

.NET Wrapper Assemblies for accessing the following MS Office applications:

Office, Excel, Word, Outlook, PowerPoint, Access, Project, Visio

Features

Office integration without version limitations
All features of the Office versions 2000, 2002, 2003, 2007, 2010, 2013 are included
Active support in version independent development (please scroll down)
Syntactically and semantically identical to the Microsoft Interop Assemblies
No training if you already know the Office object model, use your existing PIA code
Reduced and more readable code with automatic management of COM proxies
Usable with .NET version 2.0 or higher
Easy Addin Development
No deployment hurdles, no registration
No dependencies, no interop assemblies, no need for VSTO
Visual Studio Project Templates and Wizards available Photo Gallery

Visual Basic and C# Example Code Online

1	Tutorials currently under construction for Release 1.5
2	Excel
3	Word
4	Outlook
5	PowerPoint
6	Access
7	Misc

An indispensable helper

How compatible is your solution with all the office versions ?
You are not sure if your Addin is already loaded?

The NetOffice Developer Toolbox helps you.

Active support in version independent developement

XML source documentation for information which version are offering the particular entity
check at runtime your specified entity is available in current version (Tutorial 08 C# VB)
check your solution with the Toolbox which Office version are compatible with your code

Documentation and FAQ

1	Why NetOffice?
2	How does NetOffice work?
3	Which NetOffice assemblies do I need for my desired Office application?
4	What do I have to do to deliver my application with NetOffice?
5	Do COMAddins also work version independent?
6	NetOffice is ready for multiple platforms(32/64 Bit)?
7	How do I migrate my solution to NetOffice?
8	COM proxy management
9	Unknown and Variant Types
10	How do I know which Office version offers which functionality?

Technical Documentation and Ressources

1	Technical Documentation (Reference, Performance) under construction
2	Technical FAQ
3	NetOffice.DeveloperToolbox
4	Visual Studio Project Wizard

Roadmap

1	NetOffice.DeveloperToolbox Done!
2	Extended Linq Support
3	Support Microsoft Exchange, Microsoft Visio, Microsoft Project completly
4	Enumerators for collections without native enumerator support Done!
5	Additional overloads for methods with optional parameters Done!
6	FxCop approved Sourcecode
7	Visual UI designer

Questions or Comments?

1	E-Mail
2	Disscusion Board
3	Sebastians Blog about NetOffice

Stay informed

Follow NetOffice on Twitter for actual infos about updates and issues

Updated Wiki: Documentation

artnib — Fri, 28 Dec 2012 18:20:51 GMT

They are limited to a version, i.e. they only work with one or certain versions of Office
They cause problems while transferring or installation on other systems
They offer no protection mechanism in the management of COM proxies

NetOffice eliminates these disadvantages and remains a 1:1 wrapper that is syntactically and semantically identical to the interop assemblies.

Office applications	Dependencies
ExcelApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll

WordApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll

OutlookApi.dll
	OfficeApi.dll
	NetOffice.dll

PowerPointApi.dll
	OfficeApi.dll
	VBIDEApi.dll
	NetOffice.dll

AccessApi.dll
	OfficeApi.dll
	DAOApi.dll
	VBIDEApi.dll
	ADODBApi.dll
	OWC10Api.dll
	MSDATASRCApi.dll
	MSComctlLibApi.dll
	NetOffice.dll

MSProjectApi.dll
	OfficeApi.dll
	MSHTMLApi.dll
	NetOffice.dll

VisioApi.dll
	NetOffice.dll

"File <path to assembly> is not a valid assembly".
You can read a workarround by Microsoft here:
http://support.microsoft.com/kb/956933

Unknown and Variant Types