Comments (1)
As per the Central Package Management the .props file name should be Directory.Packages.props
instead of Directory.Build.props
.
When I renamed the. props file, I was unable to reproduce the issue by following the steps mentioned in the issue description.
![image](https://private-user-images.githubusercontent.com/52756182/327610187-3c6848e0-593a-4f12-83f9-26aa6e16ad43.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIyMjc5MDEsIm5iZiI6MTcyMjIyNzYwMSwicGF0aCI6Ii81Mjc1NjE4Mi8zMjc2MTAxODctM2M2ODQ4ZTAtNTkzYS00ZjEyLTgzZjktMjZhYTZlMTZhZDQzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI5VDA0MzMyMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTU2NjM3MGMwMjk1MjM4ZGFiYmMyZmJkNDY4ZjI1NDczNmUyNTU3ODUxNmNmMDZhY2M0OWViYjA1MjA2OTFhY2YmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.kykBeVa8ceETP7ylb3PWDyY11TDXnuUka0YN_HmkIfk)
![image](https://private-user-images.githubusercontent.com/52756182/327610222-453e5c70-39e7-474e-86b2-9232c6df0de1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIyMjc5MDEsIm5iZiI6MTcyMjIyNzYwMSwicGF0aCI6Ii81Mjc1NjE4Mi8zMjc2MTAyMjItNDUzZTVjNzAtMzllNy00NzRlLTg2YjItOTIzMmM2ZGYwZGUxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI5VDA0MzMyMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWFmNGIxYTY2MjhkMWM4YWIwMWE5NmNlNDBiY2QzM2E2ZmY0MWE3NmM1NDYwNTdiN2NhMWFiMTdkMTY4OWY0ODMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.Fpji5xOHbHemRtlmxXfRBfiyjCpcqNaFCfSqsy79ixc)
Then I executed dotnet list package
command whose output matched with versions displayed in the VS.
> dotnet list package
Project 'MainProject' has the following package references
[net8.0-windows7.0]:
Top-level Package Requested Resolved
> CommunityToolkit.Mvvm 8.2.2 8.2.2
> Microsoft.Extensions.DependencyInjection 8.0.0 8.0.0
> Microsoft.Extensions.Hosting 8.0.0 8.0.0
Project 'SecondProject' has the following package references
[net8.0-windows7.0]:
Top-level Package Requested Resolved
> Microsoft.EntityFrameworkCore 8.0.0 8.0.0
> Microsoft.EntityFrameworkCore.Design 8.0.0 8.0.0
> Microsoft.EntityFrameworkCore.SqlServer 8.0.0 8.0.0
> Microsoft.EntityFrameworkCore.SqlServer.HierarchyId 8.0.0 8.0.0
> Microsoft.EntityFrameworkCore.SqlServer.NetTopologySuite 8.0.0 8.0.0
> Microsoft.EntityFrameworkCore.Tools 8.0.0 8.0.0
I am closing this issue as not a bug. Please feel free to reopen it if the suggestion to change the file name to Directory.Packages.props
doesn't work for your scenario.
from home.
Related Issues (20)
- [Bug Bash] Punctuation located incorrectly in the bottom-text of the “License Acceptance” dialog HOT 7
- Make 'why' command available in NuGet.Commands HOT 1
- [Localization] Revert latest changes from 6.11.x branch HOT 1
- Error NU1301 instead of "TLS validation failed" displays when running ‘dotnet restore’ before TLS certificate validation is disabled HOT 9
- dotnet add package stops checking sources on the first failure http code HOT 2
- Can not install signed package with certificate chain building issue HOT 2
- Fetching Vulnerability Resources doesn't respect cancellation HOT 1
- Improve the PM UI (especially update) experience for CPM transitively pinned packages
- PERF: NuGet Cloning operations are showing heavily in allocations during VS solution load
- Consider offering snapshot functionality as an alternative to lock files HOT 2
- Machine readable output for 'why' command
- [Cross-platform Dotnet NuGet Sign] Adding trust for a certificate leads to an error SYSLIB5007 for .NET SDK 9.0.1xx HOT 1
- [Cross-platform Dotnet NuGet Sign] The error “invalid value for’--certificate-fingerprint’ option” displays instead of error NU3001 when signing with certificate search criteria yields no certificate matches HOT 1
- Publish error: `Found multiple publish output files with the same relative path` for `packages.loc.json` files. HOT 1
- Coud you reference a bug in the docs, please?
- [Tech Debt] Improve test for XPlatHelpOutputTests.cs
- Publishing to BAR/Maestro will no longer support tokens HOT 1
- dotnet add package with CPM installs a different version than what gets restored HOT 3
- NuGetAudit should check PackageDownload
- NUGET_CERT_REVOCATION_MODE not using HTTPS
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 home.