3

I open a XAML file. Start editing a control. I want to type in the following simple property setting:

  Background="Transparent"

That's it. But after typing at most 3 characters, Visual Studio completely locks up never to come back. (I just left it running all weekend and it was still locked up)

If I paste the line into the text editor there is no lockup. But typing it locks up Visual Studio every time.

Here are the things I have tried to fix it. None of them have worked (Note: I always have the XAML designer disabled, even before this happened so I did not need to disable it)

  • I've tried individually disabling extensions, particularly Resharper and Visual Assist.

  • I have tried manually disabling every single extension that I have installed.

  • I've tried disabling all intellisense options that can find in Tools >> Options.

  • I've tried deleting the .vs subfolder where my solution file lives

  • I've tried deleting the component model cache, both manually from the folder where it lives and using Mads Kristiansen's "Clear MEF Component Cache" extension

  • I've tried starting Visual Studio from the command line with the /safemode switch

  • I've tried starting Visual Studio from the command line with the /resetsettings switch

  • I've tried using the Visual Studio installer to repair the installation

  • I was told to "delete the .suo file" but I don't have one because i use the new .SLNX solution file format.

  • I've tried (on a suggestion from .AI) to go into the .csproj file and add the following lines (which did not help)

<DisableXamlTypeBackgroundCompilation>true</DisableXamlTypeBackgroundCompilation> <XamlDebuggingInformation>False</XamlDebuggingInformation>

Does anyone have any idea what will fix this?

Improve this question
2
  • Did you try to reinstall everything? Does it depend on the user data? You can find it out by creating a new user account and trying your project with it. Anyway, if the user data is also a reason, you have to clean it up after you save your important data. Commented Jun 8 at 23:44
  • After 2 days of experimentation, I appear to have located the cause of the issue. One single check-in that merely updated our Telerik UI for WPF NuGet packages to the latest version seems to have somehow caused this. If I change all the projects to go back to the older packages, the problem goes away. The strange thing is that the app runs just fine, regardless. The packages/assemblies are downloaded from the Telerik NuGet Server and run with the app. But they trigger this lockup. So for now, we stick with the older Telerik Assemblies Commented Jun 10 at 15:29

1 Answer 1

Reset to default
0

The problem seems to be the Telerik.UI.for.Wpf.AllControls.Xaml (v2026.2.520) package. I installed this because it seems to be the latest Telerik release but was getting the same error.

Installing Telerik.UI.for.Wpf.80.Xaml fixed the problem for my .Net Core WPF project.

Improve this answer
New contributor
Neil.R is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

Draft saved
Draft discarded

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.