Empty top-level Timestamp namespace appears in 1.2.2 causing CS0118 errors when a Timestamp type already exists in used namespace

Probably related to #170 and/or #171. With LinqKit.Core 1.2.2, the assembly includes a Timestamp namespace with no public types in it. This raises compiler error CS0118 whenever using any type also named Timestamp, whether that type is defined within the project depending on LinqKit.Core or defined in another assembly which the project also depends upon.

This problem does not exist with LinqKit.Core 1.2.0.

Only solution for this is to copy the source code/project from https://github.com/SimonCropp/Timestamp into this project. And rename Timestamp class to LinqKitTimeStamp.

also this warning:

2>C:\Users\***\AppData\Local\Temp\Timestamp\Timestamp_LinqKit.Microsoft.EntityFrameworkCore7_ykzt5wi3.pyh.cs(4,12,4,21): warning CS0436: The type 'TimestampAttribute' in 'C:\Users\***\AppData\Local\Temp\Timestamp\Timestamp_LinqKit.Microsoft.EntityFrameworkCore7_ykzt5wi3.pyh.cs' conflicts with the imported type 'TimestampAttribute' in 'LinqKit.Core, Version=1.2.4.0, Culture=neutral, PublicKeyToken=bc217f8844052a91'. Using the type defined in 'C:\Users\***\AppData\Local\Temp\Timestamp\Timestamp_LinqKit.Microsoft.EntityFrameworkCore7_ykzt5wi3.pyh.cs'.

Navigation Menu

Repository navigation

Empty top-level Timestamp namespace appears in 1.2.2 causing CS0118 errors when a Timestamp type already exists in used namespace #175

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Empty top-level Timestamp namespace appears in 1.2.2 causing CS0118 errors when a Timestamp type already exists in used namespace #175

Description

Activity

StefH commented on Jun 14, 2022

StefH commented on Mar 18, 2023

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions