I have an old WebForms app that I'm working on. I'm running in debug mode.
I get an error message when loading a page. It is a message from a dynamic script:
Javascript Runtime Error "False" is undefined
I'm stuck as to how to debug this. I was thinking that I might need to update a nuget package, but I don't know which one.
Update:
Get this error with IE 11. Do not get the error with Chrome.
Just in case someone else hits this. I was using LastPass password manager. For some reason the JavaScript did not behave when using Visual Studio debugging with IE. I turned the password manager (LastPass) off and we were home free.
Related
I created a simple UWP app from the VS 2017 blank UWP template. No added XAML or C# code-behind:
Create new app with Blank Universal Windows template
Set Debugger type to Mixed (Managed and Native)
Build and Run (No XAML or code added)
Following error: WinRT originate error - 0x80070490 : 'Element not found.'
This happens every time. Does anyone have a handle on this error? If I don't have Mixed Mode debugging on, I don't see the error but I'm assuming it's still there. Is this an error that I should be concerned about?
Thank you.
A lot of problem may result this error, and it should not be a fatal error in your case. Most likely you changed the default Exception Settings in visual studio.
Just like all other apps, Windows use exceptions and catch them at different level.
For end user, you should not see this exception and app should not crash.
In your situation, I think you click continue and the program should not crash, and it should not be a big concern.
I suggest you:
1, start and debug your app, open Debug|Windows|Exception Setting, then click the 'restore the list to default settings' button
2, restart your app.
3, You should not catch the exception, but you still see error message in Output window.
If you still see a exception window popup, you need to post more information like your os version, and then someone can help you
I met this error when I call the winRT api CommunityToolkit.WinUI.Notifications.ToastNotificationHistoryCompat.Clear(). Then let the app toast someting once the error had gone.
I am new to Laravel. When I am in debug mode I get the following errors every time every page loads:
The payload is invalid
After pressing two times on Continue I get the error
The MAC is invalid
The error messages are located inside the encrypter.php file. After pressing "Continue" again, I can proceed with debugging with breakpoints and so on, and everything works fine. The $payload-variable is null.
The project is still very basic. Only some things like CRUD like explained on tutorials.
What is payload? And am I missing some kind of configuration? How to get rid of these error messages?
The answer is found in this post:
Can't using Visual Code to debug in Laravel project
I also:
closed VS Code Editor
cleared all history in my browser, including cookies and cache
ran the commands as mentioned in the post inside the windows cmd window (so not the integrated terminal inside VS Code Editor)
When I open WebMatrix it works without problem and shows the start page.
When I click 'My sites' and choose my site or choose My site by click 'Open'=> My site or create new site (and choose the site type: Empty, App Gallery or Template Gallery) WebMatrix crashes. Note: It crashes when it needs to show the site pages.
I tried to re-install WebMatrix but that didn't help. I also tried to change the Workspace(by clicking 'Options' on the start page).
When it crashes, I get the message 'Windows is looking for a solution to the problem.' (My computer isn't in English so that might not exactly be the words) and then I am asked if I want to close/debug the program. I click 'Debug' and choose Visual Studio. I don't know how to debug a program, but I tried and it says to me that:
System.NullReferenceException was unhandled
Message: An unhandled exception of type 'System.NullReferenceException' occurred in Microsoft.WebMatrix.Core.dll
Additional information: Object reference not set to an instance of an object [-translated].
I have searched on the internet and here and I didn't find any solution to my problem.
Actual Answer
This bug is in the market for a time now. I have seen similar issue on another forum too, where the user was facing the same issue and same thing he tried but all in vain.
I think you need to wait for the next Update for your System, or try removing each and every component that WebMatrix installed, that means all the .NET Frameworks (4th version), Sql Dependencies Sql Server Ce, and all other files that were shipped along with WebMatrix to your computer. Remove them, and start the installing process once again freshly.
If nothing does the job, please uninstall WebMatrix 3 and install WebMatrix 2: Click here for link. I know it is awkward to go back a version, but you'll have to. Secondly you can mention this bug on their support/suggestion page. They would fix it.
http://webmatrix.uservoice.com/
I hope that would help you. And you'd be back in developing the apps :-)
Just for information
Secondly, do you understand what is meant by debug? Debugging is a method or process to remove the bugs from a software or an application etc. When you chose Visual Studio, it provided you or not provided you with the WebMatrix source code, I am not sure I never tried it. And you tried out debugging it. The exception is gave you, was a message saying that the parameter you're passing onto the next stage is a null. Which means it doesn't even exist and thus the value or the method cannot be executed and it breaks.
I just configured my Visual studio 2010 with IIS express 8.0. It works perfectly but in case of any error in my code it is showing me crash page in encrypted format (Meaning - It shows full of boxes and some special characters). So every time i need to go event viewer to check the issue. Can you please help me in this?
This is how the message looks:
��I�%&/m�{J�J��t��$ؐ#�������iG#)���eVe]f#�흼��{����{����;�N'���?\fdl��J�ɞ!���?~|?"��Ey�')=��y6�����h���8]�����u]���u�-�������Gi[,�ߪ�?��WZ4i���uQ��t������>z��YQ6�Ҽ������S����YQ���|9+�O�f �ϫly�����A���U��?�_�������������������w�n<=>9��ypzr��/�:�]�W�b]f�/\N���ٲ%����G�(Eӏ�b���(��>�� 1~�]/����K���=^����Xe���1��Y����2�6�u�A:�f��/>����y�(��G�d^ϲe��!z���ђh���QS� �����iUV��I�M���ԃ�z�>�EV_���Z=J���������T���������f�����Z�s���� �-H¸���U�w�|=-fYzR-�������|��<&�o�Z()*�S!U��k�g����o��j��.�_�/^��u�/��J�Iն��Q���z�i�n�-gل���ݞ��Y^����H�8/���CMC� ԡO��w}V|W���\?�#�}t5/��#����G���{�:�iܩU(��8=^��b�؎��������vwv~���ٮ��YS���������|�(}\�l������-��b{4��3�y���4�������Q���آ%������~�^/g�f�U~AT$D���uq�F�sr�>͛i]�DVߝ/���P���i�ߥՔ�������2o����f�19h���|E�n��;������}x��:I~��e���N��5�ϑ�I~�h�}��JV>ͧ��f,x��'.���ﶮʒ�b�N�I�5���>ْ_2K4�*�s��9$r��U������M�Hw�ӺZ���C����{������lIf.?c3��wg<|���ϧ�t ��wgD�������{�h��o�-��fE/���(����#��Q���lY��9nɖ�
I just resolved the issue. Initially my application was working in integrated mode. I tried it with classic app pool and it started showing the real error message :-)
since moving to Windows 7 (IIS 7.5), the debug assertions do not prompt a pop up dialog anymore.
I have tested this in a separate project, and noticed that they do work when using the integrated Visual Studio Developer server (Cassini) but they do not work when using IIS Web Server.
This is a big issue for us since we are counting on debug assertions to identify potential programming errors, so any help would be appreciated.
Thanks. Eyal.
That's because failed debug assertions are displayed in the Output window now instead, under the Debug section.
To view the Output window in Visual Studio 2008 go to the 'View' menu and click 'Output'.
I also find it inconvenient. Some more info...
You can work around by using
System.Diagnostics.Debugger.Launch();
You can make for example this function
[Conditional("DEBUG")]
public static void AssertEx(bool condition, string message)
{
if (condition) return;
System.Diagnostics.Debugger.Launch();
// Still write the message on output
Debug.Fail(message);
}
and get similar results.
That is the default behavior now and it cannot be changed.
What you can is generate a file with the assertions that failed in your app. That will still help you track your issues without halting the app when running inside the IIS.
Take a look at this good article about it.