Vatsalya Goel

A quick suggestion before we proceed this bug, Can you try having the MvxSetup on both Mvxsplashscreen and MvxFormsAppCompatActivity by adding this and then try to replicate the behaviour SplashScreen.cs...

Hi @nickrandolph I was able to reproduce and solve the issue by following the steps above. The issue happens because the app is not launching form SplashScreen but rather from...

https://github.com/MvvmCross/MvvmCross/pull/3066#issuecomment-415269471 a way to solve this issue

After diving into Winget Source Code and investigating logs, in my case it ended up being a Registry issue. First, run `winget list --upgrade-available --verbose-logs` Then `winget list --upgrade-available --logs`...

This is more a design conversation @cafferata @tlimoncelli. We can add the support for CanUseAlias however. the provider support for specific features is based on intent and what they actually...

My proposal is as follows: ```js var REG_THIRDPARTY = NewRegistrar('none'); ``` Add a Record Modifier IGNORE which takes in an array of registered providers ```js var ignoreThirdParty = IGNORE([REG_THIRDPARTY]); ```...

Looking into the issue

@fabienmazieres When adding additional NAMESERVER Records, you don't need to specify the Azure records on the domain. NAMESERVER("ns1-01.azure-dns.com."), NAMESERVER("ns2-01.azure-dns.net."), NAMESERVER("ns3-01.azure-dns.org."), NAMESERVER("ns4-01.azure-dns.info.") These will automatically be there when DNSControl gets the...

@tlimoncelli maybe I should add a PR to de duplicate NS/Nameserver records if we detect that there are any. But I don't know if it would go against the design....

Added a PR fix to the issue