You don't need to recompile and run the application for every minor Design/view related changes should be pretty easy to identify and test. There is no replacement for manual testing really. Apart from this you should run the applicationĮvery now and then to manually verify that it behaves as expected. You could write unit tests to test your application and business logic and possibly using a UI automation framework to test the UI part. Well, the designer is certainly not a replacement for manual testing. >The application builds fine, as the program is quite huge already, we do need the design time data, else we would have to compile, run and navigate to the corresponding view each time we do a change, to check if it is correct. Please don't ask several questions in the same thread. Please remember to close your threads by marking helpful posts as answer and then start a new thread if you have a new question. Please refer to the following thread for more information: Make sure that you include a minimal reproducible sample in the bug report. If you think that you have found a bug, you should report it at Connect:
Unfortunately the XAML designer cannot really handle all scenarios anyway and I personally almost never use the designer in Visual Studio at all.Īfter all, every successful WPF developer should know how to do things in XAML markup without using the designer :) If your application works at runtime I wouldn't spend to much time and effort on trying to fix designer issues. Building the application may get rid of certain types of designer errors. Make sure that the application builds and you have no other errors. A 'DynamicResourceExtension' can only be set on a DependencyProperty of a DependencyObject.
XamlParseException: A 'DynamicResourceExtension' cannot be set on the 'Converter' property of type 'Binding'. Some websites suggested using DynamicResource, but that's not going to work, as the designer apparently encounters an exception. In the Converters.xaml are the converters defined. Inside of this Generic.xaml - in the DLL/Assembly - are resourcedictionaries defined. In the xaml files, where the converters are used, is a resourcedictionary defined. The resource ".Converter" could not be resolved.
While trying to use these converters from the DLL, the xaml designer underlines where converters are used. One of these includes converters, styles and similar items. We currently have a couple of DLLs containing logic for different projects.
0 kommentar(er)
