Microsoft.Azure.Cosmos package ref folder lacks XML doc and is incompatible with reflection
See original GitHub issueDescribe the bug
- Microsoft.Azure.Cosmos.Client.xml exists only in the
lib
folder, but not inref
. This means there is absolutely no documentation shown inside VS. - Microsoft.Azure.Cosmos.Client.dll inside
ref
is not an actual ref assembly (it’s just a copy of the same assembly from the lib folder). This means that it contains unresolvable references to other assemblies (e.g.,Microsoft.Azure.Cosmos.Core.dll
) and is unusable by reflecation based tools (e.g., OrleansCodeGenerator).
Expected behavior
ref
folder contains an actual ref assembly (with no code and no invalid references to other assemblies) and also contains Microsoft.Azure.Cosmos.Client.xml
.
Environment summary SDK Version: 3.6.0
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Conflict resolution types and resolution policies in Azure ...
This article describes the conflict categories and conflict resolution policies in Azure Cosmos DB.
Read more >Package List
Package List . This is a list of things you can install using Spack. It is automatically generated based on the packages...
Read more >Strange issue with System.Net.Http 4.2.0.0 not found
I have a simple Class Library Project (Full .NET Framework, 4.6.1) with a wrapper class for functionality around Cosmos DB. Therefore I have ......
Read more >Introduction to Azure Cosmos DB | Microsoft Docs
Azure Cosmos DB is Microsoft's globally distributed multi-model database service. You can quickly create and query document, key/value, and graph databases, ...
Read more >Use the ColdFusion administrator
Task. Description. Establish database connections. ColdFusion applications require data source connections to query and write to databases.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Linked the PR which removed the ref folder. +1 to not bring back ref folders.
If we’re not actually producing a ref assembly, we should be able to just eliminate the entire ref folder, and NuGet will add references to the assemblies in the lib folder.