But in many cases, it’s just candy tooling for the XAML developer. In some cases, Blend for Visual Studio 2013 returned some of the features removed in Blend for Visual Studio 2012. Who better to walk through, not the new features of Blend, but all the core features of Blend – and the new features, too.
November 2013, immediately after the release of Visual Studio 2013, I sat down for an all-day session with Unni Ravindranathan, the Senior Program Manager for Blend.
#VISUAL STUDIO ULTIMATE 2013 WITH BLEND FOR FREE#
The issue caused by CodeLens is an extremely frustrating one and it will only be addressed in Visual Studio 2015.Īfter a few days working with Visual Studio 2013 with CodeLens turned off, I have not had a single issue with it locking up my laptop.Jerry Nixon Work - The most Comprehensive Blend for Visual Studio training you will ever receive – for Free you’re welcome! I hope that this will help someone somewhere in the world. I love the functionality that CodeLens provided me, but if I have to choose between a freezing laptop every time I debug a web app and the minor inconvenience of not having CodeLens, the choice is obvious. If you are experiencing the same issues, switch off CodeLens (Tools -> Options -> Text Editor -> All Languages -> CodeLens). This process my dear friends is CodeLens, and this particular issue seems to present itself when there are many projects in your Visual Studio solution. I Googled it and stumbled on this article. This process was called .RemoteContainer.dll (32bit). I managed to scroll down the running processes and noticed a particular process hogging almost 500 MB RAM. I noticed though that my laptop was still strangely unresponsive. The resolutionĭuring another freeze this afternoon, I managed to kill Visual Studio and the browser used for debugging. My i7 Dell laptop with 8 GB RAM was now dead. The Memory utilization in task manager would report 99% utilization and the CPU utilization wasn’t doing any better either. Outlook, Skype, Toggl and even the Task manager itself. One after the other, all my open apps would become unresponsive. As soon as the browser became unresponsive, I noticed that a cascading problem would occur. These were always the browser used for debugging and Visual Studio.
#VISUAL STUDIO ULTIMATE 2013 WITH BLEND WINDOWS#
It resulted in me having to keep the Windows task manager open the whole time on a second monitor in case I needed to kill unresponsive processes. I changed the version of IIS used in debugging to the 64-bit version.
Strangely enough the most freezing and laptop lockups would happen in the afternoon. I would have to do a hard reboot at least 6 times a day. I mainly work on Web Applications, and this issue caused me to sit with an unresponsive laptop. Will the real culprit please stand up? First a bit of background: My problems with Visual Studio Ultimate freezing always seem to happen during a build and debug (or start without debugging). CodeLens Freezes Visual Studio 2013 Ultimate
Unfortunately, for the past four months Visual Studio has been frustrating me and driving me nuts! It keeps on freezing and locks up my laptop totally. As my development tool of choice, I use Visual Studio 2013 Ultimate. I really enjoy learning something new and getting to grips with new technologies gets my heart racing. I started a new job in January and being challenged every day is as rewarding as it is fun. CodeLens Freezes Visual Studio – This year has been quite a hectic year for me.