CommunityToolkit 8.2.2 with Wpf .Net framework 4.8.1 gets error The name '' does not exist in the current context

Question

Hi,

I am working with WPF .Net framework 4.8.1 using CommunityToolkit 8.2.2. I've already set the LangVersion to 8.0, and migrated the package.config.

In my MainWindowViewModel, there is a ObservableProperty string _myName, the Source Generator already generated the public string MyName. However, the build keeps building failed with the error The name '' does not exist in the current context.

Here is my ViewModel

Here is the Code generator

Here is my MainWindows.xaml

Here is the error:

Here is the Solution Explorer

Could you tell me what I am missing here to make the ObservableProperty works?

Thank you,

Dung Huynh.

Answer 1

Hi,@Dung Huynh. I found a workaround.
You could try creating a .NET Standard 2.0 library, flip on C# 10, and moving your ViewModel there to see if it works.

For more details, you can refer to the chat here.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi,@Dung Huynh. Welcome to Microsoft Q&A. I reproduce your problem in Microsoft Visual Studio Community 2022 Version 17.10.5 and got the following errors and warnings. I've already set the LangVersion to 8.0.

But it has been tested to work in .net 8.

When i migrated the package.config to PackageReference ,the warning disapper. But still can't run.

According to the documentation Introduction to the MVVM Toolkit , it does not support .NET Framework.

You could migrate your application to .NET 6 or 8 Upgrade a WPF App to .NET 6 with the .NET Upgrade Assistant

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.