canton7
canton7
PostsComments
CC#
Created by MCUnderground on 5/7/2025 in #help
WPF Icon
AFAIK you need: * In the csproj, <ApplicationIcon>MyIcon.ico</ApplicationIcon> * In your <Window>: Icon="MyIcon.png"
2 replies
CC#
Created by nevemlaci on 5/6/2025 in #help
ObservableProperty isn't updating on the UI
So the binding did fail?
32 replies
CC#
Created by nevemlaci on 5/6/2025 in #help
ObservableProperty isn't updating on the UI
Ah, that's an important bit of info, yeah
32 replies
CC#
Created by nevemlaci on 5/6/2025 in #help
ObservableProperty isn't updating on the UI
Ah, no idea then I'm afraid. I didn't even spot it was Avalonia, not WPF, so no idea how it logs binding errors
32 replies
CC#
Created by nevemlaci on 5/6/2025 in #help
ObservableProperty isn't updating on the UI
(I mean when you run the app and load that view -- binding failures pop up in the Output window)
32 replies
CC#
Created by nevemlaci on 5/6/2025 in #help
ObservableProperty isn't updating on the UI
Any errors in the Output window?
32 replies
CC#
Created by AK on 5/6/2025 in #help
✅ How do i get .NET 4.x on VS 2022?
I'd follow that screenshot, but then open up the csproj (just double-click on it) and change the <TargetFramework> to net45 or whatever
40 replies
CC#
Created by AK on 5/6/2025 in #help
✅ How do i get .NET 4.x on VS 2022?
Will that give you an old-style csproj?
40 replies
CC#
Created by LastExceed on 5/6/2025 in #help
consolidating my understanding of `async`/`await` in C# and Rust
I.e. this has always brought down the process: 
async void Foo() => throw new Exception();
Foo();
async void Foo() => throw new Exception();
Foo();
This used to bring down the process, but that was changed in .NET 4.5: 
async Task FooAsync() => throw new Exception();
_ = FooAsync();
async Task FooAsync() => throw new Exception();
_ = FooAsync();
31 replies
CC#
Created by LastExceed on 5/6/2025 in #help
consolidating my understanding of `async`/`await` in C# and Rust
I'm 98% sure that's wrong
31 replies
CC#
Created by LastExceed on 5/6/2025 in #help
consolidating my understanding of `async`/`await` in C# and Rust
That's whether an exception stored in a Task but which is never looked at brings down the app
31 replies
CC#
Created by LastExceed on 5/6/2025 in #help
consolidating my understanding of `async`/`await` in C# and Rust
That's nothing to do with whether an unhandled exception on a threadpool thread brings down the app
31 replies
CC#
Created by LastExceed on 5/6/2025 in #help
consolidating my understanding of `async`/`await` in C# and Rust
This business: https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/throwunobservedtaskexceptions-element#remarks
31 replies
CC#
Created by LastExceed on 5/6/2025 in #help
consolidating my understanding of `async`/`await` in C# and Rust
That was whether an unobserved exception in a Task causes a problem, right?
31 replies
CC#
Created by LastExceed on 5/6/2025 in #help
consolidating my understanding of `async`/`await` in C# and Rust
Other languages which started out with async/await have a primitive which is just a "pending work" / "I'm done" signal
31 replies
CC#
Created by LastExceed on 5/6/2025 in #help
consolidating my understanding of `async`/`await` in C# and Rust
Yeah pretty much
31 replies
CC#
Created by LastExceed on 5/6/2025 in #help
consolidating my understanding of `async`/`await` in C# and Rust
Yeah I'm not sure exactly what the process for terminating because of an uncaught threadpool exception is
31 replies
CC#
Created by LastExceed on 5/6/2025 in #help
consolidating my understanding of `async`/`await` in C# and Rust
Why should something which is just a signal that an operation has completed know how to start work on a thread?
31 replies
CC#
Created by LastExceed on 5/6/2025 in #help
consolidating my understanding of `async`/`await` in C# and Rust
Not sure: I don't think it's had time to die yet? If you replace the Task.Delay(2000 with a Console.ReadLine, you'll see the process terminate
31 replies
CC#
Created by LastExceed on 5/6/2025 in #help
consolidating my understanding of `async`/`await` in C# and Rust
Task generalises over many types of things now, but it also has behaviour which is very much tied to its old fork/join threading model history. E.g. if Task were just a generalisation over an operation which might not have completed yet, why does new Task(() => ...).Start() run something on the thread pool?
31 replies