Difference between revisions of ".NET"
From Blue-IT.org Wiki
Line 1: | Line 1: | ||
− | == | + | == Programming MS Office in C# - Why? == |
There are a lot of complaints on not developing open source software on csharp ([http://www.fsf.org/news/dont-depend-on-mono Stallman - Don't depend on mono]). | There are a lot of complaints on not developing open source software on csharp ([http://www.fsf.org/news/dont-depend-on-mono Stallman - Don't depend on mono]). | ||
Unfortunately it is obvious, that a lot of software has to be developed for Microsoft Office out there. As a programmer addicted to document management, I can't ignore that. So I was looking around searching to get my work done without beeing bundled with Visual Studio ... | Unfortunately it is obvious, that a lot of software has to be developed for Microsoft Office out there. As a programmer addicted to document management, I can't ignore that. So I was looking around searching to get my work done without beeing bundled with Visual Studio ... | ||
+ | |||
+ | C# sharp has a lot of interesting features and is much more major | ||
== NetOffice == | == NetOffice == |
Revision as of 07:56, 29 October 2013
Programming MS Office in C# - Why?
There are a lot of complaints on not developing open source software on csharp (Stallman - Don't depend on mono).
Unfortunately it is obvious, that a lot of software has to be developed for Microsoft Office out there. As a programmer addicted to document management, I can't ignore that. So I was looking around searching to get my work done without beeing bundled with Visual Studio ...
C# sharp has a lot of interesting features and is much more major
NetOffice
The Manufactor describes the advantages of developing for MS Office with its product in the following way:
- Why NetOffice?
- 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.