Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Nuget Package #6

Open
chuck-flowers opened this issue May 3, 2018 · 15 comments
Open

Update Nuget Package #6

chuck-flowers opened this issue May 3, 2018 · 15 comments

Comments

@chuck-flowers
Copy link

I'm interested in trying out Irony for a project idea I've had but it appears the 'Irony' nuget package only targets .NET Framework 4.0. I'm wanting to use it for a .NET Standard/Core project. From the issue tracker here it seems like you've added .NET Standard support but the nuget package doesn't seem to reflect that.

Does the package need to be updated or am I missing something?

@yallie
Copy link
Member

yallie commented May 3, 2018

Hi Chuck,

you're right, the Nuget package is out of date.
I don't have access to the package, perhaps Roman does.
For now, you can just build Irony code from sources.

@chuck-flowers
Copy link
Author

Alright thanks.

@igitur
Copy link
Member

igitur commented May 7, 2018

On that subject, is Roman involved with this fork?

@yallie
Copy link
Member

yallie commented May 7, 2018

Roman is the administrator of the IronyProject organization.
However I'm not sure if he has time to actively contribute to Irony.

@igitur
Copy link
Member

igitur commented May 7, 2018

Ok, let me rephrase, does this fork have his 'blessing'? If so, let's get @daxnet involved with this fork rather.

@igitur
Copy link
Member

igitur commented May 7, 2018

And what's the chances of getting control of the NuGet package? cc @rivantsov ?

@rivantsov
Copy link
Contributor

Hi guys
this is Roman. I just granted control over nuget packages to Alexey (yallie), so from now on he is in charge. Whatever he does, he 'has my blessing'.
Sorry, no time to be involved, too much other stuff going on. There is a possibility I might come back, I am planning GraphQL server implementation (on top of VITA (https://github.com/rivantsov/vita), and it turns out search (predicate language) is not part of 'standard', so it's up to implementers to figure it out

@igitur
Copy link
Member

igitur commented May 7, 2018

Thanks, Roman.

@igitur
Copy link
Member

igitur commented May 8, 2018

@yallie Would you mind downloading https://ci.appveyor.com/api/buildjobs/152pwkrfd38p08xq/artifacts/Irony%2Fbin%2FRelease%2FIrony.1.0.9.nupkg , adjusting its internal version number and pushing it to NuGet as a beta version. I suggest using version number 1.0.0-beta1 .

@yallie
Copy link
Member

yallie commented May 8, 2018

Looks like the package currently includes the GrammarExplorer tool.
Perhaps it should better be published as a separate nuget, say, Irony.GrammarExplorer.
I guess I'm publishing the package as is for now, just Irony.dll.

@igitur @wasabii Any thoughts?

@igitur
Copy link
Member

igitur commented May 8, 2018

Definitely agree that the tools should be published separately. I'll add the CI .nupkg build for that later.

@musukvl
Copy link

musukvl commented Jun 20, 2018

I don't see Irony.Interpreter beta in nuget latest I see is 0.9.1.
Where can I get Irony.Interpreter for my .net core project?

@yallie
Copy link
Member

yallie commented Jun 21, 2018

@wasabii
Copy link

wasabii commented Jun 28, 2018

Why hello there. Looks like everybody has everything handled? Heh.

Yes. The tools should be split out. The original package was a quick effort on my part. I didn't even get it upstream, I don't think. Mercurial. Ugh.

@yallie
Copy link
Member

yallie commented Jun 28, 2018

Hello @wasabii,

The tools should be split out.

Yes, that's on the todo-list.

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

No branches or pull requests

6 participants