We develop a Silverlight application, the latest version of which we have just deployed to our clients.
The problem is that some of our clients are getting errors when they attempt to access the application in Internet Explorer. The application loads fine in Google Chrome.
The error initially manifested itself as showing the Silverlight loading animation, getting to 100% and disappearing leaving a white page or simply sticking at 100%.
Having enabled JavaScript debugging, an error dialog appears informing the user of the following:
Line: 62
Error: Unhandled Error in Silverlight Application
Code: 2110
Category: InitializeError
Message: 2110 An error has occurred.
We cannot get any further than this. Can anyone shed any light on this issue?
Thanks very much,
Martyn.
I am very late, but since I could not find the answer that eventually solve the issue for me I am posting here for others :
In my case, the answer was to set back the compilation platform to "any CPU" I got the 2110 error in x86 and it loaded properly using "any CPU".
In my experience this is almost always a problem with dependencies.
To prove that it is, create a new Silverlight project and include all the references you have in your existing project and see if you get a white screen of death.
If you do then try removing references from your test SL project one at a time until you get something that works.
HTH
There are many reasons that cause this error. It may be from your code or IE itself. Could you ask the users do things such as:
Try to disable IE9 compatibility view. (Press F12)
Clear IE cache then close and re-open it before you go to the website.
If none of them works, you should check xaml code or attach the Silverlight process to the debugger and debug the code.
I have the same problem, but in Firefox x64, when I have in Silverlight csproj:
<Reference Include="mscorlib">
<Private>True</Private>
</Reference>
When I changed it to:
<Reference Include="mscorlib" />
everything goes well.
Related
I'm developing a mini project using asp.net in visual studio 2017 community edition.
When there is an error in my code, browser window doesn't show what are the errors. It only shows a blank page. Since I'm new to web development using asp.net, this makes it very difficult to debug the code.
I've seen lot of developers have suggested to edit the web.config page. However there is no web.config page in VS2017.
Can anyone help me to solve this?
Seems like issue with VS2017 it self! Error List Window.
When a build fails, the error list window won't be shown if you have
the setting to "show output window when build starts" turned off, and
you have not yet manually shown the error list window (View => Error
list). The build will fail but no error list window.
And as per the updated comments..it has been fixed in current release.
While configuring middleware, sequence of statements matter.
Try putting app.UseMvc() after Exception blocks.
You can try error pages for different status codes, this may help you.
https://github.com/aspnet/Diagnostics/blob/dev/src/Microsoft.AspNetCore.Diagnostics/StatusCodePage/StatusCodePagesExtensions.cs
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
I have a ASP.Net 4.0 site that I am editiing in VS2010. Every # Master and # Page tag has the blue squiggle lines giving the following error:
ASP.NET runtime error: Could not load file or assembly 'Interop.CertEnroll' or one of its dependencies. An attempt was made to load a program with an incorrect format.
I know it is related to trying to load a 32bit dll into a 64bit application but I am not sure how to control it since I am not sure how this Iterop.CertEnroll client is evening being referenced.
I am targetting Any CPU for my builds.
My application still functions but it bothers me to see all of these warnings and I have seen hints that this may be causing issue with my AjaxToolkit server tags not being recognized.
Thank you!
Karl
I discovered this solution for you. Since I cannot reproduce the error, can't exactly say if it would resolve the error for you, but you can still try. Here is the crux of the story from the link:
If you compile against x86 platform instead of Any CPU platform (which makes the code to run against x64 platform on x64 systems by default), it will work fine.
All the best!
Make sure you are compiling against .NET 4 and not .NET 4 Compact Framework.
I had the same issue not long ago with this missing dependency.
Installing Microsoft Online Services Sign In provides the correct assembly, although I'm not sure why this would be required.
edit: I can't seem to find the article that pointed me to the above download.
This is a known bug they aren't going to fix. You can try suggested workarounds though.
TL;DR: Check your master page(s) if the ContentPlaceHolder tags are specified correctly, and your pages to see that the ContentPlaceHolder tag ids are correct.
Long answer:
For anyone facing this issue and if the other solutions do not work, here is another thing you could try. I was getting the same error, with all master and page tags highlighted with the error:
Could not load file or assembly Microsoft.Practices.ServiceLocation,
Version=1.3.0.0
My packages were all in order and I spent quite a lot of time trying to get it to work. Turns out the error was misdirecting and the actual error was missing ContentPlaceHolder tags in my nested master page.
I've Googled this particular problem, but cannot seem to find a working solution.
Symptoms: After adding a breakpoint in the codebehind for an aspx page in a web application project, the breakpoint displays in the margin as a hollowed out red circle with an exclamation point enclosed in a yellow triangle in the bottom right of the circle. When mousing over the breakpoint, the message "The breakpoint will not currently be hit. No symbols have been loaded for this document."
Note: I'm trying to hit the breakpoints by "attaching to [a] process", namely w3wp.exe, located on a remote computer.
Things I have tried.
Recompiling other projects in the solution.
Checking to make sure that the configuration for each of the projects and the website in the solution is set to "Debug" on "any pc".
Closing the solution and restarting Visual Studio.
Restarting IIS.
Reattaching to the process (w3wp.exe).
I've been trying to hit the breakpoints using Internet Explorer version 9 and Mozilla FireFox version 4. In each case, the breakpoints are never hit.
Any ideas are welcome! Thanks!
Andrew
If you have more than one solution in your project.
Right click on your solution --> Properties
Set as --> Startup Project
Are you deploying your assemblies to the GAC? If not, copy the .pdb file along with the .dll file, placing both in the same bin directory. The debugger should pick up the symbols automatically.
I run into the same problem and guess what? Just do it: At solution explorer, right click on Project -> Package/Publish Settings UNCHECK "Exclude generated debug symbols"...
Maybe it can't solve your specific problem but certainly it will save another people from suffering.
I can't post a screenshot because I don't have 10 of reputation... :(
Like you guys I lost all day searching on google and stackoverflow and the problem was just that. I realized that when I saw the PDB file in the bin folder ready to be published becoming 0 bytes size when I clicked "publish"...
In my case I was trying to debug an ASP.NET Core app hosted in IIS. I noticed that when I published the app (dotnet publish) the generated web.config had this line:
<aspNetCore processPath=".\MyService.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />
I had to attach to MyService.exe rather than w3wp.exe to debug the app even though it was running in IIS.
This error produce by many reason, one solution is : its due to different framework version when you try to attach process. For more details, please visit: https://stackoverflow.com/a/13106908/1218422
I realize that this is an old thread, but the one thing that nobody mentioned was to make sure that debugging is enabled in the web.config file.
I had the same problem, fixed it by switching the debugging method. I was clicking F5 with web project set to startup project (and the "Don't open a page. Wait for a request from an external applicaton" selected in project settings).
When I attached VS debugger manually to the w3wp.exe process using the debug menu it worked.
I'm facing problems when i try to debugging with Visual Studio 2010.
My breakpoints don't work and gives the message:
The breakpoint will not currently be hit. The source code is different then the original version
I've go to tools and enabled "Enable Just My Code" but now i get the message:
Breakpoint will not currently be hit. No symbols loaded for this document
I've delete the obj folder, with no success.
I've used the "Clean Solution", i've Rebuild Solution, and so on.
What should i do more to fix this?
Thanks
One of the projects it's debugging successfully. I've just changed the ports of Web Server.
But other project (i've changed the ports too) still doesn't work. The message of this one is:
the breakpoint will not be hit. the source code is diferent from the original
I had a similar problem.
Trying changing the debug attribute of the compilation tag in the web.config:
<compilation debug="true">