Ok, so here is the issue we are having. We have a website that uses a DevExpress callback panel. We have gotten calls from users using IE10 that the page is blank.
I setup a machine with IE10 - to try and replicate the problem. When logging into the production website, I saw the same thing – the page is blank, except that you can see an empty SpitterControl up in the top left corner (indicating a control with nothing in it). I checked the f12 developer tools, all of the markup is there. Also, when going to quirks mode, or IE9 mode, page renders fine.
So good so far. The next step is to replicate the issue in my local environment so I can throw in some breakpoints and try to find the cause. Here is where I am stumped. Local dev environment no issue at all; Page renders fine in IE10. I am running IIS7 on my machine with the same .NET framework.
So, on to the next step. We have a machine where we stage code for beta testing – its configuration basically mirrors the production configuration. Same result, all IE10 pages rendered just fine.
I have kind of run out of ideas. I have of course researched the doctype, and forcing the IE9 mode. All things that I could try, but I just puzzled by the fact that all of my testing environments I could not get it to break.
Any thoughts?
Try setting up an offsite dev setup. It could be that within your domain. I know that in one case we had problems with devexpress controls loading out of order.
Figured it out - well work around anyways. Setting the worked. It just wasn't so simple to just make a change like that to the production database - but I finally got it in there to try it. Jeez.. what a pain!
The NuGet package option from this link worked for me so I assume that installing the hotfix on the server would also work:
http://www.hanselman.com/blog/BugAndFixASPNETFailsToDetectIE10CausingDoPostBackIsUndefinedJavaScriptErrorOrMaintainFF5ScrollbarPosition.aspx
SUMMARY:
Make sure you have NuGet installed
Right click on project then click on Manage NuGet packages
Search Online for "App_BrowsersUpdate"
I installed the one for .net 4
Republish
Related
I am getting this error a lot:
Feature '{insert feature here}' cannot be used because it is not part of the
ISO-2 C# language specification
I am working on a .NET 3.5 website that I've worked on on and off for about two years. I've never seen this error before my most recent around of updates. I'm using a decent amount of LINQ coding throughout and I get these errors related to much of the LINQ code. Based on what I've read it seems like even though I'm using .NET 3.5, for some reason it thinks I'm using 2.0. But I can't find anything that says how to fix it.
One example of a problem is that if I try to add a new item to the App_Code directory, I do not get the option to add a LINQ to SQL dbml file.
If anyone can shed some light on how exactly I would fix this, I would much appreciate it.
I was unable to locate an "Advanced" option under the build tab. I have a feeling it is probably because it is a web app. I looked through the web.config and found 2 parts that may be important. Most things referenced 3.5.0.0 or v3.5. The settings are consistent with older backups of the web.config from when there were no errors. By the way, only intellisense and things within VS2010 are giving me problems. The website is running error free.
I have completed a total uninstall and re-install of VS2010 and I'm still having the same issue. I fired up my old install of VS2008 and I am NOT having this issue there. However, I would MUCH prefer to use VS2010 on this project.
I opened the website in VS2010 on my work computer, and there are no errors reported. This is making me think that there is something on my laptop that is causing the problem. As I noted above, I completely reinstalled Visual Studio 2010 and I am still having the problem. What does this leave? I have only one extension installed in VS, and it's the same one at work and on my laptop. Also, I did not reinstall the extension after reinstalling VS, and the problem persists.
Both PC's run Win7 Ultimate. Have VS2008 and VS2010 installed. VS2010 has the same extension installed on both. On my laptop I have the full version of SQL Server 2008 installed, but only the Management Studio on my desktop (we have a server in the office). Would SS2008 have anything to do with it?
Go to your project properties, the Build tab, Advanced - that should allow you to set which version of C# you want to use. It should default to the latest version supported by the version of Visual Studio you're using, but it sounds like at some point you've switched it to ISO-2.
(That's certainly true for Windows projects and class libraries - there may be a different location in a web app. In particular, have a look in Web.config.)
If this has only started happening recently, I'd have a look through your source control history at changes to any configuration files. Also try creating a new project of the same type, and see if that has the same problem.
Jon Skeet's answer is mostly correct. The location for the update is in the "Property Pages" which I got to by right-clicking on the name of the website, clicking Property Pages, the Build item, then target framework.
The extension I use, Solution Navigator, has it's own heading for the solution. Right-clicking on it DOES NOT give me the Property Pages option. By chance I right clicked on the title of the website under the solution heading and was presented with the Property Pages option. In there was the Build tab which contained the target framework option.
Once I finally found the target framework option, it was indeed set to .NET 2.0 for some reason. I changed it to 3.5, reloaded the solution, and now it works great.
Thanks a million Jon for your help and time working with me!!
I dont know if anyone else has had this problem. I'm using VS2005 working on a C# website.
The problem is on the .aspx page, when I click on the "Design" option two things happen.
It does not switch to design mode. I see only source. But I the problem is that the source mode gets stuck and uneditable.
Second thing is that I cannot switch back to source mode and hence am stuck only in that non-editable mode.
I tried to Reset my settings, but that hasnt helped.
Any ideas?
Try running visual studio in safemode. Launches Visual Studio in safe mode, loading only the default environment and services, and shipped versions of third party packages.
Try the below command in Start-> Run
devenv.exe /safemode
http://msdn.microsoft.com/en-us/library/xee0c8y7(v=vs.80).aspx
i am using Netbeans PHP + Firefox 4 on Windows for my web development.
I've used a common firebug extension called Xrefresh. It was automaticlly refreshing my opened firefox tab everytime change in my projects directory occured, so pressing ctrl+s in netbeans was triggering auto-refresh in the browser. Very comfort way to work with css, almost live preview.
But now since new Firefox and Firebug versions Xrefresh doesn't work anymore and the question is - are therey any good alternatives, or does someone know how to configure Xrefresh now?
Without live preview my development is somehow slower.
https://github.com/NV/auto_update_stylesheets
This could help you. It refreshes the page via ajax on css save.
There's an automatic refresh-on-change tool for IE. It's called ReloadIt, and is available at http://reloadit.codeplex.com . Free.
Not an add-on to IE, but more of an "adjunct". It does not change the IE install, does not install a BHO or anything like that. So very low-impact installation.
You choose a URL that you'd like to auto-reload, and specify one or more directory paths to monitor for changes. Press F12 to start monitoring.
After you set it, minimize it. Then edit your content files. When you save, the page gets reloaded. like this:
I've managed to keep using xrefresh up until Firefox 9 however I'm not having any luck with version 10.
I've now switched to livereload, they've had a decent Mac version out for a while and a very experimental Windows version has recently been released.
I am trying to prevent VS from breaking on JS errors.
I have the following settings:
In IE, under Tools->Internet Settings->Advanced (tab)->Browsing,
Disable script debugging (Internet Explorer) and Disable script debugging (Other) are checked.
In VS, under Debug->Exceptions->Common Language Runtime Exceptions,
JScript Exceptions (thrown and user-unhandled) are unchecked.
In VS, under Tools->Options->Debugging->Just-In-Time, Script is unchecked.
There are some JavaScript errors that I just don't care about and it is driving me insane having to deal with them.
try This
This is more prominent solution rather switching to firefox. i tried this and it worked for me like charm.
check out alternative work around in same document if you dont want to choose silverlight tool..
Don't think you can do that. VS will auto enable the settings in IE when you run the page under debug (and will keep those settings as long as the IE window is open).
Obvious workarounds:
Set default browser to Firefox
Don't run in debug mode
I have VS2005 and I am currently trying to debug an ASP.net web application. I want to change some code around in the code behind file, but every time I stop at a break point and try to edit something I get the following error message: "Changes are not allowed when the debugger has been attached to an already running process or the code being debugged is optimized."
I'm pretty sure I have all the "Edit and Continue" options enabled. Any suggestions?
This may seem counter-intuitive, but turn edit and continue off.
There might be another "allow me to edit read-only files" or "allow me to edit even when I am debugging...no really!" setting somewhere, but I don't have 2005 to look at to check.
In 2008, turn off edit and continue and you can edit while it's running (but those changes aren't appplied.)
If you actually want to use edit and continue, you also have to enable it for the project, on the web tab of the project settings.
The application is actually running off of a compiled version of your code. If you modify it it will have to recompile it in order for your changes to work, which means that it will need to swap out the running version for the new compiled version. This is a pretty hard problem - which is why I think Microsoft has made it impossible to do. It's more to protect you from THINKING some changes were made when they really weren't.
For Asp.net it is possible to think of two types of 'edit and continue'.
One is a classic edit and refresh the browser. This works because the browser refresh recompiles everything except precompiled code behind files. This is not referred to as Edit and Continue, though in practice it provides a similar effect. In this mode you cannot change code behind files, because they were precompiled and deployed, but you can change just about anything else.
Another mode allows you to change precompiled code behind files but nothing else ... (this is the mode Chris Bilson mentions which needs to be set on the project properties for ASP.Net). In this case you are using the Edit and Continue feature of the debugger, which knows preciously little about ASP.net. The debugger just sees a loaded .Net assembly and can modify it when stopped in the debugger because there is a project in the solution that claims to know how to build it. In this case you are prevented from modifying things that would otherwise mess up the debugging session. This method however is the only way to change the code while it is running rather than requiring a browser refresh.
You are allowed to make changes to the *.aspx file while it runs, and you can hit refresh on your web instance to see those changes immediately. However, you cannot make changes to the *.cs/*.vb or *.designer.cs/*.designer.vb files while the program runs.
I search for this on Visual Studio 2008 WAP (Web Application Project) and it took me two days to find the solution, so here it is in the hopes it helps somebody else:
There are two locations that have to be checked, one it under tools-options-debugging-Edit And Continue-Enable Edit And Continue, the other is right click project-properties-Web-Enable Edit And Continue
For the record, I had a similar problem with VS 2008 and a different solution resolved the problem for me. Editing code in Visual Studio 2008 in debug mode
Check that you are not in release mode.
In release mode you cannot edit your code while debugging. Just change mode to Debug