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.
Move Tye to .NET 6
See original GitHub issueWhat should we add or change to make your life better?
- Move Tye to .NET 6 now that it’s GA.
- Consider moving to all-in-one executable released in both x86 and ARM flavors for each platform.
- Consider then eliminating dependency on
dotnet toolmechanism for installation (i.e. have Tye be a standalone CLI)
- Consider then eliminating dependency on
Why is this important to you?
Developers will tend to migrate to .NET 6 being the new LTS version, meaning fewer will have .NET Core 3.x installed (currently required for Tye). Moving to .NET 6 will also avoid x86/arm issues currently seen on Apple Silicon.
If we were to also move to all-in-one executables, we could also eliminate the need for a particular version of .NET runtime just for the purposes of running Tye. Eliminating our dependency on dotnet tool would also be helpful for those wishing to use Tye with non-.NET development platforms.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:15
- Comments:8 (4 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
@philliphoff Its still not available when using
As the port to .NET 6 is done, and CI builds are available, I’m going to close this issue. The question of splitting off of
dotnet toolor otherwise becoming a self-contained CLI tools will be tracked as a separate issue (if and when we decide to pursue it further).