Cool project 👍

Very cool. Let us hope this will encourage more porting!

@U03AU2X8TD5 Thanks! You just reduced my list of ports blocking my project by one, and I will be using it as soon as I figure out how to incorporate it! I don't suppose you published it to nuget yet?

Very happy to hear that, Bob! 😃 I should add publishing as a TODO! Not even started looking into that yet.

Do you know of any good guide on the topic?

I mean, I can build it locally and then simply refer to it. I have my cljr.exe able to pre-load assemblies referred to via :local/root on the harddrive.

sounds like a good plan in the meantime 👍

Neart-term on cljr's list of todo's is using the NuGet API but I looked at it and recoiled in horror at the apparent complexity of it, so kicked that can down the road a bit as at least I'm functional with local assemblies. I will probably integrate :git/url before I deal with :nuget/version. lol.

Hah! I can imagine. Is the plan to have it work with Maven/Clojars too?

Re publishing on nuget: in the docs folder in clojure-clr there is a guide to publishing a lib on nuget. This is something that could be automated at some point.

Nice! I think I’ve seen that in the past but forgotten about it. Thanks David 👍

NuGet first. Clojars and Maven are definite "maybes" at this point. Clojars will make sense for libraries that are intentionally portable, whereas NuGet will make sense for libraries that are strictly bound to .NET. I imagine once my first pass using deps.edn with clr-specific keys is done, there will be some thoughtful feedback from the deps/cli folks about how we might more thoughtfully integrate these worlds. Right now I have :clr-deps, :clr-aliases and :nuget/repos as toplevel keys and they do no harm to normal clj deps projects (cuz they are ignored by them). In theory clj could probably handle all of the platforms - would just need to interact with NuGet via it's http interface. But then .net devs would be required to have java on their machines (which many probably do anyway but I hesitate to make it a requirement per se). Plus there are just certain realities about how the CLR runs that is sufficiently different from how JVM runs that keeping them separate makes more intuitive sense to me, even if we merge the deps.edn spec around cross platform support.

I think you should publish to NuGet and Clojars for a Clojure/ClojureCLR library

@U03AU2X8TD5 I've published ClojureCLR code to NuGet before, I'm rusty on the process but willing to help

@U45FQSBF1 the guide in the readme didn't work for me when I tried to use it months ago but I was able to tweak it to work for my project

Do you remember what the problem was? (This is generally the routine I follow.)

No but I could probably recreate it at some point

I’ll follow it when I publish, and will report if I get stuck somewhere