stigzler Comments - Answer Overflow

Topics

stigzler

•Created by stigzler on 10/22/2024 in #help

Pack URIs do my bloody head in - help needed

.UriSource = New Uri("pack://application:,,,/WpfWorkspace;component/ShaderEffects/GrayscaleEffect.ps")

8 replies

•Created by stigzler on 10/22/2024 in #help

Pack URIs do my bloody head in - help needed

Nemmind - figured it - it was because it was in a referneced assembly:

8 replies

•Created by stigzler on 10/22/2024 in #help

Pack URIs do my bloody head in - help needed

System.TypeInitializationException HResult=0x80131534 Message=The type initializer for 'WpfWorkspace.GrayscaleEffect' threw an exception. Source=WpfWorkspace This exception was originally thrown at this call stack: [External Code] WpfWorkspace.GrayscaleEffect.New() in GrayscaleEffect.vb Inner Exception 1: NotSupportedException: The URI prefix is not recognized.

8 replies

•Created by stigzler on 10/22/2024 in #help

Pack URIs do my bloody head in - help needed

Error:

8 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

thanks for the constructive point, fred

22 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

With respect, Sergio, it's the interface between the toolkit and VS environment/stack, which is a core aim of the toolkit - thus it is related to the toolkit code. You also work for MS, so more broadly speaking the answer comes somewhere between you or your colleagues at VS. I do really respect what you've created here, but am so frustrated that a team as big and as well resourced as MS don't help their users over what should be core functionality. I also do think it's really short sighted of MS as VS extension developers essentially attract/maintain users and thus revenue. I updated the Issue on GItHub with a pointer to the SO post which has the specific repo branch demonstrating the problem. I think the biggest issue that caused this response from me was just the total lack of any communication on the GH issue. Great code is awesome, but communication and respect for persons is fundamental. I'm sorry if this came across as personal - that wasn't my intention and maybe I was a bit cross, but it was more your role as a MS employee. I have split it out into its own project (which has brought its own problems) so will just battle on with that. I also know your to-do list is likely very long (?) but maybe consider having a look at the toolkit <> vsix interface at some stage (or your colleagues)?

22 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

@ref *&Sergio I'm really sad that you or any members of your team aren't helping with this issue. It really is very short sighted of MS not to support extension developers. Poor show. 👎👎👎 - the dicky performance of your code has brought my dev to a standstill.

22 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

(weird thing is [Relay Command] works fine)

22 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

Just disabled package source mapping and re-installed the lib. Still bugs out on [Observable Property] - will refactor to separate lib tomorrow. Just for clarity - is this a known difficulty with Ext Dev in VS?

22 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

hey - sorry missed this. Is packages.config linked with nuget source mapping? I did turn this on via VS options, but can't find any packages.config file in my solution folder.

22 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

@ref *&Sergio - hey sorry to ping you on this - but do you have any ideas? I've scoured the internet and am totally stuck on this issue. Really want to use this library, but impossible to do so atm. A basic starting point would be: can you use this with Framework 4.8 and can you use it in VS extension development or is there something about the dev environment that breaks mvvm toolkit?

22 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

Hey - no probs and thanks for checking in. It may be clearer on the StackOverflow post here: https://stackoverflow.com/questions/78619310/build-errors-when-using-communitytoolkit-mvvm-with-visual-studio-extensions/78621701#78621701 I also rose an issue against the repo here: https://github.com/CommunityToolkit/dotnet/issues/889

22 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

Anyone? Still stuck on this. The hype was great, but sadly its implementation isn't a great expreince so far!

22 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

🤷

22 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

No description

22 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

To add (as ran out of words in OP): If I set _exceptionMessageText to a value, it displays correcly in the xmal binding (Text="{Binding ExceptionMessageText}"). However, if I try to assign ExceptionMessageText a value in the ViewModel itself, I get the does not exist in the current context error again for this property.

22 replies

•Created by stigzler on 6/12/2024 in #help

Community.Toolkit.MVVM Error on [ObservableProperty]: The name 'x' does not exist in current context

NArrowed it down a little and updated OP

22 replies

•Created by stigzler on 5/26/2024 in #help

Filtering an Observable Collection in WPF MVVM via ICollectionView

thanks for the answer. Sadly, it didn't work - same problem 😦

3 replies

•Created by stigzler on 5/20/2024 in #help

✅ Force Binding update in ViewModel where UpdateSourceTrigger==LostFocus

Caved in and did it in the code behind:

private void SaveBT_Click(object sender, RoutedEventArgs e)
{
    BindingExpression expr = CodeEC.GetBindingExpression(EditControl.TextProperty);
    expr.UpdateSource();
}

private void SaveBT_Click(object sender, RoutedEventArgs e)
{
    BindingExpression expr = CodeEC.GetBindingExpression(EditControl.TextProperty);
    expr.UpdateSource();
}

Unless anyone can tell me how to do it properly (if 'properly' even is doing eveything in the ViewModel?)

2 replies

•Created by stigzler on 5/19/2024 in #help

✅ How to use IRelayCommand in CommunityToolkit.Mvvm with parameters?

ah! you may have apoint there

77 replies