My system is W7, english; IIS 7.5, english, and VS2010 SP1, also english; why is VS throwing exceptions in spanish and how can I make it throw them in english?
Change language of error messages in ASP.NET
The solution was to add the following to web.config
<system.web>
<globalization uiCulture="en-US" />
</system.web>
Related
Since today I can't debug any applications anymore.
If I want to start the debug session, I get the error message
error while trying to run application: invalid pointer
It doesn't depends on the project, this behaviour appears in every project/solution.
What i've already tried:
Reset VS settings
repair Visual Studio
complete reinstall of visual studio
Changed Build Platform to x86/x64
Enabled native code debugging
If you press Ctrl-F5 to run the application, you won't get the error and the application will start, but you can't do debug, so this isn't a real solution.
The only way to solve the problem is to update Visual Studio: I had the same problem (WPF application), which was solved by the Microsoft Visual Studio 2013 Update 4.
If you're running VS 2013 and get an error that's pointing to the body tag, try adding this to the web.config under
<appSettings>
<add key="PageInspector:ServerCodeMappingSupport" value="Disabled" />
That key disables browser link which currently isn't playing nice.
I'm having a strange problem where I've got identical code in my local development machine running VS 2013 with IIS Express and my development server running IIS 7.5. It used to work fine but recently odd things started happening on my local machine. I saved off the rendered HTML output and noticed there was a small section of the layout code that didn't get rendered. I also noticed that the htm file from the server saved as ANSI and the HTML file from my local machine saved as UTF-8 BOM.
Any idea what might cause this?
We finally discovered this was caused by Visual Studios browser link functionality and to fix it we needed to disable it by putting this in the section of the web.config:
<add key="vs:EnableBrowserLink" value="false" />
Alternatively you can disable in in Visual Studio altogether.
More info: http://www.telerik.com/forums/the-new-browser-link-feature-in-vs-2013-is-causing-an-error-when-detailtable-of-hierarchy-radgrid-is-expanded
Upon debugging an ASP.NET WebForms project, I'm shown an error dialog in Visual Studio 2013.
The Browser Link feature includes a handful of pre-generated or runtime-generated JavaScript.
JavaScript critical error at line xyz column abc in http://local.host/foo/browserLink\n\nSCRIPT1010:
Expected Identifier
This is on setting the line label.for = id;
How can I avoid this error?
Visual Studio 2013 Ultimate
IE 11
Windows 8.1 Pro
You'll find the problem is the new Browser link feature.
You can disable it, it solved my issue with IE7 and below when debugging.
for is a reserved word. You either have to choose another name or do label["for"] = id;
IE doesn't accept reserved javascript words.
Adding the entry below to web.config resolved the issue for me.
<appSettings>
<add key ="vs:EnableBrowserLink" value="false"/>
</appSettings>
I need to debug WPF Client with RIA Services. In VS 2010 it was working fine and now I am under VS 2012 and I an facing this error.
Any clue how to return to debugging?
I have already checked web.config and it has <compilation debug="true" targetFramework="4.0" />
Did you try right click on devenv.exe and select Troubleshoot compatibility? And always execute VS with administrator permission.
I'm having trouble getting Visual Studio to recognize the #model directive in MVC3. As a result, I'm not getting any Intellisense help. For example, I just loaded up the standard base MVC3 project in Visual Studio and it shows all sorts of errors in LogOn.cshtml since it can't figure out what the view model is. However, if I run the application everything works just fine. So I guess this is more of an annoyance than anything else.
If you have installed the ASP.NET MVC 3 Tools Update make sure you have set the webpages Version in your web.config:
<appSettings>
<add key="webpages:Version" value="1.0.0.0"/>
...
</appSettings>
Then simply close and reopen the view and syntax highlighting and Intellisense should come back.
UPDATE:
Reinstalling ASP.NET MVC 3 Tools Update solves the problem.