VS 2001 SP1 crashes non-stop when editing razor views. I'm never sure what causes it. Sometimes it's fine, and then other times it crashes when I try to edit an @if block. Then on another its ok. Or it causes VS to freeze for a minute or two. It does this in /safemode, and normally. In mvc3 and mvc4, with and without SP1 applied. Also, typing / intellisense in .cshtml files is really slow. Lagging 1/4 to 1/2 second behind key-presses at times, even when editing plain HTML. Maybe these issues are related?
I dont' see how anyone can hope to use Razor for actual work, if this kind of performance is a problem. Since people actually are, they must not be living through this nightmare. The problem (at least the *latest* problem) is in the report below.
Does anyone know what the heck is going on?
Problem Event Name: CLR20r3 Problem Signature 01: devenv.exe Problem Signature 02: 10.0.40219.1 Problem Signature 03: 4d5f2a73 Problem Signature 04: Microsoft.VisualStudio.Web.HTML.Razor.Implementation.Shims.2_0 Problem Signature 05: 10.0.0.0 Problem Signature 06: 4f221241 Problem Signature 07: 44 Problem Signature 08: 105 Problem Signature 09: System.AggregateException OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033
25 апреля 2012 г. 6:17
It is always the same problem, and this is the stack trace from WER
Application: devenv.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AggregateException Stack: at System.Threading.Tasks.TaskExceptionHolder.Finalize()
I was able to fix it by adding this to the web.config in the Views directory. Will this have any bad side effects?
<appSettings> <add key="webpages:Version" value="18.104.22.168" /> ... </appSettings>
25 апреля 2012 г. 7:23
For an MVC 3 app then that is the correct version. But that should have been automatically generated when you created a new MVC 3 application via the template. If you didn't use the template then more problems are likely to occur.
The exception in question is being caused by an exception while an async call is running in the designer. It makes sense that webpages could have been causing it.
Michael Taylor - 4/25/2012
25 апреля 2012 г. 13:48Модератор
When something is normal, it doesn't even occur to mention it:
I am making an MVC4 app. v3 works just fine!
* forums require two clicks on reply to reply. clicking to vote helpful is not an ajax call, causing me to lose my reply, hence this short one. the back button is broken now, meaning <- doesn't restore the previous form. The editor mangles my text so bad I'm normally editing HTML to remove a bold/underline. Sigh. Move to Markdown guys!26 апреля 2012 г. 8:56
MVC 4 is still in beta. You should post problems that you are having in the ASP.NET MVC forums instead. This forum is for the C# IDE itself and not beta products. I can tell you that I'm using MVC 4 without problems so I suspect there is something about your machine that is causing problems. Nevertheless it is beyond the scope of what we can help with here. The MVC forums will get you the help you need.
Michael Taylor - 4/27/2012
27 апреля 2012 г. 13:45Модератор
I guess that makes sense. I'll move it over there. Put it here because it seemed like an IDE thing to me, I didn't really stop and think what part razor belonged to, just thought of it as part of VS and not mvc specifically. I saw other mvc related stuff here, which is how I ended up here in the first place :) Thanks for not recommending connect!27 апреля 2012 г. 17:55
I rebuilt my development VM, installing just VS.Net & MVC4. I skipped MVC3 in case that was part of the problem.
The issue has gone away now, after the rebuild, but I'm worried about the future ;) I occasionally get issues with the designer not knowing what ViewBag is (or @Html.), and need to delete the ASPNet temp files in user/appdata/local... but thats it.9 мая 2012 г. 2:02