Final release candidate 1.0.1 is pushed, .NET Core version, nuget package pushed

[rivantsov]

Hi everybody
Official release candidate is in github and nuget as version 1.0.1
Silverlight is gone, only .NET 4.0 and .NET Standard 2.0 versions; Full .NET v 4.6.x+ apps work perfectly with .NET Standard 2.0

Some reorg and cleanup
Have a look; unless I hear some screaming, I will push this as 1.1 Official release for .NETStandard 2.0 tomorrow

Roman

[rivantsov]

If you use Irony in you app(s), pls pls try the current version 1.0.1, see if something broken

[yallie]

Hi Roman, thanks for the update!
Looks like appveyor doesn't work with the auto-detected configuration, so I restored the config file.

[rivantsov]

hmm.. do we need apveyor? I looked it up, looks like a commercial product, what it does that cannot be done with VS? I just tried to keep these extras out and trim down to minimal set of 'dependencies'. I added scripts (batch files) and .nuspec files for packing nuget packages, and that seems enough

[yallie]

Appveyor is not really a dependency, it's a CI service, free for open-source projects.
It's a widely used CI provider for github (along with Travis for linux-based projects).
And it's a handy tool to validate the incoming pull requests.

[rivantsov]

all right, let it stay, but then pls add some instructions on top, how to use it with the service (which would justify its presence) for a guy like me who never worked with this

[yallie]

There is no need to work with it at all.
Each commit to the Github repository automatically triggers a new build.
When the build is finished, Github displays build status in the commit log, either ✔ of ❌:

Badges on top of the readme file display the outcome of the latest build:

Each time someone sends a pull request, it also triggers a CI build.
If the build fails, Github warns about it, so it's trivial to see if a PR breaks anything.
That's all, basically.

[rivantsov]

Ok then, thanks for the explanation