I have a .NET Core 3.1 web application and I'm working in VS Code.
If I make changes to my HTML or JavaScript, the browser doesn't see the changes when I refresh the page. This is happening with IE, Firefox and Chrome. If I stop the project and re-reun it, the changes are there.
I've tried :
CTRL+F5
Right click refresh button "Empy Cache and Hard Reload"
Clearing cache and browser data through settings
Checking the Disable Cache option in Network tab of DevTools
Restarting my computer
How can I make the browser see the changes I'm making to my project?
I don't want to have to constantly stop and start my project for small content changes.
I've figured this out. Turns out that for .NET Core 3.1 and possibly other versions, you need to install a Nuget package to enable compiling during debug!
I installed this Nuget package:
Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation (version 3.1)
And added this to Startup.cs > Configure Services:
services.AddRazorPages().AddRazorRuntimeCompilation();
Everything works the way it should now.
Related
I am having trouble debugging my web project using the Chrome Browser. I can only use IE to do my debugging. I did some "googling" to resolve this problem, and came across a few Microsoft threads that said to update to the latest version of VS2017, which I did. I use version 15.9.13 and Visual Studio 2017 tells me I am "up to date" when I check for further updates.
When I first updated VS 2017, it started working, and I could debug using Chrome (finally!). But now it has stopped working again.
I saw in other threads where people suggested deleting the .vs folder, which I did, but had no luck with that.
Google Chrome is up to date at Version 75.0.3770.100
I debug and run my application as "Administrator" so that shouldn't be the problem either. I also close all browsers before running the debugger, so Chrome isn't running elsewhere when I try to debug.
Is there any explanation why Chrome cannot launch when using debugger? I would really like to use Chrome because of it's superior "dev tools" and inspection tools. Any suggestions? Was sad to have it working only one day.
Having configured the same environment like yours(VS version and Chrome version) but can't reproduce the issue.I would think if something is broken in VS or maybe third-party extension is the causes this issue.
Please try:
VS repair and a reinstall of Chrome(don't forget to backup the bookmarks)
Uninstall or disable third-party vs extensions, this won't take effect until restart vs
Navigate to %LocalAppData%\Microsoft\VisualStudio\15.xxx directory, delete all ComponentModelCache folders in all 15.xxx folders.
Open your project in vs, changed the target browser from Chrome to IE. Then F5 and wait until it is finish. Stop it and change the browser back to Chrome. After that the error disappeared.
Also, create a new asp.net web app and debug it with Chrome browser to check if the issue persists. Hope it helps.
When I save changes to my css code, Browser-sync doesn't refresh the browser automatically. I still have to click on my browser window and hit F5 to see the changes I have made. I installed npm and browser-sync and it shows I am connected to browser-sync. I am using Sublime Text 2 and Chrome (Dev 56.0.2924.87) on a windows 7 operating system.
Any ideas on how to fix this? Thank you!
I found a solution. I had to fix or update deprecated npm packages. How to determine path to deep outdated/deprecated packages (NPM)?
What also helped - Gulp. I used Gulp in combination with browser sync and now my browser automatically refreshes when I save changes.
I used the following link to guide me through using Gulp for the first time: https://css-tricks.com/gulp-for-beginners/
I have 4.4 updated to 6.2.15. And the RTE doesn't work in Chrome (45). But the problem is in the version 4.4 the same. I checked the user options and I tried to change the BE compress option in Install tool. I played with the options in the extension options.
In Firefox will it work. I have no idea anymore and I search in the whole internet.
Clear all cache in TYPO3 and clear your browser cache - you should allways do this after an upgrade. You properly still have a compressed version of the JS file in your typo3_temp folder or a cached version in your browsers cache memory
I'm building a mobile application with Visual Studio 2013, using Ripple Emulator and Cordova.
Every time that I try to inspect an element (hitting Ctrl + Shift + I, F12 or right clicking the page and selecting Inspect element) the Google Chrome closes and Visual Studio stops running the application.
Has anyone know why I'm unable to inspect elements inside the browser using Ripple Emulator?
Ps: Visual Studio 2013 has his own DOM Explorer but the experience is not the same as the Chrome Developer Tools.
A simple workaround is to start your project without debugging (Ctrl+F5) from Visual Studio. This will allow you to use the Chrome dev tools (F12 and so on) without killing the VS debugger process and therefore stopping your Ripple session.
I've been having the same issue since upgrading to cordova tools update 3 with visual studio 2015 community edition - it was working fine before "upgrading"
I haven't found a reason why, but there is a workaround which is to start your debugging session (F5.. or whatever) then hop back to visual studio, then select "Detach All" from the debug menu. This, or use a different browser (Edge works fine in Windows 10, but I'm not used to it's interface).
Hope that helps.
There was a change in the chrome debugging API that prevents VS from inspecting the elements and changing the style. Chrome version 43 will work. You have to take some steps to keep it from auto updating. The installer for chrome 43 is here:
https://dl.google.com/chrome/win/4ED6DD719811795B/43.0.2357.134_chrome_installer.exe
You will need to uninstall chrome, update the registry, then install chrome 43. When you go to the about screen it should say updates have been disabled by the administrator.
Here are the registry changes:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update]
"Update{8A69D345-D564-463C-AFF1-A69D9E530F96}"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Google\Update]
"Update{8A69D345-D564-463C-AFF1-A69D9E530F96}"=dword:00000000
This thread has more information on the changes needed to the registry to prevent the auto update:
cannot stop Chrome from updating from 43 to 44
NOTE: this means you are not getting security updates on that install, only use this until the issue has been resolved in an upcoming patch.
I have downloaded the javafx 2 samples and want to run in from its HMTL. For example there is one javafx application called BrickBreaker. For the specific sample the following files exist : BrickBreaker.jar, BrickBreaker.jnlp and BrickBreaker.html
When double clicking on jar or jnlp the application runs as expected but when i click on the html the application does not run. Instead i get the message "View the conectes of the page. Please install javaFX"
Why is that happening ? ( i have the javafx installed as the application runs when choosing the jar and jnlp files). My guess is that the html should be called from within the context of a webserver meaning that i should deploy my application first to a server and call the url from my explorer. For example if using glassfish i should call the url http://localhost:8080/Brickbraker
The problem is that i don't know how to deploy the javafx application in the server.
i tried to copy paste all the above three files in the autodeploy folder but it didnt worked...
Could you please help me?
Thanks in advance
EDIT: some more info - I have installed JDK 7 and JavaFX SDK 2.0.2
No, JavaFX is client technology, you don't need Glassfish to run it. JavaFX should run in browser the same way as Java plugins do.
If you can't run an application directly from html file it means your browser doesn't recognize you have runtime installed.
There can be next reasons for that:
JavaFX runtime is actually not installed (check in Windows Control Panel)
pure java plugin is not installed (you can check on java.com)
javafx runtime is 32bit and you are using 64bit browser (or vice versa)
you are using not supported browser (e.g. Safari)
you are using not supported system (at this moment, January 2012, only Windows supports runtime)