starred/outlookcaldavsynchronizer

Fork 0

mirror of https://github.com/aluxnimm/outlookcaldavsynchronizer.git synced 2026-04-25 11:05:56 +03:00

[GH-ISSUE #231] Could not load file or assembly NodaTime #226

New issue

Closed

opened 2026-02-25 20:31:12 +03:00 by kerem · 5 comments

kerem commented

2026-02-25 20:31:12 +03:00

Owner

Originally created by @fluboi on GitHub (May 18, 2018).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/231

Hi,
I've updated to v3.1.1.0 this morning, and now I do have the following error on one of my calendar:

System.IO.FileLoadException: Could not load file or assembly 'NodaTime, Version=2.2.4.0, Culture=neutral, PublicKeyToken=4226afe0d9b296d1' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'NodaTime, Version=2.2.4.0, Culture=neutral, PublicKeyToken=4226afe0d9b296d1'
   at CalDavSynchronizer.Implementation.Events.EventEntityMapper.Map1To2(AppointmentItem source, IEvent target, Boolean isRecurrenceException, ITimeZone startIcalTimeZone, ITimeZone endIcalTimeZone, IEntityMappingLogger logger, IEventSynchronizationContext context)
   at CalDavSynchronizer.Implementation.Events.EventEntityMapper.<Map1To2>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at GenSync.Synchronization.States.UpdateAToB`7.<UpdateEntity>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at GenSync.Synchronization.States.UpdateAToB`7.JobWrapper.<UpdateEntity>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at CalDavSynchronizer.Implementation.CalDavRepository`1.<TryUpdate>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at GenSync.EntityRepositories.BatchEntityRepositoryAdapter`4.<PerformOperations>d__3.MoveNext()

Windows 10
Outlook version 1708

Let me know if you need others infos/logs.

Originally created by @fluboi on GitHub (May 18, 2018). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/231 Hi, I've updated to v3.1.1.0 this morning, and now I do have the following error on one of my calendar: ``` System.IO.FileLoadException: Could not load file or assembly 'NodaTime, Version=2.2.4.0, Culture=neutral, PublicKeyToken=4226afe0d9b296d1' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'NodaTime, Version=2.2.4.0, Culture=neutral, PublicKeyToken=4226afe0d9b296d1' at CalDavSynchronizer.Implementation.Events.EventEntityMapper.Map1To2(AppointmentItem source, IEvent target, Boolean isRecurrenceException, ITimeZone startIcalTimeZone, ITimeZone endIcalTimeZone, IEntityMappingLogger logger, IEventSynchronizationContext context) at CalDavSynchronizer.Implementation.Events.EventEntityMapper.<Map1To2>d__22.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at GenSync.Synchronization.States.UpdateAToB`7.<UpdateEntity>d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at GenSync.Synchronization.States.UpdateAToB`7.JobWrapper.<UpdateEntity>d__11.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at CalDavSynchronizer.Implementation.CalDavRepository`1.<TryUpdate>d__16.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at GenSync.EntityRepositories.BatchEntityRepositoryAdapter`4.<PerformOperations>d__3.MoveNext() ``` Windows 10 Outlook version 1708 Let me know if you need others infos/logs.

kerem closed this issue

2026-02-25 20:31:12 +03:00

kerem commented

2026-02-25 20:31:12 +03:00

Author

Owner

@sfranken-smartwireless commented on GitHub (May 18, 2018):

I have the same issue here.

@sfranken-smartwireless commented on GitHub (May 18, 2018): I have the same issue here.

kerem commented

2026-02-25 20:31:12 +03:00

Author

Owner

@aluxnimm commented on GitHub (May 18, 2018):

Did you try uninstall and install a fresh 3.2.0

@aluxnimm commented on GitHub (May 18, 2018): Did you try uninstall and install a fresh 3.2.0

kerem commented

2026-02-25 20:31:12 +03:00

Author

Owner

@fluboi commented on GitHub (May 18, 2018):

In fact the update I receive this morning was the 3.2.0. But it seems that restarting Outlook is mandatory to have the caldavsynchronizer load the new version.
By simply restating Outlook, the error disappear.
@sfranken-smartwireless does restarting your outlook also solve the problem for you ?

@fluboi commented on GitHub (May 18, 2018): In fact the update I receive this morning was the 3.2.0. But it seems that restarting Outlook is mandatory to have the caldavsynchronizer load the new version. By simply restating Outlook, the error disappear. @sfranken-smartwireless does restarting your outlook also solve the problem for you ?

kerem commented

2026-02-25 20:31:12 +03:00

Author

Owner

@aluxnimm commented on GitHub (May 18, 2018):

Well thats nothing new and the update even shows a message box that a restart is required

@aluxnimm commented on GitHub (May 18, 2018): Well thats nothing new and the update even shows a message box that a restart is required

kerem commented

2026-02-25 20:31:12 +03:00

Author

Owner

@SreeniC commented on GitHub (Jul 23, 2020):

I have the same issue for MS Build, Build failed due to this.
Any solutions.. ?

@SreeniC commented on GitHub (Jul 23, 2020): I have the same issue for MS Build, Build failed due to this. Any solutions.. ?

kerem referenced this issue

2026-03-01 17:40:56 +03:00

[GH-ISSUE #226] Can't parse calendar data: Invalid property #687

kerem referenced this issue

2026-03-14 00:21:35 +03:00

[GH-ISSUE #226] Can't parse calendar data: Invalid property #1122