ALTER DATABASE dbname SET search_path=new_search_path;

Current Status

The Plan

Unit Testing

File is lacking providers

Moving to multi-valued titles

Providing actual functionality

R: Gendarme.Rules.Exceptions.ExceptionShouldBeVisibleRule
T: System.Diagnostics.Contracts.__ContractsRuntime/ContractException

R: Gendarme.Rules.Exceptions.MissingExceptionConstructorsRule
T: System.Diagnostics.Contracts.__ContractsRuntime/ContractException

R: Gendarme.Rules.Serialization.MissingSerializableAttributeOnISerializableTypeRule
T: System.Diagnostics.Contracts.__ContractsRuntime/ContractException

R: Gendarme.Rules.Serialization.MissingSerializationConstructorRule
T: System.Diagnostics.Contracts.__ContractsRuntime/ContractException

Since this is a tool-generated class we cannot do anything about it anyways and should not access or need the missing features.

Status

• Sync Infrastructure: although the two projects are written in Java and C#, they share the basic algorithms and principles of operation. This groundwork is also shared between the addressbook and contacts synchronizers of each project. This is already stable. Some edge cases still require a second synchronization run to converge.
• Addressbook Synchronization: being the easier part of the two, this is mostly finished and working.
• Calendar Synchronization: Arthur is currently implementing the last piece here: reading and writing of recurrences.
• Managing Edit Collisions: If two copies of the same item are edited and then synchronized, there is no easy way to automatically manage the merge. On the Android the server item always wins. For the Outlook plugin we plan on implementing a conflict resolution dialog where the user can pick and choose from the conflicting items.
• Managing Duplicates: When starting to use synchronization tools, users often end up with multiple copies of the same entries (especially in the addressbook) when multiple data sources are added. Currently the only way to work around this problem is to use a third-party duplicate-detector or wipe all but one device clean before synchronizing. A way to handle this could be added similar to a edit conflict resolver.
• Multiple Calendars, multiple IMAP Folders: planned.
• Testing: Currently there are only manual test routines.

using Microsoft.Build.Framework;
using Microsoft.Build.Utilities;

public class ArebisGenTask
: Task
{
[Required]
public ITaskItem[] Templates { get; set; }

[Output]
public ITaskItem[] GeneratedFiles { get; set; }

public override bool Execute()
{
var generatedFileNames = new List<string>();
foreach (var task in this.Templates)
{
string inputFileName = task.ItemSpec;
string outputFileName = Path.ChangeExtension(inputFileName, ".Designer.cs");
string result;

try
{
// Build code string
result = Builder.CreateCode(inputFileName);

using (var destination = new FileStream(outputFileName, FileMode.Create))
{
var bytes = Encoding.UTF8.GetBytes(result);
destination.Write(bytes, 0, bytes.Length);
}
generatedFileNames.Add(outputFileName);
}
catch (Exception ex)
{
Log.LogError("Error while compiling [{0}]", inputFileName);
Log.LogErrorFromException(ex, true, true, inputFileName);
}
}
GeneratedFiles = generatedFileNames.Select(name => new TaskItem(name)).ToArray();
Log.LogMessage("Finished Generation");
return !Log.HasLoggedErrors;
}
}