Skip to content

Investigate why Microsoft.Azure.Cosmos.Direct reference is needed #22231

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
smitpatel opened this issue Aug 26, 2020 · 9 comments
Open

Investigate why Microsoft.Azure.Cosmos.Direct reference is needed #22231

smitpatel opened this issue Aug 26, 2020 · 9 comments

Comments

@smitpatel
Copy link
Contributor

CSC : error CS0012: The type 'PartitionKeyInternal' is defined in an assembly that is not referenced. You must add a reference to assembly 'Microsoft.Azure.Cosmos.Direct, Version=3.11.4.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. [D:\code\efcore\src\EFCore.Cosmos\EFCore.Cosmos.csproj]

We don't use the type directly. The package is not supposed to be referenced directly. Though removing CosmosClient and dependent files from codebase make the error go away.

@ajcvickers
Copy link
Contributor

@dotnet/efteam @Pilchie I'm not going to get to this before vacation. It is something we need to follow up on with other teams since it appeared when we updated to the preview 8 SDK. It's not clear whether Cosmos, NuGet, the SDK, or something else is causing this. We're working around it by referencing the package directly, but this not the correct thing to do.

@smitpatel
Copy link
Contributor Author

@JeremyLikness JeremyLikness added this to the 5.0.0 milestone Sep 4, 2020
@smitpatel smitpatel self-assigned this Sep 4, 2020
@ajcvickers ajcvickers assigned bricelam and unassigned smitpatel Sep 8, 2020
bricelam added a commit to bricelam/efcore that referenced this issue Sep 8, 2020
@bricelam bricelam removed this from the 5.0.0 milestone Sep 8, 2020
ghost pushed a commit that referenced this issue Sep 8, 2020
@ajcvickers ajcvickers added this to the Backlog milestone Sep 11, 2020
@jongio
Copy link

jongio commented Oct 22, 2020

I'm seeing this in SDK Version: 5.0.100-rc.2.20479.15

Added this to csproj
<PackageReference Include="Microsoft.Azure.Cosmos.Direct" Version="3.4.1.0" />

azsdke2e

@MooVC
Copy link

MooVC commented Nov 12, 2020

This issue has recently cropped up for me on a project targeting v3.14.0.

@DonFrazier
Copy link

DonFrazier commented Nov 12, 2020

Updated to 16.8.1 and now getting this with 0 changes. Super disappointed to update VS and now I have to investigate what you guys broke before I can do anything. I'm running the community free edition.

Adding the Cosmos.Direct package "fixes" the problem but the package comment itself instructs me not to reference it directly since it's for internal use only.

@MattMinke
Copy link

I have the same problem today after having upgraded to VS 16.8.0.

it looks like Microsoft.Azure.Cosmos 3.15.0 will make the problem go away.

@bbsdddougla
Copy link

Can confirm that 3.15.0 made this problem go away.

Interestingly, I didn't see the issue until I opened the solution in VS. (Had been working in another IDE)

@hari-hlubovac-carvana
Copy link

I'm not able to find the source for the Microsoft.Azure.Cosmos.Direct library. The project-website link on its nuget webpage points to Microsoft.Azure.Cosmos repo. Anyone knows? Thanks.

@ajcvickers
Copy link
Contributor

@hari-hlubovac-carvana Probably best to ask on the Cosmos repo.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests