In handleActionWithIdentifier:forLocalNotification:'s docs, this method is declared that deprecated from WatchOS 2.0
I looked for App Programming Guide for watchOS, at Notification section, they suggest using UNUserNotificationCenter of UserNotifications framework. But this framework does require WatchOS >= 3.0
How do my app adapt to WatchOS 2.0 user?
For WatchOS 2.0 you have to implement the deprecated method handleActionWithIdentifier:forLocalNotification:. The method has been deprecated with the introduction of the UserNotifications framework. As this framework is not available on WatchOS before 3.0, the deprecated method is the way to go for older versions.
Related
I'm trying to use Caliburn.Micro 4.0.102-alpha with .Net Core 3.0
But there is no BootstrapperBase.
So I have to ask: Is there now another concept or is the class missing in the alpha version?
Is it too early to test Caliburn.Micro with .Net Core 3.0?
Is there an other MVVM Framework available to use with .Net Core 3.0?
Your opinion or solution is very welcome :-)
I did not manage to find in the documentation Microsoft Teams extension samples that use .NET Core. Every sample I found in GitHub included those of Build 2019 are in .NET Framework. I was expected to see everything in .NET Core, especially for something like Microsoft Teams which is recent and moving fast.
So that makes me wonder if .NET Core is supported for building Microsoft Teams extension.
.NET Core was not supported for bots until Bot Framework SDK v4. It wasn't supported for Bot Framework 3.x. All of our samples that use bots, with one exception, still support Bot Framework 3.x, and we expect to support both 3.x and 4.x indefinitely: in part because there's no good way to migrate from 3.x to 4.x.
The exception is our sample app for our Bot Framework 4.x SDK, which is currently in beta.
Over time we expect to focus more on .NET Core as we add Bot Framework SDK 4.x support to more of our samples.
Want to run a .net framework 4.x or 3.x client against a asp.net core 2.0 signalr service. possible?
for now my client is a .net framework 4.x or 3.x console app.
eventually it will be a DLL i drop into unity3d plugins directory.
Then i can call my methods like so MyNet4ClientClass.MakeSignalrCoreCall(data).
Is this possible? Can .NET 3.x or 4.x talk to asp.net core 2.0 signalr service?
I tried to add the nuget package for Microsoft.AspNetCore.SignalR 1.0.0-alpha2-final but....
"Could not install package 'Microsoft.AspNetCore.SignalR 1.0.0-alpha2-final'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.5', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author. 0 "
i thought this post was hopeful
https://www.rizamarhaban.com/2016/09/13/asp-net-core-signalr-for-windows-10-uwp-app/
in the post the guy talks to signalr code 2.0 from a UWP app
the client UWP app uses "Microsoft.AspNet.SignalR.Client": "2.2.1" from nuget
and service which uses Microsoft.AspNetCore.SignalR.Server: 0.2.0-alpha1-22118
obtained from https://dotnet.myget.org/F/aspnetcore-ci-dev/api/v3/index.json repository
this works its seems because these older SignalR.Server packages still exposes themselves the old signalr way. you can see from the url it exposes at /signalr/hubs
but the new new signalr core changed its protocol sometime so now incompatible.
how can i talk to the new new signalr core from .net framework 4.x or 3.x client ?
Is there any plan to support .NET Core in the near future? I mean, without refactoring my bot code. There are still components not compatible with it.
Yes, it is planned and in the works. You can follow the topic on this related GitHub issue: [Feature Request] Porting to .NET core #572
Update 2017-10-26:
Bot Framework team is working on a complete rewrite of BotBuilder SDK (v4) which will be fully compatible with .NET Core.
Update 2017-12-14
Bot Builder v3 - New Bot Connector support for ASP.NET Core 2.0 and 1.1 has been released on NuGet!
We’ve released two new nuget packages for the Microsoft Bot Connector to support .NET Core 2.0:
Microsoft.Bot.Connector.AspNetCore.1.1.3.2.nupkg
Microsoft.Bot.Connector.AspNetCore.2.0.0.3.nupkg
The above packages each target ASPNetCore 1.x and ASPNetCore 2.x respectively, and provision authentication for your bot. They must also use Microsoft.Bot.Connector.3.12.2.4 or higher.
My application is ASP.NET MVC5.1 and ASP.NET WEB API 2.1. The application
is small and currently using Microsoft Unity for IOC.
Can someone advise me if they know of any changes needed to make Unity
work with these very new releases of MVC and Web API?
I am also considering changing to Ninject depending on features.
If I made this move then what features does it offer that the latest version of Unity lacks? My big concern is that Ninject appears to be well supported whereas Unity seems to be a product that's updated every couple of years when the Microsoft guys have the time to look at it.
Finally how much of a change is needed if I change from Unity to Ninject?
I don't know much about Ninject, but we upgraded our MVC4 to MVC5 application here earlier this week, following the instructions for How to Upgrade an ASP.NET MVC 4 and Web API Project to ASP.NET MVC 5 and Web API 2.
The application is already in production, so I can confirm that Unity supports these new releases! Then you can continue to use it without any damage.
Hope it helps to make your decision.
See ya!
Yes, you can use Unity 3.0.1304.1 in ASP.NET MVC/WEB API 5.1 and 2.1 project.
I use it, because i can't configure ninject without any bugs for latest mvc core libraries.