Skip to content

Changes to improve build and test and removed need for nuspec (which incorrectly references Newtonsoft now) - #58

Open
Colin Dekker (colindekker) wants to merge 3 commits into
plivo:masterfrom
colindekker:master
Open

Colin Dekker (colindekker) wants to merge 3 commits into
plivo:masterfrom
colindekker:master

Conversation

@colindekker

Copy link
Copy Markdown

When using the current Plivo NuGet package, the consuming projects get a build warning due to the way the dependency in the nuspec was annotated.
To circumvent this it's possible to have the csproj be the nuspec as csproj files are now fully part of the build and development process (either set manually or using the project proeprties in Visual Studio).

Then I looked at the two test projects and removed the old, NUnit one because it's not needed. I multi-targetted the .NET Core test project to netcoreapp1.1 and net461 then ran the command line dotnet test which will run every available framework.

Cleaned up some files, moved and renamed the .NET Core Test projet to be just Plivo.Test as it replaces the old NUnit project

…Core XUnit Test project. Tests pass for both frameworks using dotnet test Pliivo.Test.csproj
…notes to Plivo project and setting create package on build to true
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant