Replies: 5 comments
-
I really should push that sometime to GitHub packages or somewhere... But anyway no changes just uhm compiled up to date version of CWTools. Existing nuget is not really up to date. |
Beta Was this translation helpful? Give feedback.
-
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Beta Was this translation helpful? Give feedback.
-
there's also some versioning issue with FSharp.Core, I had to include FSharp.Core 4.7.0 as a dependency to IronyModManager.Parser to make it build |
Beta Was this translation helpful? Give feedback.
-
I use a local nuget server as well for nugets (makes maintaining consistent nuget versioning easier for me). So it's probably related to that. |
Beta Was this translation helpful? Give feedback.
-
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Beta Was this translation helpful? Give feedback.
-
Went to spin up a clone of the code to take a look if there was anything I could potentially help out with (can't hurt right) and your dependency appears to be pointing to a local spin off of CWTools rather than the main one, so nuget can't find it to pull down.
Wondering if there are any changes present there that would be necessary to run or if it's safe to just redirect that to the public CWTools package.
Beta Was this translation helpful? Give feedback.
All reactions