WPF: Project doesn't find its own Classes ("tag not found in namespace")
Hi there, I've got a problem that's driving me crazy: c# WPF Custom Controls Project (NET 7), Base Namespace "UserControls". All the controls, styles and Converters existing in the project are in that namespace (I tripple checked, it's the only namespace used). All the controls and Converters are public classes. In the project, there is a Class named "EqualityToBooleanConverter.cs" Additionally, there is a Style file called Button.xaml. I need to use the aforementioned converter here, so I am referencing it like this: <ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:local="clr-namespace:UserControls;assembly=UserControls"> <local:EqualityToBooleanConverter x:Key="ETBConverter" /> Intellisense does find the Namespace "UserControls", in fact, the namespace declaration AND the ressource declaration was done using intellisense. BUT as soon as I compile the project, the following error pops up: MC3074 - type "EqualityToBooleanConverter" does not exist in "clr-namespace:UserControls;assembly=UserControls" I just don't get it, as I said, all the files are in the same project, and they are - as of now - all using the root namespace "UserControls". Everything is fine until I start compiling. What I have tried so far: removing the "assembly"-part of the namespace-declaration changing the compile target from AnyCPU to x86 and back cleaning the solution creating a new solution, and re-adding all the files to it Also noteworthy: The same problem occurs when I try using one of the Usercontrols in that project WITHIN the project itself (like: creating a Window.xaml, defining the local-namespace, and trying to add the control leads to the same error as soon as I compile). I don't know what else could cause this...does anyone have any idea?
How to decouple views from view models using CommunityToolKit.mvvm
I am writing my first MVVM app using CommunityTookit.mvvm. I am using as reference the Micrsoft Learning link https://learn.microsoft.com/en-us/dotnet/communitytoolkit/mvvm/ioc. This link shows the setting of the viewmodel to the view DataContext using the following statement in the view's .cs file: this.DataContext = App.Current.Services.GetService<ContactsViewModel>(); The problem with this as I see it is that this statement couples the view to the view model, in this case ContactsViewModel. This means that in another app the view cannot be used with another viewmodel without modifying the view, i.e. changing ContactsViewModel above to another viewmodel type. This means that the view cannot be stored in a common library that is shared among different apps. There is a C# Corner example with the older MVVM TookKit that solved this problem using a ViewModelLocator class. This project is found https://www.c-sharpcorner.com/article/getting-started-with-mvvm-light-with-wpf/. The solution is to put the following code in the view's XAML file: DataContext="{Binding Main, Source={StaticResource Locator}}" The source object for the binding is found by looking for a ResourceDictionary that is in the scope of the view and which has an entry whose key is "Locator". In app.xaml which by definition is always in scope we have: <Application.Resources> <ResourceDictionary> <vm:ViewModelLocator x:Key="Locator" d:IsDataSource="True" /> </ResourceDictionary> </Application.Resources> The Dictionary element with key "Locator" is an object of type ViewModelLocator. In the ViewModelLocator class there is a Main property that always returns an instance of MainViewModel: public MainViewModel Main { get { return ServiceLocator.Current.GetInstance<MainViewModel>(); } } In our example, the view's DataContext binds to the Main property of the ViewModelLocator object. The value of the Main property is a MainViewModel object and this becomes the DataContext of the view. We can now in a different app re-use the view without changing it. All we have to do in the next app is to create a different ViewModelLocator object that specifies a different viewmodel in its Main property. The view is now completely decoupled from the view model. My question is, how would we de-couple the view from the view model using the CommunityToolkit.Mvvm? Do we also use a ViewModelLocator class? Is there a more elegant way with dependency injection? Another question I have is, suppose we want to use in one app the same view twice with different view models. An example of where we might want to do this is if we had a view that displayed a chart. It is conceivable that we might want to have more than one view model display its data using the same chart view. I cannot see how to do this in either of the above Microsoft or C# Corner examples.
关于Microsoft Defender对VisualBasic.Net编写的软件报毒问题
大家好，我之前使用VS2019写过 VB.net 程序，该程序使用了Winform框架，除了导入了system.data.sqlite之外，其余任何组件都是使用的winform自带的组件，没有使用第三方库，并且仅仅只是一个数据库查询以及创建窗体的功能，将它编译好后，在打开时Microsoft Defender对其报毒（Trojan.xxx.A.xx）了，并且它不是每次打开都会报毒，是偶尔报一次毒，这对我的体验很不好，我无法找到它报毒的原因，请问这应该怎么解决？或者说我在写代码时应该注意什么以避免此问题。期待收到大家的回复，非常感谢
MAUI XAML "in-app toolbar" / "xaml inspector" no longer visible
Sorry for using some made up term but I have no idea what this little menu is called. So I referred to it as "xaml Inspector" I have 2 systems opening the same project, one is 17.3 preview 6 and the other is 17.3.2. On the preview version I can see this menu when I debug my MAUI app in Windows. I cannot see it on the 17.3.2 release, which seems to also be part of a wider debugging issue that I'm experiencing. Any idea how to fix this? Maybe I have changed a setting somewhere but am not aware of what. Thanks in advance!
