After upgrading to Prism.Forms 6.3.0 (from Prism 6.2.0) OnNavigatedFrom is no longer triggered when leaving a page (NavigationService.NavigateAsync from MasterDetailViewModel). Tested on iOS.
I am using version XF version 2.3.4.267. Is there any changes from 6.2.0 to 6.3.0 that could influence such an behaviour? Have I just stumbled upon a bug?
Any help will be appreciated.
Nothing has changed in that area of the code base. When navigating from a MasterDetail, you don't leave the MasterDetail so it won't call OnNavigatedFrom. It simply updated the Detail to the target page. When the detail page changes the INavAware methods will be called on the detail page.
Related
Yesterday I have pushed a new app to AppStore, but it gets rejected with the following error.
ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).
In my knowledge, this issue usually occurs due to the use of Webview. I have one Webview in my project, so I decided to remove it (Since that part is currently not using in the project). I have pushed the app again to AppStore after removing the Webview, but again my app gets rejected with the same error. After that I do a clean, rebuild, and deleted the bin, obj folders. 2 times my app gets rejected from Appstore after removing Webview.
See the below screenshot: No Webviews are available for the entire solution.
Are there any other reasons for this error?
This seems an existing issue of Xamarin.forms on iOS .
Make sure that the version Xamarin.Forms is 4.6 or higher and Xamarin.iOS is 13.10.0.17 or higher.
Change the Linker Behavior to SDK Only or Link All and then add the
additional arguments: --optimize=experimental-xforms-product-type
Please check all of these have been set under the release
configuration and iPhone platform.
For more details you could refer
https://devblogs.microsoft.com/xamarin/uiwebview-deprecation-xamarin-forms/
We have an Asp.Net 4.5 WebForms application that we still maintain. It uses WebForms with master pages. In VS 2019 the Go to Defintion option is completely missing when I select a form's button event and right-click. The same result when pressing the F12 key which should take me to the method definition for GetTokenButton_OnClick in the code behind page, nothing happens.
This all still works nicely in VS 2017.
Have MS dropped full support for Webforms in 2019 or am I missing an add-on or something?
This is right-click on the button event in 2017:
This is 2019> Notice how many functions are missing:
UPDATE:
I have the same issue with a class library that is part of the same solution. When hitting F12 on any of the class library's objects referred to in the web project's code, I get the dreaded "cannot navigate to symbol under the caret" error. What is strange is that everything builds and executes.
I had this issue earlier today after updating to VS2019 and tried all the solutions I found in Go To Definition: "Cannot navigate to the symbol under the caret.". None of those worked, but I solved it by updating the Microsoft.CodeDom.Providers.DotNetCompilerPlatform and Microsoft.Net.Compilers versions in my NuGet Packages for the solution.
Right-Click the solution file and click 'Manage NuGet packages for this Solution'
Under Updates, search for 'compiler'
I updated both Microsoft.CodeDom.Providers.DotNetCompilerPlatform and Microsoft.Net.Compilers to versions that other solutions we maintain use. These were 1.0.8 and 2.4.0 respectively in my case.
After that, definitions and symbols started working again.
Believe it or not but I am still maintaining this WebForms app and this now seems to have been resolved. I'm now running Visual Studio Entrerprise 2019 version 16.9.4 and the go-to-definition option is back.
let me know if anyone else, also having the same issue. it is working fine with older version but I just installed the latest version and now it's not working.
I have faced the same problem today in morning when I have updated WordPress to latest version 5.
But I have fixed the Problem by updating the Visual-composer back end-editor to latest version.
Check this link. You can see Release Notes there that says VER 5.6 - Update: Compatibility with WordPress 5.0.
So just update your plugin & sure that will fix your problem.
Try it & let me know if you have any issues.
Use the plugin call classic editor. It uses the old editor. Do not use classic editor addon. Just the standard classic editor plugin.
You can use Wordpress Version 4.9.9
It is working for me.
Download link
I can’t find Backend Editor, where is it?
The WordPress admin panel is a very unpredictable environment for such a complex product like Visual Composer. Because of that, we decided to remove Backend Editor in 2.0 version and focus our development on Frontend Editor. As a result, you as a user are getting a more stable and faster editor. Release cycles will become shorter and new features will be delivered to you faster.
To justify the “loss” we will introduce new “structured view” mode in Frontend Editor (similar how it was in the Backend Editor) and there is always Tree View mode available (a layer style representer and editor of your layout).
official website
Anyone try using Microsoft.Identy.Client package with Xamarin.Forms in MacOS project?
I try to implement OpenUrl method according to sample: https://github.com/Azure-Samples/active-directory-xamarin-native-v2/tree/master but in AppDelegate in MacOS project VS cannot see AuthenticationContinuationHelper class. Microsoft.Identity.Client class is limited:
Microsoft.Identity.Client in MacOS Project not show all items
At .Droid and .iOS project everything work properly.
Anyone was handled with this?
So there is a video from Build 2018 as well as the Slide Deck that discuss that. You need to make sure in your nuget settings you have the "show pre-release packages" checked, and then install the Microsoft.Identity.Client. I had the same issue until I did that, installed the nugets, cleaned and rebuilt the solution.
The problem with Xaramin.mac is that the library does not currently, nor does it sound like it will any time soon support the Xaramin.mac platform. This is mentioned in Open Issue #522 on the GitHub repository, after some further reading into it. That was dated on February 20th, with no news since then, so I don't believe they have it on their roadmap. Must be something with the way MacOS handles the brewer handoff, let alone the MacOS was just recently supported by some of their services in Azure, which makes me think there is not enough market share there yet in this space?
I have been using an old versión (April 2010) succesfully and I decided to upgrade to the latest versión (Dec 2013). All .NET.35 (Same as my project)
I have a page that is using a few extenders (Confirm and Autocomplete) that was working fine, the moment that I upgraded the library the page upon displaying keeps reloading in a loop.
I have removed all references to the Control Toolkit and and then it does not do it anymore, but the moment I just introduce the:
The cc1 is defined in the web.config under Pages/Controls as:
With the new library it starts an endless reloading again.
If I put back the .NET35 from April 2010, all works again
Any ideas/suggestions that any of you has heard about this issue?
Thanks
Pete