My team is working on MSAL migration and we found "microsoft.bot.Connector" nuget is using ActiveDirectory reference internally.
What is the latest version of microsoft.bot.Connector nuget which is migrated for MSAL?
A sample code for latest version upgrade for MSAL will also help.
As per the Dotnet SDK releases, 4.16.0 is the most recent version to merge work on MSAL. Your screenshot shows version 4.14.4, which is too old to have those fixes. Please update to 4.16 or newer.
Related
I'm migrating from VS2015 to VS2017, and updating a repo's solutions to be able to be compatible with VS2017. In the process, I'm also updating the Azure SDK version from 2.7 to 3.0.
I'm setting up a fresh dev environment, and installed Azure SDK 3.0 via VS2017's Azure development workload.
When I opened the solution file in the repo, I got one notice per cloud service project that its Microsoft Azure Tools version was getting upgraded from 2.7 to 2.9...
...and the ProductVersion tag in the corresponding .csproj files was updated from 2.7 to 2.9.
Questions:
Why wasn't this updated to 3.0?
Is there anyway for me to update it
to 3.0 without manually editing the csproj file? I don't see an
option to do so in Properties when I right click the cloud service
projects in Solution Explorer.
Is there some reason I shouldn't be
doing this?
"Microsoft Azure Tools - v2.9" mentioned in your screenshot is just a little misleading.
Underlying reason is that Microsoft hasn't really changed the version number of most components as part of 3.0 SDK release. Even the binaries get installed in the same folder as 2.9.
Good news is that you don't need to do anything special apart from converting the project to target latest version, which you're already getting prompted for.
So once you do convert your project as per the prompt, you're essentially working with SDK 3.0, even though version string says v2.9, because as the links explain, most of the components haven't changed major version number as part of SDK 3.0 version (when comparing with 2.9)
Here are some of the links which talk about this -
Azure SDK for .NET 3.0 Release Summary
No breaking changes to the Azure SDK 3.0 have been introduced in this
release. There is also no upgrade process needed to leverage this SDK
with existing Cloud Service projects. To allow use of the Azure SDK
3.0 without requiring an upgrade process, Azure SDK 3.0 installs to the same directories as Azure SDK 2.9. Most the components did not
change the major version from 2.9 but instead just updated the build
number.
Visual Studio 2017 latest installer does not install Azure SDK 3.0
In this link look at the response from Devin Breshears - MSFT
Azure 3.0 SDK Install Weirdness
An independent blog talking about the same issue.
We are using NotificationHubs version 1.0.9 with .NetCore 2.0 and .Net Framework 4.7.
At compile time, we get this warning:
"Package Microsoft.Azure.NOtificationHubs 1.0.9 was restored using '.NETFramework, version=4.6.1' instead of the project target framework '.NETCoreApp, version=2.0. this package may not be fully compatible with your project."
Everything is still built, but at runtime when this call is invoked:
RegistrationDescription hubRegistration = await hubClient.CreateAppleNativeRegistrationAsync(device.DeviceToken); //hubClient is NotificationHubClient
We get this error:
Has anyone encountered this before and have any idea how to fix it?
At compile time, see this warning: "Package Microsoft.Azure.NOtificationHubs 1.0.9 was restored using '.NETFramework, version=4.6.1' instead of the project target framework '.NETCoreApp, version=2.0. this package may not be fully compatible with your project."
The Microsoft.Azure.NotificationHubs package requires .Net Framework 4.5 Full Profile. And here is a feedback Microsoft.Azure.NotificationHubs add support for .NET CORE.
AFAIK, if you create the ASP.NET Core Web Application with the target framework at .NetCore 1.0 or .NetCore 1.1, you could edit your *.csproj and change the TargetFramework to net461, then you could install and use Microsoft.Azure.NotificationHubs 1.0.9.
While for .NetCore 2.0 MVC, after you create the project, it would reference the Microsoft.AspNetCore.All 2.0.0, and this package supports netcoreapp2.0. I assumed that you could leverage Notification Hubs REST APIs and follow the git sample azure-notifications Send REST to access your notification hub for a workaround.
A preview version of a .NET Standard compatible NuGet is now available. It will allow using Notification Hubs with .NET core.
According to a Microsoft Product Manager a new version of the .NET SDK supporting .NET Core will be deployed very soon.
cf this question
But no mention on Feedback Microsoft site. I would recommend to vote for this feature
Does Microsoft publish release notes for individual nuget packages?
I noticed a few nuget packages with a 'dot' release (which leads me to believe some bugs were resolved) but I can't find information about what exactly was fixed in these dot releases.
Here are a few examples, picked at random, of packages released by Microsoft:
System.Net.Http version 4.3.2
System.Reflection.Metadata version 1.4.2
System.Collections.Immutable version 1.3.1
Microsoft.Data.OData version 5.8.2
Microsoft ASP.NET Identity Core 2.2.1
The description for most of these packages says that release notes are available at https://go.microsoft.com/fwlink/?LinkID=799421 but that's a link to the release notes for .NET Core 1.1.0 Preview 1 released 10/24/2016, nothing specific to the packages.
An example of a Microsoft nuget package that publishes very clear release notes for each version is Windows Azure Storage.
Please give some details about the latest released version of ARM SDK. Because i could see the MVN repository having 0.9.4 , beta1 and beta2 versions. Please suggest which version going to be stable.
In GitHub link do not have java-docs for 0.9.4 version release. Please share the link for the same.
I referred the below link but it is having v0.9, 0.9.3, beta1 and beta1+fixes releases.
https://github.com/Azure/azure-sdk-for-java
I referred the link to download SDK. But it is having only 0.9.0 like (azure-svc-mgmt-0.9.0) version
https://azure.microsoft.com/en-us/downloads/
Why the latest version SDK documentation not uploaded in azure site. Please give me some suggestion to get rid of this. Which version last stable release?
Thanks in advance.
Regards
Rathidevi
Recently azure has released 1.0.0 as stable release and this Java SDK version is the latest stable version.
This version has changed drastically compared to older stable versions such as 0.9.0.
I would recommend you to upgrade you to new Java SDK version 1.0.0.
I have an AzureAD registered Web API working correctly. I am able to acquire the access token by means of AcquireTokenAsync. No problems there. However, no I need to downgrade my rest client library to .net 3.5. I am not being able to use ADAL in .net 3.5. AcquireTokenAsync returns a Task, which is not supported in 3.5. I have read in some tutorials that there is a non async verstion of the method (AcquireToken) here. But I just can't access that method. Also, when I try to install that specific version of ADAL(2.19.208020213) I get a Nuget error saying there is no version supported to .Net 3.5
What am I doing wrong?
UPDATE
I am trying to find out which version of ADAL targets .Net 3.5 so I can install it in my project.
UPDATE 2
If ADAL is not supported in .Net 3.5, what are my options to obtain authorization token from Azure AD in .net 3.5?
The library only supports 4.5 because async support was added in that .net release. You may need to dig back to very old versions of the library to get older .net sdk to work. But you would lose significant big fixes and features.