Skip to content
This repository has been archived by the owner on Jun 12, 2020. It is now read-only.

port2core 🎉 #65

Merged
merged 2 commits into from
Jan 29, 2017
Merged

port2core 🎉 #65

merged 2 commits into from
Jan 29, 2017

Conversation

TerribleDev
Copy link
Contributor

@TerribleDev TerribleDev commented Nov 27, 2016

Port the main project to core. This still supports .net 3.5!!!

Convert unit tests to project.json format but maintain the same version of nunit/rinomocks (so obv the unit tests are still full framework bound).

also update appveyor accordingly, and set the proper package options in the project.json file since nuspec's dont really exist with project.json.

The one wildcard is I got rid of the Configuration project, and I'm not too sure what requires it, since I was able to compile without it.

if the configuration project is needed and has to be in the net35 nuget package just let me know.

@TerribleDev TerribleDev force-pushed the port2core branch 2 times, most recently from 862a906 to 34a24e4 Compare November 27, 2016 05:20
@TerribleDev
Copy link
Contributor Author

I'm assuming this makes #56 obsolete sorry :(

@TerribleDev
Copy link
Contributor Author

btw I tried to make the changes minimal. We can add async overloads and what not later. One major change at a time!

@TerribleDev
Copy link
Contributor Author

So I just realized the unit tests didn't compile because of the missing Configuration project. I see its 1 file that has an obsolete on it. Should we just kill it? For now I'll comment out the broken test file

@TerribleDev
Copy link
Contributor Author

Copy link
Collaborator

@DarrellMozingo DarrellMozingo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Tommy, mighty generous of you to do the PR!

Would you mind deleting the old IStopwatch.ElapsedMilliseconds() method which is causing some warnings on the build while you're in there? Another long ago obsoleted thing.

https://ci.appveyor.com/project/DarrellMozingo/statsd-csharp-client

Also how does the nuget package get generated w/the new core build system? Where does the information from the nuspec go (ie package name, description, etc)?

Thanks again!

@@ -38,19 +38,20 @@ public void TearDownUdpListener()
// Stop listening for client requests.
tcpListener.Stop();
}
//this test requires a listener for a tcp socket...is it really a unit test?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope - it's more integration. To be fair it never did say it was a unit test ;) We just lumped them all together.

{
Assert.That(Naming.CurrentEnvironment,Is.EqualTo("environment"));
}
//namespace Tests
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was actually planning to remove this in a future version as it's been Obsolete for a while - seems as good a time as any if you wouldn't mind just deleting the tests too.

@TerribleDev
Copy link
Contributor Author

You place the nuspec info in the peoject.json file. I just realized I filled out the wrong file. So I will have to fix that, but it looks like this. https://github.com/Pereingo/statsd-csharp-client/pull/65/files#diff-30e4c60ec7fca7af35cd910663eb7df8R4

@TerribleDev
Copy link
Contributor Author

You run dotnet pack path/to/project.json and that project gets placed in the nuget package.

@DarrellMozingo
Copy link
Collaborator

Ah, cool. So for in the appveyor.yml can we just do:

after_build:
  dotnet pack src\StatsdClient --output .

And we'll get the same artefact output, right?

@TerribleDev
Copy link
Contributor Author

@DarrellMozingo isn't that what I am already doing?

@DarrellMozingo
Copy link
Collaborator

Oh yea, I'm blind :P Can you add the --output . or change the artefact path so they get picked up (looks like they default to the bin folder)?

@TerribleDev
Copy link
Contributor Author

So I'm really sick with the flu right now. I'll have to come back to this next week when I'm feeling better.

@DarrellMozingo
Copy link
Collaborator

No worries mate, hope you feel better.

@dkhanaferov
Copy link
Contributor

Will this make it out some time soon? We'd really like to be able to use this library in out new .net core apps.

@TerribleDev
Copy link
Contributor Author

@dkhanaferov
Oh sorry so I was super sick in november, and december..was well the holidays...and then forgot I had this on my plate

I'll make this happen very soon-ish.

@TerribleDev
Copy link
Contributor Author

@DarrellMozingo ....done

@DarrellMozingo DarrellMozingo merged commit b88dedd into Pereingo:master Jan 29, 2017
@DarrellMozingo
Copy link
Collaborator

Thanks again @TerribleDev for the PR

@TerribleDev TerribleDev deleted the port2core branch January 29, 2017 16:20
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants