In Visual Studio 2010 I can change cshtml file with the project running, save it, refresh the page in the browser and see my changes take effect. But, for some reason I can't see my changes when I refresh the page while running a Visual Studio 2012 project. I have to rerun the project to see my changes. Needless to say, it makes developing in VS 2012 impossible, because I can't test my changes out very quickly. So, unless, I can get this to work in VS 2012, I'll have to stick to VS 2010. Can anyone help me with this?
P.S I had installed Visual Studio Update 2 hoping that it would fix this issue, but it didn't get fixed
Tools->Options->Environment->Documents->
Checked first option with suboption
Detecked when file is changed...
Auto-load changes..
I hope after ctrl+f5 it works...
or maybe
Tools->Options->Projects and Solutions->Build and Run-> On Run, when projects are out of date
Choose Always Build
Related
EDIT: Good information provided below to diagnose, but the issue was I was running Visual Studio 2022 17.3. Version 17.4 is required for .NET 7, and I had just installed that. Once I installed the latest version of VS, all my problems went away. Install with Visual Studio
Suddenly today, debugging my ASP.NET Core 6 and 7 apps suddenly has stopped working. I hit F5 to debug, it stops on my breakpoint, but as soon as I continue or step into, I'm shown this dialog:
I haven't made any changes to code, I'm simply trying to continue after I've stopped at a breakpoint. This just started happening today and I can't figure out what I did.
I haven't made any changes to code, I'm simply trying to continue
after I've stopped at a breakpoint. This just started happening today
and I can't figure out what I did.
Well, if your visual studio stop working for debugging all type of application, please check following configuration:
1. Tools > Options > Debugging > .NET/C++ Hot Reload
2. Tools > Options > Projects and Solutions > ASP.NET Core >
Furthermore, If you select the Always rebuild option in the dialog box, you won't see the dialog box again in the current Visual Studio session, and Visual Studio will automatically rebuild and reload instead of showing the dialog box.
Note:
In addition, as you can see above in the first release of Visual Studio (version 17.0) the standard Edit and Continue dialog is still shown when using Hot Reload with the debugger. This was a bug and has been resolved starting with 17.1 Preview 2 release.
If you still need more details about the issue you are having with, I would higly recommend you to check our official document here.
If issue still perist:
After checking above configuration, if your issue still persists and if you are not using Visual Studio (version 17.0) then you still reset your unknown setting in visual studio as following:
Go to Tools > Import and Export Settings.
Then No, just reset settings
Finally, restart Visual studio.
You can get more details here.
When I go to start debugging a webform I have created in Visual Studio 2013 using any browser, the page comes up garbled. However when I publish it to a web server, it is fine.
I already searched the web and tried to disable the browser link as others have suggested. I tried recreating the code in a new webform. I have uninstalled and reinstalled IISExpress and Visual Studio 2013. Please see the image attached as to what it is doing. Any help is much appreciated.
Thanks Mark,
it was definitely the compression setting. I searched online for it and changed it in the applicationhost.config file and that fixed it.
EDIT:
Found issue to be resharper. When I disable it it stop showing errors.
When I start a new Blazor fullstack project from Visual Studio it shows error in IDE. I have looked at Visual Studio displaying errors even if projects build but doesn't seem to help.
I followed the guide on Blazor (https://blazor.net/docs/get-started.html)
But the client side project shows lots of errors
EG:
and more details:
and:
Any one else tried this and know how to fix it?
I am running VS Studio Enterprise 2017 Version 15.8.8
I have installed ASP.NET Core Blazor Language Services.
Everything seems to work as it should. I was able to add new page with external RestAPI calls and all.
Edit:
Updated VS to latests version with no luck
Seems it might be resharper:
https://resharper-support.jetbrains.com/hc/en-us/community/posts/115000554550-ASP-NET-Core-Razor-Pages-page-Cannot-resolve-symbol-
Well. Seems that jetbrains is aware of issue.
It can be found here:
https://youtrack.jetbrains.com/issue/RSRP-469186
Not much to do than disable Resharper for the moment and wait for them to fix it :)
If you need help to disable and enable it again:
How can I disable ReSharper in Visual Studio and enable it again?
For some projects VS 2015 crashes when I try to rename a symbol (F2). If I create a new project it works fine, but my main task is a older project where my colleagues uses VS 2013 and there it keeps crashing.
I have found a possible solution which states that I should uncheck "Use undo transactions". The problem is that I can't find this setting in Visual Studio. Where is it? Or am I on the wrong track?
Did you already check this CodeMaid issue?
That settings you mentioned seems related to CodeMaid extension, not to Visual Studio on its own. I don't have that extension, but the options seem either to avoid Undo transactions altogether, or keep them enabled but Skip during automatic cleanup on save.
I have installed visual studio ultimate 2012 for windows 8 store apps but it doesnt show JavaScript in the new project.
The setup is good, i have installed it before using the same setup but i dont know what is the problem now..
I have also tried Visual studio Express, but got the same issue.. And one more thing BLEND is also not working in both the cases.
Are you looking in the right place? They can be 'hidden' in "Other Languages"
Search in the upper right hand corner of "New Project" for javascript to be sure.
Make sure you are up to date as well on the following updates as good measure
http://support.microsoft.com/kb/2797912
http://www.microsoft.com/en-us/download/details.aspx?id=38188
After uninstalling the current VS and then deleting all registries and finally installing Vs 2012 ultimate, fixed the issue.