I'm currently facing an issue that I have to login with msal without any redirections and stumbled across the release notes of msal 1.2.0 where it said that there is now the feature "silentLogin()" included.
After installing msal 1.2.0 (via npm install) the function silentLogin() isn't there...
I just replaced the msalInstance.liginRedirect(request); with msalInstance.loginSilent(request);
Does anyone know more about this?
This was a mistake in the release notes, and should not have been included. We'll make sure this gets fixed. Apologies for the confusion!
(We are planning to add an ssoSilent API in a future version of the library, but that is not available yet.)
Related
So today I was updating one of our SPFX extensions to use the latest spfx framework (1.16) with node (16.13) and after finishing my updates I got the following inside my code:
I am not exactly sure why these are not coming in, I suspect the newest version of spfx moves these classes out of sp-application-base, but why? and where is the documentation for it? Because there is this link that is only 6 months old and explains to use this code for the top and bottom headers.
I was expecting this code to remain in sp-application-base, but it appears it isn't in that package.
How did you perform the upgrade? I highly recommend using the Microsoft 365 CLI to upgrade projects, as the developers of that app do thier best to cover every part of the project that needs to change. Learn more at https://pnp.github.io/cli-microsoft365/cmd/spfx/project/project-upgrade/
Here are the commands to run from the root of your project
npm install -g #pnp/cli-microsoft365
m365 spfx project upgrade --output text
This will give a list of npm commands and code update instructions to follow. See the above documentation for other options for output and use whatever works best for you.
It is still there. What version of #microsoft/sp-application-base is in your project? Should be 1.16.1 I believe. I will say that I am new to all of this as well, but I am using the latest framework and VS is not flagging any issues with these.
webdatarocks v1.4 was released a few days ago
There's no public changelog or post
Anyone knows what changed in this version?
This release was mainly focused on new integration wrappers for Angular, Vue & React. So now it's easier to integrate it via npm.
Also, new predefined skins were added like Striped-Blue, Striped-Teal & Green.
Plus, a few minor fixes were done.
More detailed info can be found here: https://www.webdatarocks.com/blog/webdatarocks-1-4-release-new-long-awaited-features/
Is there a manual describing migration from Bot Builder SDK v3 to v4?
I have a lot of compilation errors after updating NuGet packages
Update
It appeared to be difficult. In addition to the answer below, I found this post quite useful to get a general picture https://blogs.msdn.microsoft.com/martinkearn/2018/07/17/bot-framework-v4-what-i-learnt-in-4-days-in-july-2018/
You can't just update your NuGet packages from V3 to V4, without changing your code. It is a major release with a lot of breaking changes.
The roadmap
for botbuilder-dotnet describes that a migration path from V3 to V4 is still in progress. I would suggest to have a look at BotBuilder-Samples and Microsoft Docs for the moment, to get an idea about how much has changed.
There are lot of changes from V3 to V4, they have completely re-written the concepts, architecture and terminologies.
So just updating the libraries won't work, you must update the code as well.
The roll-out is still not complete so it is recommended to use v3 in production as of now.
Upgrade is almost equal to the efforts of writing the complete bot code again. In case you are comfortable with your existing bot functionality and is willing to add new features which has nothing to do with SDK version, you can do this using Bot Channel Registration. Steps to do this is mentioned in a blog here - https://chatbotslife.com/microsoft-bot-framework-sdk-3-code-on-azure-bot-service-without-migrating-to-sdk-4-14afa3300887
I'm getting some errors after updating from Firebase 2.5.1. It seems to me that GeoFire has lost some critical components, and being a beginner I am immediately lost. Has anyone seen this issue yet?
Below is a screenshot of my list of errors.
To add a little more info, here are the lines where the errors are occurring in GFQuery.h:
- (FirebaseHandle)observeEventType:(GFEventType)eventType withBlock:(GFQueryResultBlock)block;
- (FirebaseHandle)observeReadyWithBlock:(GFReadyBlock)block;
- (void)removeObserverWithFirebaseHandle:(FirebaseHandle)handle;
The current geofire version is not compatible with Firebase 3 the team is currently working in a compatible version
You can follow the issue here
https://github.com/firebase/geofire-objc/issues/37
I'm looking for Symfony2 forum bundle, which is:
working
not dead
supports sf 2.1
Anyone knows of such a thing?
check this one out:
http://packagist.org/packages/herzult/forum-bundle
It has been updated recently and it is symfony 2.1 ready. You can install it through composer.
Also check http://packagist.org/packages/friendsofsymfony/comment-bundle that allows you to threading capabilities to your symfony application.
You can always check http://packagist.org for symfony 2.1 ready bundles ;)
If you have any problem instaling these feel free to ask.