This project has moved and is read-only. For the latest updates, please go here.

New versions of NetOffice

Oct 9, 2016 at 10:51 AM
Thanks Sebastian for your great software.

There are some nuances that complicate the transition to NetOffice, because after the transition it is necessary for some time to fiind out why the code does not work so as it worked before.

For example, by using ExcelApi it is necessary to adapt (do anew) Range.Resize[row, column] on Range.Resize(row, column). The same regards Offset.
Instead .Names.Item(rangeName) it should be .Names[rangeName, null, null].
Work with optional arguments differs.

In issue Worksheet.Range is not an indexer (C#) ( you write that

"So Excel.Worksheet need a -real-simple Range property in NetOffice.
(The indexer comes from the Excel.Range class in your scenario)
This is easy to fix in a minute :)"

In this connection, I have a question, do you plan to release new versions of NetOffice and where can it be retrieved?

Best regars,
Oct 9, 2016 at 6:32 PM
I know...holy shit i know.

NetOffice is written in C# and this comes with a drawback. I've been tried VB a lot of times with much more problems.

In fact: It is impossible to reproduce the Primary Interop Assemblies as 1:1. (Standard Interop Assemblies are no match for NetOffice of course)

All .Net languages doesnt allows what the COM standard doing here.
The primary interop assemblies bypass any compiler rules and can do the magic

Yes, imitate the PIA's better in Excel as first is part of the todo list and fixed in the current source state.

I have a new release right now for 1 year but Codeplex drop the support to my lovely Subversion(SVN), and i have no experience with Git at all, and i have no time to learn all about git to continue the contribution.

Oct 10, 2016 at 9:46 AM
Thanks Sebastian,

can you somehow make the sources of the latest version available without source control?

Best regars,
Oct 11, 2016 at 5:47 AM
There is one package in the download section now: [Source] Current Source State

Oct 14, 2016 at 11:34 PM
Hi Sebastian,

have you tried to use Subversion with netoffice/NetOffice repostory on GitHub?
GitHub repositories can be access with SVN clients.
Oct 15, 2016 at 4:13 PM
FYI, Jozef Izso was kind enough to submit a pull-request to the Github repository with the latest code submitted by Sebastian, which you can get by cloning the repository:

Caio Proiete
Oct 16, 2016 at 5:37 PM
I've update the repository with automated build on AppVeyor and deployment of NuGet packages to MyGet.

This is the current release process:
  1. Update code at
  2. Automated build on AppVeyor will compiled both Debug and Release configurations
  3. NuGet packages are created for NetOffice libraries
  4. Packages are published to feed
Developer experience for developing NetOffice based projects:
  1. Use pre-release feed to get latest NetOffice packages:
  2. Write code
  3. Configure Visual Studio to use Symbols Server at
  4. Debug your project and step into NetOffice source code