I have recently started working with Unified Communication Managed API 2.0 (UCMA) and Office Communication Server(OCS) 2007. I have a need in my app that I have to create custom presence for my users? Has anyone of you guys done this before and can point me in right direction?
There is not much documentation out there regarding this, so I am struggling here.
Thanks
I've not done any work with the 2.0 API yet, but these posts may be useful for you:
Joe Calev's Weblog (apologies if you've already seen them)
Also, there might be some useful nuggets in here (its V1 but some of the concepts are similar):
UCMA 1.0 Sample app
Ok I got the Answer.
We have to execute couple of stored procedures on OCS side to add those custom presence there.
Then we can publish to those presence just like every other ones!
Related
I want to integrate the oxford speech recognition API in a project in unity.
The problem is that the source code in the sample use .NET 4 libraries while unity only support until 3.5 (and only until .NET 2 on phones as far as i know)
Did someone found a way to make it work?
Thanks!
The sample code you mention is the SDK sample I believe. The functions that come with the SDK is just wrappers around the actual REST API requests. You don't necessarily need to use them. Instead I suggest you give the REST API itself a try. You can find the info below.
https://www.projectoxford.ai/speech
And here is sample usage for your convenience
API testing console.
One more thing to remember is the Auth token expires every 10 mins so it's a good idea to renew every 9 mins.
Hope this helps!
I've spent the last few days trying to understand if I should use api blueprint, RAML or swagger.
It looks like swagger has the biggest community but the closer I look the more I feel that it greatly lacks in documentation (I was forced to look at the code many times to try and integrate it with my current project), many github issues and stackoverflow questions are unanswered.
Is it possible that I am missing something here?
All I want is a tool to help me write the API documentation and test the endpoints.
Why must swagger become part of the server logic?? If I create swagger files in the editor and then serve them to the UI directly it breaks..
As far as I can tell it even makes the server slightly slower and forces the existence of many clumsily maintained integrations :p What am I missing here?
We're trying to work a lot on improving the documentation of Swagger. It's a bit more difficult when many of the projects are community-driven and not managed by a single organization.
We actually try to reply to issues on github quickly (we don't always succeed) and we have our own google group for general questions so we follow stackoverflow somewhat less.
The editor you mention is a new tool as part of the work on Swagger 2.0 and it's not final yet. As such, it still have a few bugs and missing features. The UI is also in the process of being adapted to Swagger 2.0 and the same limitations apply to it.
You most certainly don't have to integrate it with your server and you can expose the documentation statically. The advantage of integrating it with the server is that it's easier to maintain if the API changes.
You can try RAML + ramlev + Abao
The steps should be
Write API Spec in RAML with your fav editor, ie. Atom, vim
Validate your RAML with ramlev
Implement the server logic according API Spec
Validate server logic with Abao
I want to get a list of all running application in my windows mobile 6.5 from my application.
Can anyone tell me how to do this for CF??
You have to P/Invoke the toolhelp APIs. There used to be an MSDN article that covered this (it's a bit long to put it all into a post here, though maybe that's a better idea?). The gist of it can also be found in the SDF source code over on Github.
Can some one point me to some books or online resources to help learn about the windows cryptoapi package? I did find "Cryptography for Visual Basic" by Richard Bondi. I'd be more interested in something aimed at C++ or the package in general. The MDSN is overwhelming!
Here is a simple tutorial that could point you in the right direction. I hope it helps.
http://www.codeproject.com/KB/security/EncryptionCryptoAPI.aspx
MSDN can be overwhelming however there are some pieces of light. This page would provide you some context:
http://msdn.microsoft.com/en-us/library/ms867086.aspx
In any case, it really depends on what are you planning to do. If you're just using CryptoAPI to perform cryptographic operations you're fine with MSDN or just have a look to Wincrypt.h (there's a lot of info inside that header).
However, if you're panning to develop you own CSP (cryptographic service provider) with or without hardware you would need further information.
If you give me more details I can point you to the appropriate place (I did both things time ago).
Regards
I heard from a friend that Microsoft rewrote all the Windows Workflow Foundation (WF) again and changed everything was in .Net 3.5.
Is that true?
And what about what we learned about WF in 3.0 and 3.5?
According to this article:
http://visualstudiomagazine.com/articles/2009/01/01/windows-workflow-changes-direction.aspx
Windows Workflow Foundation 4.0 is a "bottom-up rewrite with entirely new thinking...WF 3.0/3.5 will remain part of the framework and will run side by side with WF 4.0. This lets you manage the transition at a time that fits your organization's broader goals."
...which is code for, "We know we just screwed up your programming model, but we have a long term strategy, so we hope you will forgive us."
The article goes on to say that
The gains are enormous: custom
activities take center stage, and
authoring them is much simpler;
workflows are entirely declarative;
and there are three workflow flow
styles that you can combine
seamlessly. It's possible that you
could see a 10-fold improvement in the
time required to create and debug
workflows, in addition to 10- to
100-fold runtime performance
improvements.
The change is not without its detractors. In this article at DotNetKicks, the author states that "Microsoft is seriously damaging the Dot Net developer community and adoption in the industry with these half baked product releases and abrupt about-faces after shipping."
Which is why I generally wait for the 2.0 or 3.0 version of Microsoft technologies, although I made an exception for ASP.NET MVC.
We found the workflow product to be difficult to wrap your head around when it came time to pass data in and out. Scott Allen had a series of articles that did a good job describing the process, but still this was not at an easy task.
That's what the word on the street is. And on the internet. 3.0 and 3.5 will be deprecated, but still available.
Is this change not in Visual Studio 2010 beta 1? Download it, find out, and tell Microsoft what you think of it.