Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Question]: Nuget package version compatibility
See original GitHub issueHello,
We’re using Azure DevOps to run our Playwright tests and at the moment we’re installing Playwright on demand before we run the tests via pwsh bin/Debug/net6.0/playwright.ps1 install --with-deps chromium
This takes approximately 1m 30s to install it.
We’d like to “pre-install” Playwright by baking it into a Docker image that we would use via a self-hosted build agent.
We’re not sure however if there is some sort of strong-coupling or backwards compatibility issues - e.g. if the current “client” Nuget version is 1.22.0 and we would bump the “server” to a newer version in our Docker image - would this lead to any issues?
The vice versa I would expect to lead to issues, especially if the “client” relies on some new functionality that is not available on an older “server” version.
Thank you, Cosmin
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:18 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
TL;DR: if you use the official Docker image with the exact version as .NET dependency, then you don’t need install/install-deps if you use an official supported OS aka Ubuntu or the official Docker image with a different version tag, then you need install/install-deps OR
install --with-depsYes please, because like this you generate a huge amount of notifications, people will get emails etc. I’m totally fine with the other way!