Awesync 2.0.0.6

Share this

Released on: Wed, 03/31/2010 - 11:58pm

Release notes - AweSync 2.0.0.6

  • Fixed exception "AweSync.MainForm ........", which occured on startup in some rear cases.

Release notes - AweSync 2.0.0.5

  • Fixed "Error happened while Google batch ran";
  • Fixed "System.NullReferenceException at Google.GData.Client.AtomBaseLink.get_AbsoluteUri()";
  • Fixed "Can't process: Value cannot be null.";
  • Fixed "Can't convert time zone from...";
  • Fixed "Can't process: Exception... Domino8.NotesDocumentClass.get_Items()";
  • Fixed "Unexpected error: {0}Systen.NullReferenceException: AweSync.MainForm_Load(object sender , EventArgs e)";
  • Fixed "Upgrade Now box pop up every time a sync occurs" - now this message box will be shown only once;
  • Fixed "Proxy password is lost, and also in auto-detect it doesn't ask for password".

Release notes - AweSync 2.0.0.4

  • "Child domain removed" problem causing not all recurring events to be synchronized is fixed;
  • New known instances of "Notes document cannot be parsed" fixed;
  • Potentially slow or even hanging synchronization fixed;
  • Fixed events created in Google calendar from iPhone not synchronizing into Lotus Notes;
  • Fixed the problem with invitees and locations being removed during synchronization, which also caused conversion of Meetings into Appointments.

Release notes - AweSync 2.0.0.3

We fixed "Value cannot be null", "Object reference not set" and know instances of "Notes Document cannot be parsed" errors. Now the team is also actively working on "Child domain is removed" problem, and the fix should be available in the next 1-2 days.

Release notes - AweSync 2.0.0.1

  • Fixed with time zone errors, please refer for details to the following comment
  • Fixed the bug "Could not load file or assembly Interop.Domino8" on 64-bit operating systems
  • Fixed some instances of the errors "Notes Document cannot be parsed"


What's new in AweSync 2.0.0.0

  • Full support of repeated events with exceptions;
  • Configuration Wizard, see details here;
  • An option is added to change if the Google Calendar name should be stored in Lotus Notes Calendar entry Category field. Might be useful for those, who use categories in Lotus Notes Calendar intensively, and don’t want to mess it up with stuff coming from Google Calendar.
  • Support of synchronization with Google Calendars to which there is no write access (for example, shared by other users).
  • Google Apps Calendar support is added.
  • Support of public and private flags synchronization.
  • Configuration for double-clicking tray icon is added to either show/hide application window, or start/stop synchronization.
  • A log of calendar entries changes is added, where more detailed information about synchronized entries can be found (View Changed Documents link below the Synchronization Log).
  • Support of synchronization between Invitees Required field in Lotus Notes Meeting and Guests field in Google calendar event. Internet addresses of corresponding Lotus Notes user is placed in Google calendar event.
  • Google Calendar event field Where is now synchronized with Lotus Notes Calendar entry Location field, including 2 way. Values of reservation fields from Lotus Notes Calendar entry are added to Google Calendar event Where field in format [Rooms: RoomName] [Resources: ResourceName].
  • Google SMS notifications are now supported. You can enable AweSync option to map Lotus Notes Notify Me options into Google SMS notification, if it’s enabled in your Google Calendar.
  • Now it’s possible to cancel the synchronization at any time.
  • Made some improvements in handling Lotus Notes and Google data, which previously could cause some errors, as well as fixed a lot of other bugs.
  • It is now possible to run few instances of different installations of AweSync which makes it possible to use them in terminal server environment.

Please see AweSync Settings section for more detailed explanations and screenshots.