I have an Asp.Net 4.5 web application. Since we migrated to IE 11 we have the following
performance issue: Whenever I click on a button, the button stays selected for nearly
two seconds and then the request is executed. This does not happen with IE 10 or Firefox.
Is there any IE 11 specific configuration I have to consider?
I profiled the application with ants profiler, with Internet Explorer's developer tools
and Visual Studio debugger. I did not find anything special on java script side nor on server side.
We are using DevExpress controls and a little bit of jQuery.
I know that I am very general, but we have no idea, what the problem could be.
After removing all java script, jquery etc, the problem did not disappear.
So we investigated more into the page itself. The reason for performance problems
was an update panel we used. Adding the workaround from
http://support.microsoft.com/kb/2000262
fixed the problem immediately.
There is nothing in ASP.NET per se that would be causing your issues. There has to be something wrong in the JavaScript is my guess. It could either be your code or DevExpress code. Do a memory profile, take a snapshot. Are there any memory leaks? Run the script profiler see what is hogging the CPU, etc. If I were you I would focus on your code and see if anything there is the issue because you can control it. If you cant find anything there check the DevExpress forums, etc.
Related
I have an ASP.NET Application I want to debug on localhost. When I run it without debugging, it runs very fast and smoothly, with about 3 seconds per page load. However, when I try to debug the app with Visual Studio and Chrome or Firefox, every page load takes about 20-30 or even 40 seconds to load, which is extremely slow. I have tried everything I found on the internet about these issues, yet none seems to help me out:
"Load all Symbols" from Microsoft Symbol servers, then uncheck that location
Delete all breakpoints
Uncheck "Enable property evaluation"
Other options I can't recall
Which is a good debugging configuration for asp.net apps? Any extra suggestions that may help?
Thank you very much and kind regards,
David
It is possible that your visual studio is using a lot of memory. You should try to turn off the browserlink which will reduce the amount of memory being allocated. It is still fine to disable the browserling and the preview still works.
Here is a guide and explanation
http://blogs.msdn.com/b/webdev/archive/2013/06/28/browser-link-feature-in-visual-studio-preview-2013.aspx
It is also possible that you have a lot of data or calculation to be ran in your form load.
Another possibility is a slow internet connection, this only applies if you have items or scripts on your page the are from an external source like JavaScript, CSS etc.
My company recently migrated to Visual Studio 2012 and I am using it to develop web application using ASPX pages. The pages are split with the C# in a code-behind file. After using 2012 for a couple weeks now, I noticed something: if my ASPX page does not correctly validate to the HTML5 standard (i.e. I am missing a closing tag somewhere), the page will not save. This problem does not occur in the code-behind file, nor does it occur on Razor pages.
I briefly looked through the standard Visual Studio settings pages, but cannot find a setting to allow invalid code to be saved. I also have Resharper installed (as well as the Productivity Power Tools), but cannot find a setting in either of those extensions that seem to relate to my issue. If it matters, the project I am working on is part of a TFS solution.
Has anyone else experienced this issue? If so, does anyone know of a setting that might have caused this that I may be overlooking?
Update: Since posting this, I have noticed that I am unable to save even after the page has been validated. It can take up to a minute before Visual Studio allows me to save the page. The length of time may be related to the amount of text that I entered before trying to save.
Update 2: After talking to a coworker who has a similar set of extensions, I determined that Resharper must be causing the problem. If anyone knows of a Resharper 7 setting that may be causing this, please let me know. I can't tell if this is a bug or an intended feature.
Final Update: Thank you to all who offered assistance, but after installing the Visual Studio Update 1, I no longer notice the problem. It seems to have been a bug that was fixed with the update.
As stated in the final update section in the question, after installing the Visual Studio Update 1, I no longer notice the problem. It seems to have been a bug that was fixed with the update. Problem resolved!
Grrr, still happening in 2015, and I don't even have ReSharper or Productivity Power Tools installed. I found a workaround. I quit VS, said YES to saving the items in the popup, reopened it, and found that they were saved to older statuses. I re-changed the code, saved (took many seconds but probably less than a minute), and recompiled, and the changes took this time.
It was nice that when I quit and saved (unsuccessfully), it at least showed that the code was in an older state, instead of showing the newer code with a perpetual asterisk.
I'd never seen this before, and hope never to again.
I am facing one weird problem. In my flex application, there is one
grid on click of each grid item, it will dispatch one event and show
the details. As usual am changing the state of the component to
achieve this. But this is working perfectly in my machine, but from my
client side it is not working. Only difference am seeing is the
difference in flash player version. The FP version am having here is
10,0,45,2 but the onsite is having the latest version : 10.1.102.64.
Will this cause any problem in the behaviour of the flex application?
Am quite confused here, because I have no rights to change the player
version in my machine.
Do anyone have face the same problem like this. Or can anyone help me
with the main difference between these two versions.
Thanks in advance for your help.
Cheers,
Anoop
Most behavioral differences between flex applications are due to different flex SDKs being used during compilation (for instance, is your client viewing the binary-exact copy of the .swf file that you are running) or browsers with different plug-in APIs (the way they handle 500 errors for instance). If you think it's a flash player version issue (they are probably rare since they run regression tests across player builds so that flash swf files from eons ago run fine), you can certainly upgrade to that player build and see for yourself.
Are you also able to rule-out any connectivity issues such as firewalls or proxy servers?
While the item is clicked what are you using you using to get the selected item - event.target.selecteditem or event.currentTaget.selecteditem ? Try to change from target to currentTarget or vice-versa,it might work in both the machines.
I've got a flex-based swf, which is loading an AS 2-based swf and then, negotiating further activity via a LocalConnection.
From time to time, the AS 2-swf can request that the flex-based swf load a movie.
I've arranged this via on(release){} functions.
The AS 2-swf, I'm making in Swish Max. In Swish, when i set the on (release) on a text field, (to invoke .send() on my localconnection), it works splendidly. However, when I attempt to perform the same calls for an on(release) attached to a movieclip, it actually causes the Flash player, and even the browser plugin to crash.
In fact, the browser (IE) crashes as well.
I checked the debug trace that ie asked me to send to microsoft at the last IE crash, and i noticed a StackOverflow exception embedded deep in the trace, but I couldn't determine its source.
Can you help me understand what's going on here?
Are you having more than one LocalConnection connect to the same channel? This will cause the browser to crash.
Are you sending lots of requests at the same time, this will make it crash, and some browsers are more sensitive for those things than other.
This earlier post might have some helpful tips for you.
That's a wrong way to debug your application. Use your Flex Builder's debugging tool instead. You tend to lay blame on LocalConnection as it is the most complex part of the operation, when it could just as easily be an infinite loop.
You don't seem to be using the right tools either. I'd trust FF's FireBug over IE's dump. Besides, we'll need to see some more code before we can accurately tell you what's wrong.
Are you sure the crash is not only in your computer? Try running the FlashUtil??.exe at \WINDOWS\system32\Macromed\Flash\ to fix/update the Flash installaction. There are some known issues that corrupt Flash installation so it become unstable when using some objects.
I am working on an ASP.NET 3.5 project which has 55 projects in a solution. When opening the solution in Visual Studio 2008, it takes over a minute to open - about 1 second for each project. However, if I disconnect the network cable before opening the solution, it only takes about 15 seconds! Any ideas about what could be causing the slowdown?
I had this happen to me back in the days when we were using Visual Source Safe.
Could be your source control plugin asking for updates if you have the solution under source control.
You should do some investigation, fire up Wireshark, start a capture on the interface in question and see what traffic is flowing over the wire.
Can I answer a question with a question? What is the secret to getting VS to not just die with that many projects, let alone load in a phenomenally quick 60 seconds?
At about 10-12 projects the compile time on Visual Studio becomes unbearable, at about 5-8 projects Resharper will crash. The IDE is such a memory pig that even opening more projects by using multiple instances of VS usually isn't an option.
Anyhow, it's all about memory usage and the odd ball out project is probably doing it, e.g. the one with the most files.
I had the same problem this week (5 years later!!). It was caused by a huge .suo file (almost 400 Mb), deleting it fixed the problem.
A few years ago I remember a colleague having some similar problem (with a lot smaller solution, and in VS2003). Can't remember the details, but I think it was related to the local ASPNET user account (or rather, that it did not exist). Not sure though...
As a side note: I usually find it more efficient to have perhaps around a handful of projects in each solution (usually one solution produces one or two assemblies used in production code), and then have a few Visual Studio instances running at the same time. 50+ projects in the same solutions feels like asking for problems.
Might be that you have other dependencies though, just wanted to share my thoughts.
which has 55 projects in a solution
WOW. I can't imagine what type of solution needs that many projects. The answer is probably that your source control provider needs to refresh the status of each of the items, all of which take time.
For edit-merge-commit style version control systems, such as subversion, this operation doesn't take place. Try temporarily removing source control from the entire solution to see if this is the culprit.
If your solution is attached to source control, then it is trying to load up the symbols and verify which items you have checked out. So, if you have a slow connection, it is oftentimes faster to take the solution offline.
http://www.tmgirvin.com/2009/03/working-offline-with-visual-studio-2008-and-tfs.html
EDIT
Another solution which I've seen used,
create a
_webTier.sln
_database.sln
_build.sln
( is your project name)
and each of those solutions is a self-sufficient part of the entire project, but that way if you are working on the webtier and you don't need the database project or the mobile project parts to load up, you can just open the webtier solution.
The build solution contains the entire package that needs to be built, and takes a very long time to load.
I had this problem on a development machine with no internet connection and it turned out that the problem was related to a setting in IE's internet options:
Control Panel -> Internet Options ->
Advanced -> Security -> Check for
publisher's certificate revocation
After making sure this was unchecked my solutions started loading quickly again.