As Uno.Material is marked as a pre-release package, should the other Uno libraries' versions be upgraded to pre-release as well?
If you check the 'Dependencies' tab in the Uno.Material NuGet listing, you'll see that
Uno.Material requires (at time of writing) Uno.UI 3.0.0-dev.1533 or higher (which is the version it happens to be built with). Therefore you should be fine using the Uno.UI 3.1.6 stable release or higher.
Related
I have been using Google.Cloud.Translation.V2 in a UWP app for a while. Its latest NuGet package is 3.1.0. Upgrading from 2.x to 3.x results in the following error:
NU1202: Package Google.Cloud.Translation.V2 3.1.0 is not compatible
with uap10.0.19041 (UAP,Version=v10.0.19041) / win10-x64-aot. Package
Google.Cloud.Translation.V2 3.1.0 supports:
net462 (.NETFramework,Version=v4.6.2)
netstandard2.1 (.NETStandard,Version=v2.1)
Does this mean the newer versions will no longer work with UWP apps?
Does this mean the newer versions will no longer work with UWP apps?
TLDR; UWP is not a supported platform
From this GitHub issue:
We don't currently support UWP, and even if using grpc-dotnet makes it technical work, it's unlikely that we will prioritize UWP support over other work. So when we have moved over to grpc-dotnet by default, you may be in a situation where you can try to use the libraries and quite possibly be successful, but we would still not support it.
Also shown in this comment:
To reiterate: UWP is not a supported platform for these libraries. You could potentially use the Google.Apis.* NuGet packages, which don't use gRPC, but again, UWP isn't a supported platform for those either.
Final note (from this comment):
You may find that the REST-based libraries for whichever APIs you're using (packages starting "Google.Apis") work, but again those aren't actually supported on UWP.
is there a way to know when a version of Flyway is going to get deprecated?, actually we were using 6.0.7 the last year and then got deprecated like 6 months ago, now we are using 6.4.1 but I tried to find something on the blog and documentation but there's nothing about some news of when a version is going to be deprecated, only when we run our java spring boot project we know that a version is not usable. And we're aware of this because there's a lot of changes in version 7+ that doesn't work with our project (tested version 7.0.1 and the app crashed) and we need to estimate the cost of the changes.
Any help would be appreciate, thanks.
Flyway releases via Maven OSS. Old versions are kept indefinitely and are outside of Redgate's control. In theory, all older versions which are currently available on Maven will continue to be available for all time.
Newer versions may deprecate features over time, but older versions will always be available.
When I scan my site with modern.ie, it says:
We've found frameworks or libraries that are not up-to-date and might
contain bugs.
modern.ie detects that my site is running jQuery 2.2.0 (the latest version).
Is there a bug with the modern.ie site?
What version of jQuery are you using?
You can check the current open bugs in its public GitHub repo https://github.com/MicrosoftEdge/static-code-scan and open a new issue if you find one
We are running an old version of plone (Version 2.0.5). (We will migrate next year to plone 4)
I was trying to install the Plone Hotfix 20121106, but (as mentionened in the installing description), the hotfix will not apply to the version 2.0.5 of plone.
Questions:
Are the security vulnerabilites also relevant for the plone version 2.0.5?
Is there another way to install the hot fix on that old version of plone?
Some of the security vulnerabilities do apply to 2.0.5, yes.
However, there are other unpatched vulnerabilities in 2.0.5 not addressed by this hotfix, and you want to move away from this old a version as soon as possible. The Plone security team does not provide official support for Plone versions this old; currently 3.x and 4.x releases are supported.
You can unzip the hotfix into your Products folder, and it should just work. I believe people have tested it on 2.0.x installations already; the test coverage certainly was run on 2.1. You'll have to run your own tests though to make sure nothing (important) breaks for you when the fix is installed.
I have a fairly large ecommerce site running on S#arp Arch 1.9.5. I just saw that the codebase is up to 2.0.4. First of all, nice one to everyone involved, I thought it was dead in the pan after waiting for 2.x for quite some time (...and Ayende ripping into it).
Is there a recommended upgrade path from 1.9.5 to the latest version? Do I just nuget update-package?
I personally upgraded my instance by download the 2.0.4 package from Github (seen below) and then update it locally. I did not meet any problem. Like you i looked for update suggestion but decided to do it manually.
https://github.com/sharparchitecture/Sharp-Architecture/downloads
I did find 2.0.4 Sharp-architecture package at Nuget however I did not run nuget update-package in my application.