Solutions2
Anton,
I assume it's because Outlook Client is not installed. Is it possible to use Microsoft.Office.Interop.Outlook without it?
Interop files are used for marshalling calls between managed/unmanaged boundaries. There is no the unmananged side in your case (where to marshal the call).
As already was suggested, you can use EWS instead. See EWS Managed API, EWS, and web services in Exchange for more information.
I don't have Outlook Client installed on a development server.
Moreover, Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution.