Update ProjectTracker for CSLA 8 #3689
Unanswered
rockfordlhotka
asked this question in
General
Replies: 2 comments 2 replies
-
I am dying laughing. I and the world's weirdest celebrity now. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@rockfordlhotka public static readonly PropertyInfo<string> NameProperty =
RegisterProperty<string>(nameof(Name));
[Display(Name = "Project name")]
[Required]
[StringLength(50)]
public string Name
{
get { return GetProperty(NameProperty); }
set { SetProperty(NameProperty, value); }
} This property is decorated with some nifty attributes, do you use code generation? Kind regards |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have failed to update ProjectTracker for some years now - shame on me!
I started to go down this road again - thinking I'd release CSLA 8 and then do ProjectTracker. Thankfully I brought this idea up on the Discord server, and was called out on my b.s.
So instead, I've decided to update ProjectTracker, but shrink the scope to something more realistic - which is to have only one UI: Blazor.
I'll add other UIs over time - but the big thing is to get the business and DAL layers updated and working with modern CSLA 8, and to have some UI to show how it works, and Blazor is my default UI tech for nearly everything at the moment.
So, here's the PR where I'm doing the work: #3688
Today I removed all the UI projects, updated the app server to .NET 8, and got the business library to compile. I'm sure it isn't correct, but it now compiles. So I have a reasonable start point on which to build.
And yes, @joshhanson314, that ban hammer is still floating out there!! 😀
Beta Was this translation helpful? Give feedback.
All reactions