Merge tool with .cshtml file crashes Visual Studio with RC1 tools #293
Comments
I can confirm it's happening with me as well... same exception dump. I'm doing a conflict resolution using source from TFS. To make matters worse, it's crashing VS2015 when it launches the comparer. However, a critical issue is that I can no longer open ANY cshtml file, VS2015 pops a message box "Object reference not set to an instance of an object" or "The operation cannot be completed". I can open them using another editor, like XML (Text) Editor. It appears the HTML Editor is causing the issue |
I'm also having problems with the merge tool and cshtml, though I don't get a crash, I just get "Failed to start the configured compare tool." The tool works with everything else in the project, and works on the file if I rename it to something that isn't .cshtml. The annotate tool also doesn't work, and that crashes Visual Studio. |
A little more information related to the HTML Editor crash: The HTML Editor only seems to crash when there are Razor elements in code file. For example:
Causes a crash while:
Does not. @slaneyrw Does this match your experience? |
OK, I'm able to repro. Going to start taking a look into this. |
same issue here. after vs.net 2015 update 1 update |
TFS: 168882 |
Checked in a fix for this |
How can we get this fix? |
This issue has been fixed and checked in. It will be in the next release of the ASP.NET and Web Tools tooling update. We don't yet know if that will be RC2 or if there will be canary (weekly updates) builds released before that |
I need it working, urgently. |
Does setting Tools->Options->Text Editor->Html->Advanced->Extension Management->Identify Helpful Extensions to false work around the issue for you? |
Worked, thanks. |
This is happening to me too, I'm using VS2015 Enterprise with Update 1 :S ActivityLog.xml
Visual Studio Info
|
Same problem with Visual Studio 2015 Update 1 RTM. When I click "Merge Changes in Tool", VS crashes and restart. 826 2015/12/04 01:55:59.728 Error |
+1 1010 ERROR System.ArgumentNullException: Value cannot be null. Parameter name: key at System.Collections.Generic.Dictionary`2.FindEntry(TKey key) at Microsoft.VisualStudio.Html.Package.Extensions.ExtensionsManager.OnTextViewCreated(ITextView textView, ITextBuffer textBuffer) at Microsoft.Web.Editor.Controller.TextViewConnectionListener.OnTextViewGotAggregateFocus(ITextView textView, ITextBuffer textBuffer) at Microsoft.VisualStudio.Html.Package.Commands.Html.VsHtmlTextViewConnectionListener.OnTextViewGotAggregateFocus(ITextView textView, ITextBuffer textBuffer) at Microsoft.Web.Editor.Controller.TextViewConnectionListener.<>c__DisplayClass24_0.b__0(Object sender, EventArgs eventArgs) at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.RaiseEvent(Object sender, EventHandler eventHandlers) Editor or Editor Extension 2015/12/10 14:09:25.059 |
+1 When can we expect a fix? FYI - the workaround from @ToddGrun worked for me. Does setting Tools->Options->Text Editor->Html->Advanced->Extension Management->Identify Helpful Extensions to false work around the issue for you? |
The workaround from @ToddGrun worked for me also. |
While waiting for the updated tooling to drop; the fix @ToddGrun suggested worked for me as well. |
Phew! Thanks everyone, the fix suggested by @ToddGrun worked for me too! |
Thanks @ToddGrun 👍 |
The workaround from @ToddGrun just works partially. I can open my .cshtml files again, but TFS compare still throws "Error occurred during difference operation: Cannot execute the configured tool.". When can we expect a fix? |
@ToddGrun is my hero! |
Workaround does not work for me either... Should that be working in combination to some other assumption pre-requisite please? |
Ran into this issue when attempting to merge a conflict in VS. Thankfully, @ToddGrun's workaround has saved the day. |
It is also happening to me |
Thanks @ToddGrun, saved me on VS2015 Update 1! |
This problem was even in VS2015 Update 2 |
+1 for in VS 2015 Update 2, disabling the extensions tool, worked at least for this particular merge. Please notify whoever owns the extension or just remove it all together. I've asked it to stop notifying me with the 'dont ask again' and that never works either. Thanks for the workaround @ToddGrun. have a good one. |
VS2015 version 14.0.25123.00 Update 2 also with this issue, but the method from @ToddGrun not working for me, is any other approach to fix? |
@ToddGrun 👍 thx man ! your workaround worked for me also/ |
@ToddGrun Dude you saved my evening. Cheers! |
I am using Visual Studio 2015 Update 2 with Microsoft ASP.NET and Web Tools version 14.1.20203.0 on Windows 10 and this is still an issue. The workaround provided by @ToddGrun works for me. |
Running update 2 on vs2015, same crash, but thankfully the workaround works. I'm merging a regular .html file, not even a cshtml.
|
Echoing what @oising said - same exception, same work around works. Running a Fully up-to-date VS2015 with Update 2. Given that this issue is already closed, can we re-open it or create a new issue for tracking purposes? |
@vcsjones @madskristensen Agreed. I don't know why this is closed. It's not fixed in update 2. |
If they can't fix this issue after two point releases, I suggest they take the easier route and update the text from "Identify Helpful Extensions" to "Crash when merging files", and default it to ;-) On a more serious note, @madskristensen -- why is this closed? The issue is still trivially reproducible in update 2. |
@tomexou Your solution worked for me. Thank you for posting it. |
Ping - any chance of reopening this? |
The fix for this issue was released in the new ASP.NET Core RC2 tooling |
Just ran into this issue and installing ASP.NET Core RC2 tooling for visual studio 2015 fixed it for me. I'm no longer getting an error that crashes visual studio when opening the merge tool. Thanks @madskristensen |
ping any update on correction? |
@MarcusPozzan It's fixed in the .NET Core Tooling Preview 1 for Visual Studio 2015 |
Thanks @ToddGrun ! It worked! |
how is this still a problem... |
This just confirm my impression that VS2015 is probably the biggest piece of crap software I've ever used. VS 2015 is by far the worst version so far and each update only seem to make it even worse. And I've been using it since 1997 so I have lots of Visual Studio versions to compare it with. We are seriously considering giving up on .NET all together as there as just so many problems these days :( And why is this case closed when the problem is obviously still there?? |
@improwise I'm not sure it's that bad. These guys do an amazing job with a product that has been through so many different iterations. It's practically impossible to have something completely bug free. Users will be users. We use .net all the time and don't have 'so many problems these days' However, you are always more than welcome to create your own product, plus, there's always notepad++. Happy Coding |
@brentdavid2008 Main problem is that it seems to get worse with every attempt to fix something. The Update packages seem to cause as many problems as they fix. Merge crashing, save buttons not working, frequent crashes, memory consumption increasing, lots of freezes and delays and so on. Even copy & paste does not working sometimes! Even my colleagues that has always praised Visual Studio as the best IDE (I used to be one of them) have now kind of given up on VS2015 and many has gone back to Visual Studio 2013 just to get some real work done and not just trying to figure out workaround to IDE problems constantly. I really hope MS gets their act together here... And I completely agree on Notepad++, had VS2015 been anything close to that, I would be very very happy :) |
Get the community edition not the RC...jeez. RC is a release candidate. On Sat, Aug 20, 2016 at 12:42 PM, improwise notifications@github.com
|
Not sure who you are referring to, if it is me I run Visual Studio Update 3 Patch 1 but was lead hear as I was googling to try to to solve one of the many problems with VS2015. |
The issue is still present in Visual Studio 2015 Update 3. The solution offered by @ToddGrun is already valid and it has worked for me. |
I still got this bug in Visual Studio 2015 Professional Update 3. I installed |
If I use the merge tool in VS 2015 while trying to resolve conflicts from a Git merge it will fail on some .cshtml files. This didn't seem to happen before installing the newer RC 1 tools this week.
I'm seeing this error message in C:\Users\AppData\Roaming\Microsoft\VisualStudio\14.0\ActivityLog.xml
Here is the info from About VS in case that is helpful
The text was updated successfully, but these errors were encountered: