Is there a way to share an application on an existing open conversation window, using Lync 2010 SDK.
Every example that I have come across talks about starting a new conversation
Example:
Walkthrough: Share an Application Process with Another User (Lync 2010 SDK) https://msdn.microsoft.com/en-us/library/office/hh378559(v=office.14).aspx
You don't need to do anything to "share" the applications with multiple applications using the Lync Client SDK. I like to thing of the Lync Client SDK as an API that remote controls the Lync Client application.
This is why multiple applications using the Lync Client SDK works as the Lync Client runs as a separate process and can take remote commands from Lync Client SDK application processes. It is also why when the Lync Client is no running why the Lync Client SDK can't do anything.
There is a "special" mode that you can run a Lync Client as a second instance of the Lync Client process without a UI called UI suppression mode or side by side mode. Useful if you wish to do something outside of the visibility of the main Lync Client or if you are crazy enough to replace the complete UI of the Lync Client.
Related
I'm updating a very old VB.NET console application to C#. The old application used the Domino libraries to send and search through received email through a Lotus Notes client.
My organization has since migrated all email to Office 365 and the Lotus Notes server will be retired soon. I need to be able to send emails through the Outlook REST API, and use the API to search for any email received since the last time the app ran with a specific key word in the subject (no need to actually read the email, just the subject.)
I've set up the app in https://dev.outlook.com/AppRegistration, checked all the Mail API boxes and copied the Client ID. But now I'm unsure how to proceed, since every tutorial I see involves an interactive session where the user grants access to the application. My application needs to be able to run unattended. No live interaction will be possible.
To further complicate the issue, I'm developing this app using Microsoft Visual C# 2010 Express on a Windows XP virtual machine. I could probably get our IS department to upgrade the virtual machine, but most likely Windows 7/Visual Studio 2013 will be as up-to-date as I can get.
Can anyone point me to a tutorial for authenticating with the Outlook REST API in a C# .NET console application without requiring user interaction?
I have desktop app on server, that can be used by clients via Microsoft RDP or RemoteApp or Citrix ICA. And now i need to somehow interact with REAL user desktop from that application running on server in RDP/RemoteApp/ICA session.
Is there exists some server-side API in Microsoft RDP/RemoteApp or Citrix ICA that can be used to implement this?
My app is currently written in C#, but i can easily use COM/WinAPI if needed.
Yes, on Citrix you can use the Virtual Channel SDK:
https://www.citrix.com/downloads/citrix-receiver/sdks/virtual-channel-sdk.html
Microsoft also has something similar if you want to use RDP:
http://msdn.microsoft.com/en-us/library/aa383509%28v=vs.85%29.aspx
I would like to implement my own client for Microsoft Lync embedded within my business app. Is it possible to do so without having Lync installed?. I am targeting Lync SDK 2010. I have found the following information in the documentation and I was wondering if there is a solution to avoid this:
Use Microsoft Lync 2010 SDK to add communications and collaboration functionality to your application. With Lync SDK, you can add Microsoft Lync 2010 features to an existing business application, or create a custom client that includes Microsoft Lync 2010 features. In either case, Lync 2010 must be a running process on the client computer that hosts a Microsoft Lync 2010 API application.
My idea is that my .Net app should be installed without requiring any Lync installation.
If the SDK documentation indicates no... Then no. The reason for this is the Lync client still handles the actual Lync protocol. Your only other option would be to reverse engineer the Lync protocol and roll your own client from the wire up (this is assuming its not using some sort of encryption i.e. Skype).
Edit
Turns out that Microsoft published the Lync protocol documentation: http://msdn.microsoft.com/en-us/library/cc339480(v=office.12).aspx
It's possible, read this article: An Overview of the Lync APIs.
Basicly, the Lync 2010 SDK you wanted to use talks to your installed lync client, and thus needs it. But using the Unified Communications Client API (UCCA) you could write your own client while still using the handy SDK features.
I'm trying to develop a WP7 app that will download email periodically from exchange server. I was planning to use WP7 schedule task for this, but it doesn't execute in each interval. So wanted to know how WP7 email client talk to exchange server?
Is there any API/SDK available for Activesync to use in WP7.
--Thanks in advance.
No, Microsoft did not provide the APIs to third-party developers.
for now there is no API to exchange ews for windows phone. But on the exchange server you can create your own web service using EWS Managed API
Click here fore more detail
and on the windows phone use this Web Service
I'm trying to write an asp.net (using c#) app that accesses my Outlook mailbox and display the messages. I searched on google but couldn't find useful info, any help is appreciated?
You must be aware of the fact that outlook is running on user local machine, and your ASP.NET application is running on some server and there is no way that your server side ASP.NET code can use Outlook local data.
AFAIK only way to do something like that would be creating outlook addin that will export all mails to ASP.NET application
If you are using Exchange then you can use Exchange Web Services to read emails.
Please see here
Be very careful that you do not attempt to access Outlook on the server side by using the Automation interfaces. All of the Microsoft Office desktop applications are written to be run by an interactive user in a process with a message pump, with all synchronization happening via the UI. When you run them in a multi-threaded environment like ASP.NET, horrible things will happen. If you're lucky, the application will simply crash.
If you're not lucky, you can suffer from data corruption, random crashes in unrelated code, and all the other things that happen when an application corrupts memory.
You may also violate your license if the people accessing the Office application through your web site are not individually licensed to use the application on their desktop.
You can't connect to Outlook via C# (ASP.NET), but you can connect to your mailserver via POP3/IMAP to read the mail.
IMAP Client library using C#