I am using Visual Studio 2013, and have a Web Application that I am trying to squash a few bugs. Previously I was able to start debugging, make a change to the user control then refresh the page and see the change. Now I have to stop the debugger and rebuild the entire project before the change shows. I am only changing the markup (things like in-line css, HTML, etc) and not any of the code behind so a recompile shouldnt be necessary. I have verified that this is not a browser cache issue, as I have used several browsers, and cleared the cache after loading the page. I also used incognito mode to make certain nothing was cached. Any ideas on how I can fix this?
Related
I have bootstrap in an ASP.NET MVC application. I changed one single value in the bootstrap.css file and now it's not updating. When I actually view the source file in debug mode, it also appears as though I have updated nothing. I have had an issue before where it didn't update upon deployment, and in that case I had to delete the minified file, so I also tried deleting every bootstrap file (aside from the scripts) except bootstrap.css, but still it is as if I never updated it even in debug mode. I used to be able to change the file and the screen would live update in debug mode. It's like somehow I totally locked it but I don't know how.
Starting with the basics, have you definitely hit CTRL + F5 (as opposed to just F5) when viewing the page to ensure that you're not viewing a cached version of the page? I've had a similar issue where, even though changes to a stylesheet are usually picked up when a page is reloaded, sometimes you need to force the cache to refresh to view the page correctly.
I made a lot of research on this topic but none of the found solutions helped me.
So, let's start: I have a VB ASP.NET WEB Application.
The problem is the users can see the source code of the aspx files in the browser (IE) when the Display intranet sites in Compatibility View is unchecked.
I tried all of the methods, settings compatibility from IIS, web.config or even from the meta tags from <head>.
I discovered that also with the checkbox unchecked if I use Enterprise Mode the browser displays the page ok.
I tried then to find a solution to force the Enterprise Mode from code but I didn't find anything without changing registry keys. Changing registry keys can also be done to the above checkbox.
If I go in the DOM Explorere in IE and I try editing the source, anything I delete from there, the page is displayed ok.
How can I force the Enterprise Mode, or the Compatility View Mode from code? or is there another solution for me to solve this problem?
In my opinion you need to check the caching of the application if you say that if you modify something in DOM the page appears.
I'm just starting to play with Durandal, using the starter kit. I've added a very simple new view/viewmodel combination (essentially a copy/paste of an existing one from the sample) and mapNav()'d the route.
The problem is happening when I try to refresh my browser...the new view simply does not appear. It's not in the nav bar, nor can I navigate directly to the view by typing in the address bar. I know the code is (or should be?!) correct because if I go to the page in a different browser, everything appears as it should.
Is there some browser caching that Durandal is doing somehow? Sometimes F5 or Ctrl+F5 works to refresh, sometimes it doesn't. I also can't deep-link to a specific 'page'. Ie:
http://localhost:52625/#/newpage just gives me a blank
What am I missing?
The option that I use in Chrome is to open developer tools and right-click on the refresh button. There is an option for 'Empty Cache and Hard Reload' which always fixes this issue for me. I don't know the equivalent in IE but try this and see if it fixes your issue.
Most browsers will cache modules returned via RequireJS, which is how Durandal obtains its modules and view models.
CTRL+F5 doesn't help because that just refreshes the initial page - all the modules are still requested using javascript (RequireJS), so they are usually pulled from cache first.
I've found it's best to disable caching in your browser's developer tools. Doing so will ensure that all network requests are loaded directly from the source and not from cache.
See this question for additional information: Debugging when using require.js cache
Another solution is configure RequireJS to set its urlArgs property: https://stackoverflow.com/a/8479953/91189
This solution works ok, but makes it harder to debug, at least in Chrome, because breakpoints are lost every time the module is loaded, since it's technically a different file being requested each time.
I started out with a basic site.master. After I laid out several pages, I have found that I need to make changes to the site.master. The changes show up while I am working in Visual Studio, but when I run the application, they don't take effect. What do I need to do to have them show up?
When you make changes to CSS or javascript (or any other static content, for that matter), you need to clear out the browser cache to ensure the latest version is loaded from your server.
You can force a reload from the server by using Ctrl + F5 on most browsers.
SSRS has a find button on the toolbar. Hosting an SSRS report control in ASP.NET and when you use the find and it finds something at the bottom of the report, it doesn't scroll down automatically. Wondering if anyone has seen or done anything to make the scroll happen on find in the SSRS report?
Make sure you are running the most updated version of SSRS. I recall in the past some of these controls were broken and fixed in a later release.
Ensure Javascript is enabled on your browser and add the site to your trusted list. If I recall correctly, IE has strict default permissions for intranet sites. If that doesn't work, see if it works in another browser and that will help you determine if it is browser related.
Make sure you have all CSS and javascript resources on your server. My reports contain a reference to: "assets/js/app-ffc8de72-74aa-48f8-bf1d-634ee0627bca-bundle.min.js".
I can confirm this feature is working in SSRS 2016.