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

Release information - 1.7.3

Mar 18, 2015 at 8:18 PM

I just noticed that there was a new release 1.7.3. What has changed since 1.7.2? It would be very valuable if you can add some kind of release information on the website so one can easily see if one needs to upgrade.

Thanks for the great job.
Mar 20, 2015 at 12:53 PM
Edited Mar 20, 2015 at 12:56 PM
hey men,

good point!
for the future: i want create a release notes posting here and spend a link for every new release.

About NO 1.7.3
  • Improve/Fix Assembly load in NetOffice Core.
    (old releases may cause issues if you have multiple -unshimmed- office addins in one application that using different NO versions)
  • fix DAOApi.dll
    (DAOApi is based on 2 components DAO360.dll and ACEDAO.dll, the old jet-engine and the new ace enginge.
    In NO 1.7.2 - DAOApi cant handle ACEDAO.dll correctly because the ACEDAO library id was missing in DAOApi.dll)
  • add MSFormsApi.dll
    (The MsForms Api contains the embeded default VBA ui controls, like TextBox, Button, etc.
    Now you can use/access these ones also in NetOffice with all support)
  • improve/fix NetOffice.Outlook security
    (Doesnt works as expected in NO 1.7.2 if a firewall dialog or something like that occurs)
  • improve NetOffice Tools layer:
CustomUI attribute doesnt need a hard coded rootnamespace like:
  CustomUI("RibbonUI.xml", true) // true means detect and use root namespace automaticly
  • add Utils to NO Tools layer:
ExcelApi.Tools.CommonUtils (inherites from OfficeApi.Tools.CommonUtils)
OutlookApi.Tools.CommonUtils (inherites from OfficeApi.Tools.CommonUtils)
WordApi.Tools.CommonUtils (inherites from OfficeApi.Tools.CommonUtils)
PowerPointApi.Tools.CommonUtils (inherites from OfficeApi.Tools.CommonUtils)
AccessPointApi.Tools.CommonUtils (inherites from OfficeApi.Tools.CommonUtils)

(The COMAddin base class contains an own instance of CommonUtils. this.Utils)

The various utils features is depending on the application.
Common(inherites from Office utils) is:
   bool ApplicationIs2007OrHigher {get;}
   bool AdminPermissions {get;}
   bool IsAutomation {get;}
   DialogUtils {get;}     // show dialogs 
   ResourceUtils {get;} // access embeded resources
   TrayUtils {get;}        // use a tray icon for your addin(NO is handle the dispose)
   ImageUtils {get;}     // conversion to IPictureDisp incl. mask
   ColorUtils {get;}      // conversion from Drawing.Color to double vice versa
   SystemInformations {get;} // various system informations
Excel, Word, Outlook, Word contains also FileUtils to build a document path with current extension very easy.
Outlook and PowerPoint contains also ApplicationUtils to handle some well known bugs/disadvantages.

Why the dialog utils ???
DialogUtils allows you to show a message, pre-defined or own dialogs.
Sounds stupid of course... but you can suspend this if an application is currently hidden or in automation(may testing)

from DialogUtils.cs:
        // Events
        public DialogShowEventHandler DialogShow;

        public DialogShownEventHandler DialogShown;

        // Properties
        public bool SuppressOnAutomation { get; set; }

        public bool SuppressOnHide { get; set; }

        public bool SupressGeneraly { get; set; }
Addin scenario: example to show a message box.
   // last argument is the default result if the dialog is not shown
   var result = this.Utils.Dialog.ShowMessageBox("hello world", MessageBoxIcon.Information, DialogResult.None);
   if(result == DialogResult.None)
         Log("MessageBox suspended");
  • fix NetOffice Tools for MS Project
    (NO 1.7.2 use regkey "MSProject" instead of "MS Project"
not sure thats all but i think so for the moment

Mar 20, 2015 at 1:50 PM
Thanks! An additional benefit of have a clear visible release version log on the website with changes is that the project will attract more users since new users see it is being actively maintained.
Mar 20, 2015 at 2:00 PM
Can you expand on the below (preferably in a not too technical terms)?

"(old releases may cause issues if you have multiple -unshimmed- office addins in one application that using different NO versions)"

I have an Outlook add-in that is deployed based on 1.7.2. In what cases will this affect my users?
Mar 20, 2015 at 2:49 PM
I think I get it now. NO = NetOffice. Stupid me :)
Mar 20, 2015 at 5:24 PM
exactly, NO is NetOffice :)

Its not easy to explain in detail but simple and the point...long text may boring developers.

For your outlook addin users, its a bit more safety to use NO 1.7.3 because no possible side effects with other NO-based addins that use a different NO version.
For you: Improved NetOffice.OutlookSecurity and ApplicationsUtils shows you the application is currenty visible or hidden(Outlook.Application miss a Visible property)

Mar 24, 2015 at 11:30 AM
Hello Sebastian,

I do not want to annoy, when will you update NuGet?
Thank you for your very good and hard work.

Mar 24, 2015 at 12:50 PM
hey haro,

i do not own the nuget packages on github.
i give a release notification to the owner(Caio Proiete) but no answer yet.

Mar 24, 2015 at 11:50 PM
Hey Sebastian,
thank you, I try to be patient ;)

Oct 14, 2015 at 5:00 AM
Edited Oct 14, 2015 at 5:13 AM

I've just released the NuGet packages for NetOffice 1.7.3.

They are available directly from

And also available for download in my GitHub repository (if you run your private NuGet feed):

Sorry for the delay. Getting ready to release 1.7.4 shortly.

Caio Proiete