Interpreter–part 4 of n – Deploy
- http://msprogrammer.serviciipeweb.ro/2018/07/16/interpreterpart-1-of-n/ – Idea
- http://msprogrammer.serviciipeweb.ro/2018/07/23/interpreterpart-2-of-n/ – Coding
- http://msprogrammer.serviciipeweb.ro/2018/07/30/interpreterpart-3-of-n/ – Testing
- http://msprogrammer.serviciipeweb.ro/2018/08/06/interpreterpart-4-of-n/ – Deploy
- http://msprogrammer.serviciipeweb.ro/2018/08/13/interpreterpart-5-of-n/ – Documentation
- http://msprogrammer.serviciipeweb.ro/2018/08/20/interpreterpart-6-of-n/ – Ecosystem / usage
After done the testing part, we can deploy the Interpreter . That means uploading to some package sources, as Nuget.org or myget.org. I choose Nuget.org .
For this, first we should package the applicatiuon. We right click the project, select properties, and then package tab.
Enter the details ,. save , then right click the project again and click “Publish” and fisnish.
In the folder “bin\Debug\netcoreapp2.1\publish” you will find the InterpreterDll.1.0.0.nupkg file. This file you will upload to nuget.org. For this, you have to login to nuget.rog and go to https://www.nuget.org/account/Packages
After submitting , you will find the package at https://www.nuget.org/packages/InterpreterDll/ .
From this, you can testit by downloading directly from nuget feed .
First deploy was simple – but we want to do this with a button click.
But we want more – every time a new code is pushed to github -the tests should run automatically and a new interpreter package will be created. For this we can choose VisualStudio.com site , integrate with our github repository and create a build release.
I am going to https://ignatandrei.visualstudio.com/ and create a new project. For this , I will integrate with GitHub and push a new build. Also, in this definition of build have a publish task that allows to publish as an artifacty the .nupkg that next we will put on github / nuget