Searching in the Microsoft Graph documentation, I found this:
https://learn.microsoft.com/es-es/graph/api/user-post-events?view=graph-rest-1.0&tabs=java
It says that you can create an event with an online meeting using Java "Event" type.
Code example
But the problem is, when I tried to do it with the current last Microsoft Graph SDK version 1.7.1, I noticed that "event.isOnlineMeeting" and "event.onlineMeetingProvider" don't exists.
Is it not implemented yet? Or I'm missing a new Microsoft Graph version, or something...
Edit 1
I clarify, this is not a code error, rather it is about knowing why Microsoft Graph documentation shows an example of Java code which makes use of "event.isOnlineMeeting" and "event.onlineMeetingProvider", while In the latest version of the Microsoft Graph SDK for Java, these fields of the "event" object do not exist.
Microsoft Graph API Reference
Microsoft Graph Git repository
Edit 2
In the latest versions of the Microsoft Graph SDK for Java, the event object already has both fields.
In the latest versions of the Microsoft Graph SDK for Java, the Event object already has both fields.
Related
I am having troubles with updating my OData Client.
I would refer to How to call bound functions / actions inside Java client using SAP Cloud SDK? where people from SAP helped me alot, thanks!
Issue is, I wanted to update dependency to last version of SAP Cloud SDK because of new functionality that supports bounded functions and actions.
Back then (4 months ago), I had written myself documentation how to generate and use OData Java client properly, using SAP Cloud SDK. Quite a number of people was succesful back then with installing.
Now, 4 months later, I cannot generate properly client. I have installed lombok and also set it as reference in Eclipse and am using latest Eclipse (2021-06).
I will put screenshots of my errors. It says like my properties are not generated properly and that 1 method is missing - getOdataType().
These problems just started to occur last 2 weeks or so.
Thank you in advance!
At the time of this post there are two Azure Service bus SDKs sitting within sdk/servicebus:
Microsoft.Azure.ServiceBus
Azure.Messaging.ServiceBus
They have both been updated very recently (past week).
This ms doc (written two weeks ago) states;
This quickstart uses the new Azure.Messaging.ServiceBus package. For a
quickstart that uses the old Microsoft.Azure.ServiceBus package, see ....
Where as this document (also written two weeks ago) says;
There are two supported Azure Service Bus .NET SDKs. Their APIs are
similar, and it can be confusing which one to choose. Refer to the
following table to help guide your decision. We suggest using the
Microsoft.Azure.ServiceBus SDK as It's more modern, performant, and is
cross-platform compatible. Additionally, it supports AMQP over
WebSockets and is part of the Azure .NET SDK collection of open-source
projects.
This document goes on to mention Microsoft.Azure.ServiceBus as newer and (yet another SDK) WindowsAzure.ServiceBus as older. It does not mention Azure.Messaging.ServiceBus at all.
Does anyone have any advice on which SDK should be used for a new .NET Core 5.0 project?
(I have already reviewed this question which has not helped)
For projects that have no dependency on the older packages, use Azure.Messaging.ServiceBus. For everything else, look at the dependencies. For example, Azure Functions cannot use the latest package today. It will likely be addressed in the future just not ATM. I wrote a blog post awhile ago about these 3 packages. May (or may not) help you with your question.
Is there an api to monitor Microsoft Edge browser version and its release dates?
more like https://omahaproxy.appspot.com/all.json
for google chrome.
Thanks in advance!
If anyone is looking for endpoint for finding current released version of Microsoft edge, you can get information from following,
Edge Latest Stable Version
For more information you can find answer on following
Microsoft Edge Latest Version Number
In the Swagger UI, the model/model schema are documented in the Parameters section. When I import the same documentation into the Azure API Management portal, parameters with .NET data types are documented but the complex object/model/model schema in the request body loses its documentation.
I saw an update for Model Schema support Azure API Management adds support for Swagger model schemas.
But it did not work when I tried it in the API Portal.
Do anyone know how to import the Model Schema Documentation into the Azure API Management Portal?
Is this update available in New Portal only? And if so when will API management be available in New Portal?
Note: I am using Swagger 2.0 documentation from Swashbuckle in Visual Studio 2013.
Model schemas are imported if they are in the Swagger file. If that's not the case your saw, can you please send your Swagger file to apimgmt at microsoft dotcom so that we can take a look at the file.
I was able to repro this issue and have fixed it. Hopefully, I will be able to get the fix in the next release.
I am looking to create an application that allows a user to update Microsoft Team Foundation Server work items when performing certain things in the app.
Has anyone done anything similar themselves and if so what is the best way to make the updates to the TFS work items from within the app?
There is a Java API which is linked below:
http://www.microsoft.com/en-us/download/details.aspx?id=22616
Other than that a few google searches resulted in the following discoveries:
http://msdn.microsoft.com/en-us/library/bb130146.aspx
The link below tells you how you can create new work items via a URL:
http://msdn.microsoft.com/en-us/library/bb822136%28v=VS.90%29.aspx
** As per jessehouwing's comment below *
This only works on 2008 and 2010 I suspect. There migth be a similar Url for 2012 and 2013, but the whole WebAccess feature was rebuilt using ASP.NET MVC instead of WebForms, so the wi.aspx no longer exists. I'm not aware of an alternative.
Visual Studio Online an Team Foundation Server 2013 are gaining more and more json based REST Api's and have recently been upgraded to support OAuth for authentication. Some of these API's are still in preview, but they're a great resource for a mobile platform client.
For older versions of Team Foundation Server and the On-premise version you can either install the OData service, or build a custom webservice that employs the TFS Client Object Model internally to create the work items.
Should you want to build your webservice on top of a non-microsoft-platform, then you can employ the Java SDK for Team Foundation Server. This will allow you to communicate directly to TFS from a Linux or Mac server.
TFS 2013.4 will be able to show more pages in full screen mode without any chrome around it.