Consolidates projects and prepares for AZ DevOps #143
Conversation
Changes: - Uses same folder structure as NATS.Client - Strong naming as NATS.Client - Cleans test utils as we do not have config - Fixes some tests that were comparing local against UTC times
These tests interfere with each other. If you run both then TestPublishReconnectDeadlock fails. Cleaning up solves the issue.
This to overcome the issue of NATS not being strong named before that.
This is an issue as we check it for null to determine if closed in other parts of the client.
Removes build status. Will be replaced once in Azure.
|
@ColinSullivan1 When merged to |
| <PackageReference Include="Google.Protobuf" Version="3.10.0" /> | ||
| <PackageReference Include="Google.Protobuf.Tools" Version="3.10.0" PrivateAssets="All" /> | ||
| <PackageReference Include="NATS.Client" Version="0.9.0" /> | ||
| <PackageReference Include="NATS.Client" Version="0.9.1-pre1" /> |
There was a problem hiding this comment.
@ColinSullivan1 Had to update to latest pre-rel of NATS as that one is signed. Or should not STAN.Client be signed?
There was a problem hiding this comment.
This is fine for now - we can get an official release out for core NATS, then release another version of STAN.
| } | ||
|
|
||
| [Fact] | ||
| [Fact(Skip = "HANGS SOMETIMES")] |
There was a problem hiding this comment.
@ColinSullivan1 Do you have any ideas why this one is hanging sometimes?
There was a problem hiding this comment.
I don't, it works well locally, but seems to hang up in AppVeyor.
Changes:
pingTimerTestPublishReconnectDeadlock)