Comments (5)
Had the same issue on the GitHub action for the build. It seems due to the release of .NET 7. The dependency resolution in the script uses the newer versions of build packages that are released with .NET 7. We fixed it in FAKE by pinning the packages in the build script:
nuget Microsoft.Build 17.3.2
nuget Microsoft.Build.Framework 17.3.2
nuget Microsoft.Build.Tasks.Core 17.3.2
nuget Microsoft.Build.Utilities.Core 17.3.2
from fake.
There's a related part of this - components that want to use the version of MSBuild shipped with the .NET SDK should not actually copy the MSBuild dlls to the application directory. This can be done via the use of ExcludeAssets="runtime"
or copy_local: false
. Then, MSBuildLocator can be used to discover and load the SDK MSBuild assemblies. This is how projects like Ionide.ProjInfo and Buildalyzer work, and IMO it's how all MSbuild-using utilities should work. Unfortunately, NuGet doesn't allow marking these dependencies in a way that would make the ExcludeAssets="runtime"
happen automatically.
from fake.
Welcome to the FAKE community! Thank you so much for creating your first issue and therefore improving the project!
from fake.
Just ran into it and had a quick workaround thanks to your comments here :)
Should fake.dotnet.msbuild list the nuget dependency to prevent this or did i miss something? at least it it not listed here https://www.nuget.org/packages/Fake.DotNet.MSBuild/5.23.1#dependencies-body-tab
from fake.
when I use dotnet fake build
to run run my csharp project, I also got the similar issue as follow:
Resolving dependency graph...
- FSharp.Core is pinned to 6.0.0
Could not detect any platforms from 'net7.0' in System.Collections.Immutable 7.0.0, please tell the package authors
Could not detect any platforms from 'net7.0' in Microsoft.Build.Framework 17.5.0, please tell the package authors
Could not detect any platforms from 'net7.0' in Microsoft.Build.Utilities.Core 17.5.0, please tell the package authors
Could not detect any platforms from 'net7.0' in Microsoft.NET.StringTools 17.5.0, please tell the package authors
Could not detect any platforms from 'net7.0' in System.Security.Permissions 7.0.0, please tell the package authors
Could not detect any platforms from 'net7.0' in System.Configuration.ConfigurationManager 7.0.0, please tell the package authors
Could not detect any platforms from 'net7.0' in System.Text.Encoding.CodePages 7.0.0, please tell the package authors
Could not detect any platforms from 'net7.0' in System.Security.Cryptography.Pkcs 7.0.1, please tell the package authors
Could not detect any platforms from 'net7.0' in System.Security.Cryptography.ProtectedData 7.0.1, please tell the package authors
Could not detect any platforms from 'net7.0' in System.Formats.Asn1 7.0.0, please tell the package authors
Could not detect any platforms from 'net7.0' in System.Windows.Extensions 7.0.0, please tell the package authors
my local env just installed .net6.0
SDKs and have installed fake-cli
with 5.23.1
, but I don't know that it always to find net7.0
.
Feel free if you have any idea about this error ?
from fake.
Related Issues (20)
- How can i set build.fsx to pick VS2019 MSBuild toolversion HOT 6
- Code should search for sqlpackage in $PATH on Unix-like OSs HOT 2
- `System.IO.Stream` error when using SharpCompress HOT 7
- How can i set build.fsx to pick VS2019 MSBuild toolversion HOT 10
- Fake HOT 1
- Fake script fails with Error: `The specified file name or path is too long` HOT 2
- Update Paket.Core to support .NET 7 HOT 1
- Error detecting msbuild version on Linux HOT 1
- Update to .NET 7 HOT 9
- Could not find a suitable .NET 6 runtime version matching SDK version: 7.0.100 HOT 33
- Jsjsks HOT 1
- `StringBuilder.appendQuotedIfNotNull` is used incorrectly. HOT 4
- Documentation: Fileformat for Releasenotes not rendered correctly HOT 3
- dotnet local tool fails when run via FAKE, but succeeds when run via command line HOT 8
- Fake.DotNet.Fsdocs watch command missing arguments. HOT 2
- MSBuild.build adds a bad string at the end of properties HOT 8
- Update MSBuild.StructuredLogger to latest HOT 13
- Why is the launch property not being passed into the `dotnet run` correctly? HOT 3
- Unsupported log file format. Latest supported version is 14, the log file has version 16. HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fake.