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

Referencing the alpha versions has caused code to break #552

Closed
5 tasks
StingyJack opened this issue Aug 2, 2023 · 3 comments
Closed
5 tasks

Referencing the alpha versions has caused code to break #552

StingyJack opened this issue Aug 2, 2023 · 3 comments

Comments

@StingyJack
Copy link

IF YOU DON'T ANSWER THIS TEMPLATE - THE BOT WILL AUTOMATICALLY CLOSE YOUR ISSUE!

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

  • [ x] WPF
  • UWP
  • iOS
  • Android
  • .NET Standard
  • .NET Core

Component

What component is this issue occurring in?

Version of Library

unversioned source code

Version of OS(s) listed above with issue

Any/all

Steps to Reproduce

  1. git clone
  2. open solution
  3. build solution

Expected Behavior

It compiles

Actual Behavior

It fails with errors

Some of the Orc packages reference pre-release versions of Cattel MVVM. Those prerelease versions changed the accessibility on CommandContainerBase and that means the handful of classes that inherit from that class are now broken and the project doesn't compile. Forcing the use of a stable release of Cattel.MVVM, fixes this, and I can run the program but unfortunately it does nothing useful. I cant even type a comma in!

It would be nice if the current state of the project were clear in the readme. It gives the impression of a usable program that I just wasted an hour trying to get to work to find out its incomplete.

@GeertvanHorrik
Copy link
Member

You probably used the develop branch, which is the active development branch. Best is to use the master branch which is used for stable releases.

@StingyJack
Copy link
Author

Well I would have liked to have been able to at least try submit a PR to address #551. That dev branch is more than 1000 commits ahead of master, and I dont really want to deal with that kind of distance. Thanks for getting back to me about this though.

@StingyJack
Copy link
Author

FYI - When trying to build the master branch.... I tried commenting out the nuget.config to see if that made a difference, but result was the same. Looks like someone revoked a cert.
image

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

2 participants