We have a very large WPF application that is currently using .NET framework 4.0 and setup as a x64 application. It uses a variety of 3rd-party DLLs (listed below) and implements a modified MVVM framework. We recently installed Visual Studio 2012 Update 2 and had several security updates installed by our company shortly after. Now, anytime we open or edit an XAML file using the designer, the XDesProc.exe process consumes an entire core (8% CPU on a 12-core desktop) and locks all of Visual Studio.
Our current workaround is to not use the XAML designer but instead open XAML files using the XML editor, which is a major pain. We have discovered that this is the only project affected and that if we comment out merged resource dictionaries in the app.xaml, it sometimes works. Also, computers that have not been restarted since the security updates were applied are not affected and can open files in the designer without any issue. We are currently working with our organization to gather a list of all of the updates that were applied on the day that we noticed the issue.
What we have tried:
- Fresh install - works until security patches are installed
- Restoring back to the day before security patches - works fine with no issues (note: some machines are not able to restore back far enough at this time so this is not a valid fix)
- Uninstalling patches one at a time - does not work
My question:
Have you had an related issues with the XDesProc.exe process and other updates or do you have any guidance as to what we might try to restore functionality to our Visual Studio environments?
Related 3rd-party DLLs:
- GalaSoft MVVM Light
- AvalonDock
- PostSharp
- NHibernate
- Microsoft.Practices.Prism