I'm wondering why my Visual Studio missing "Remove unused references" on right click menu project and references both.
Please Don't tell me try Migrate packages.config to PackageReference, I just did it, but nothing change.
First of all you need to have an SDK style csproj like it is said here.
Example:
<Project Sdk="Microsoft.NET.Sdk"/>
Second, you must have it enabled like #Stan1k mentioned in his answer:
Microsoft says that the feature is off by default. You need to enable it from Tools > Options > Text Editor > C# > Advanced tab > Show "Remove Unused References" command in Solution Explorer (experimental).
And finally make sure you you run dotnet restore in the project console and build the projects (this was the issue for my why it was not showing).
Do you have an older Visual Studio Version? This Feature got released with Version 16.10.
Also notice this statement from the article
Microsoft says that the feature is off by default. You need to enable it from Tools > Options > Text Editor > C# > Advanced tab.
The option appears in Options>C#>Advanced and is on. When you right click on project the option does not appear making me think all references are being used. Perhaps depends on the project.
This utility was available for VB projects up until around VS2015 I think, maybe VS2013, then it got removed or limited for some reason. I've never seen it available in C# projects. And now it's not even available for VB unless your have an SDK project type. It's a bit ridiculous because often downgrading a NuGet package (eg RestSharp) will leave a load of "reference rubble" which you have to (carefully) clean up.
As an aside, whenever I install a new version of VS, it seems that much of their effort goes into UI look and feel rather than actual functionality improvements. Quite frustrating.
I recently changed operating systems on my laptop (went from 8.1 to Windows 7). I transferred my game project, and after having to rebuild it (due to Visual Studio 2013 stating it cannot open my project file), I managed to get it to run, but as soon as the code tries to load my cube.fbx model, I get the error in the title.
My settings for the model are as follows:
And the code for loading (which worked flawlessly before the transfer) is as follows:
modelCube = content.Load<Model>("Models/cube");
I have no idea what the issue is. All help points to setting the Build Action to "Content" and the Copy to Output Directory to "Always". The only clue I can think of is that originally, my project was made for Android, and on this iteration I remade it as a normal Windows project (as for whatever reason, I couldn't get an Android project to work this time).
Thanks in advance. This is really confusing.
While I doubt anyone else will have this problem, I figured out the issue. I think Monogame changed the way it loaded assets since the last time I used it. With my install of a newer version, I just had to follow the link below to get it working again.
http://rbwhitaker.wikidot.com/monogame-managing-content
I copied my grails app to another computer and now .gsp files do not open in the editor. They also show a G icon with an arrow next to them. Dragging and dropping or double clicking do nothing. Updating intellij didn't help either
As Dónal mentioned, Grails is not one of the frameworks supported by IntelliJ IDEA Community Edition (you need the Ultimate Edition). You can view the feature comparison here.
Hi I am probably answering now when u no longer need the answer but I bumped into the same issue yesterday and only solved it now. There are chances that you associated the .gsp file type with a program which cannot be opened by intellij in your case GOSU. To fix it go to: File>Settings>Editor>File Types
In the file types go to Gosu Program Source and *.gsp should be in the registered patterns. Remove it and apply changes then you are good to go.
Re-installing community version fixed and gsp files now open in the editor
I'm working with an ASP.NET MVC project that seems to be having some issues when attaching to the IIS process (w3wp.exe). I'm running the solution and IIS 8.5 on my own local machine so I wouldn't think that this has anything to do with our network. What's strange to me is that I'm able to hit the breakpoints on any other solution I debug locally.
The issue I'm having exactly is that the breakpoints turn to red, hollow circles and never get hit. Usually the fix for this is a Clean/Rebuild of the solution but this hasn't worked. I've confirmed the code is being updated by adding "throw new Exception" to a page and ensuring it shows the exception. Again, this problem is only happening with this one solution. Any other solution I run the debugger with works fine. I've also tried restarting the app pool, the website, IIS, and also my computer.
A few of the articles I read mentioned that anti-virus programs can block a remote debugger from accessing the process. However, the entire setup is contained on my local machine so it doesn't sound like that would be the issue. It does concern me a bit though because we recently hired a new IT guy that's been making a lot of changes to everyone's machine.
One other point to add that's unique about this web application is the binding in IIS. The binding is "*" in order to leverage some custom functionality related to subdomains.
In the meantime, I'll continue to look for a solution but if anybody has any ideas what may be causing this one solution to not debug properly I'd really appreciate it.
EDIT: Found a solution that suggested deleting the ASP.NET temporary files. No luck.
Solved. Ended up being an incorrect configuration selected in the debug menu. I had mistakenly switched it to a release configuration that could not load the symbols for the document. Switched it to a debug configuration and the breakpoints hit just fine now.
To add on to what Abacus mentioned below, it could also be a web.config transform that is messing with your build. In our case, we have Release configurations that remove the debug attribute from the web.config's compilation section. Below is a screenshot of an example and Visual Studio's dropdown list of build configurations.
NOTE: Also make sure your Platform is correct along with the configuration. In my case, Dev.Debug|Mixed Platforms does not correctly build the solution but Dev.Debug|Any CPU will.
I struggled forever trying to fix this. Finally this is what did it for me.
Select Debug->Options->Debugging->General
Tick Enable .NET Framework source stepping.
(This may be all you need to do but if you are like me, you also have to do the ones stated below. The below solution will also fix errors where your project is loading old assemblies/.pdb files despite rebuilding and cleaning.)
Select Tools -> Options -> Projects and Solutions -> Build and Run,
Untick the checkbox of "Only Build startup projects and dependencies on Run",
Select Always Build from the "On Run, when project are out of date" dropdown.
Enable 'Managed Compatibility Mode'. Go to Tools->Options->Debugging and enable Managed Compatibility Mode.
In my case this solution is useful:
Solution: Disable the "Just My Code" option in the Debugging/General settings.
Reference: c-sharpcorner
I know this is not the OPs issue, but I had this happen on a project. The solution had multiple MVC projects and the wrong project was set as startup.
I had also set the configuration of the project(s) to just start process/debugger and not open a new browser window.
So on the surface it looks as if the debugger is starting up, but it does so for the wrong process. So check that and keep in mind that you can attach to multiple processes also.
Silly mistake that left me scratching my head for about 30 minutes.
The issue was resolved by unchecking the
Properties > Build > Optimize Code
setting on the web page properties screen (under General).
Right click on your project, then left click Properties, and select the Web tab.
Verify whether the correct server is selected for your case:
IIS Local
IIS Express
Go to Visual Studio Menu:
Debug -> Attach to Process
And then click the Select button, as in the image below:
Then make sure the "Automatically determine the type of code to debug" option is selected, like this:
One of my projects in my solution was set to Release mode. I changed it back to Debug mode, and the breakpoints are hitting now.
I had the same issue in a Xamarin.Forms project. The fix was manually converting the PCL from .NET 4.6 to .NET Standard 2.0.
For Visual Studio Mac: make sure you do it for each project
In Visual Studio 2017 you need to make sure you're not in release configuration mode.
Open the build menu ddl
Click configuration manager
Change from 'release' to 'debug'
In my scenario, I've got an MVC app and WebAPI in one solution, and I'm using local IIS (not express).
I also set up the sites in IIS as real domains, and edited my host file so that I can type in the real domain and everything works.
I also noticed 2 things:
The MVC code debugging was working perfectly.
Attaching to process worked perfectly too. Just when I was debugging it didn't hit the breakpoint in my API.
This was the solution for me:
Right click webapi project > properties > Web > Project URL
By default it points to localhost, but since I set up the site in IIS, I forgot to change the URL to the website domain (i.e. instead of locahost, it should say http://{domain-name}/).
If anyone is using Visual Studio 2017 and IIS and is trying to debug a web site project, the following worked for me:
Attach the web site project to IIS.
Add it to the solution with File -> Add -> Existing Web Site... and select the project from the inetpub/wwwroot directory.
Right-click on the web site project in the solution explorer and select Property Pages -> Start Options
Click on Specific Page and select the startup page (For service use Service.svc, for web site use Default.aspx or the custom name for the page you selected).
Click on Use custom server and write
http(s)://localhost/(web site name as appears in IIS)
for example: http://localhost/MyWebSite
That's it! Don't forget to make sure the web site is running on the IIS and that the web site you wish to debug is selected as the startup project (Right-click -> Set as StartUp Project).
Original post: How to Debug Your ASP.NET Projects Running Under IIS
In my case I had a string of length 70kb. Compiler did not thrown any error. But Debugger failed to hit the break point. After spending 3 hours and scratching my hair I found the cause for not hitting the break point. After removing 70kb data break point worked as normal.
If none of the above work, double-check your code. Sometimes the reason why the breakpoint appears to not be hitting is due to the block of code containing the breakpoint is not being executed for sometimes inadvertant reasons.
For example, forgetting the "Handles Me.Load" has gotten me a few times when copying and pasting code:
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)
--this block of code will not execute
End Sub
vs
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
--this block executes
End Sub
You can't hit breakpoints while attached to IIS process if you haven't logged into your Microsoft account in VS2017.
In my case the actual process was different from the original started process.
Usually we bind the local-hosted services through the w3wp.exe process. In my case a custom process was used. Changing to that solved the problem.
One more thing, change from Release to Debug mode. In release mode PDB files are not getting updated with breakpoints details. So make sure you are debugging your application in Debug mode.
Right click on your project, then left click Properties, and select the Web tab.
Debuggers > ASP.NET
My case is not mentioned here:
I have to run the web project on a fake domain (settup on IIS and /hosts/etc) because of the callbacks from a third party site.
I was seeing two w3wp processes in the process list of VS:
w3wp.exe User Name: IIS APPPOOL\Default app pool
w3wp.exe User Name: IIS APPPOOL.svc
I had to to manually attach to second one to be able to debug.
So I realised the app pool of my Fake domain in iis is not set to "Default app pool"
https://manage.accuwebhosting.com/knowledgebase/2532/How-to-change-application-pool-from-IIS.html
As soon as I changed the domain's app pool to the "Default app pool" visual studio started to debug the web app.
If any of your components are Strong Named (signed), then all need to be. If you, as I did, add a project and reference it from a Strong Named project/component, neglecting to sign your new component, debugging will be as if your new component is an external one and you will not be able to step into it. So make sure all your components are signed, or none.
It might also be (which was the case for my colleague) that you have disabled automatic loading of symbols for whichever reason.
If so, reenable it by opening Tools -> Options -> Debugging -> Symbols and move the radiobutton to "Load all modules, unless excluded"
In my case with 20+ projects in one solution, I included the project (I would like to debug) in the solution startup
Right-click solution-->Startup Project->Multiple startup projects->For project you want to debug select "Start" in action.
Now you should be able to hit those break points, especially projects which may be helper classes.
in some cases the cases the problem is in IIS. if your debug worked and suddenly stopped working , use IISReset to reset the IIS thread-pools.
I hate to admit missing something so simple, but hopefully this will help someone else. In my case, I am using local IIS and the website is running on an application pool, so when you attach the debugger to a process, be sure to checkmark "Show processes from all users" so that you can select the appropriate process.
In my case , changing Solution Platform from x86 to Any Cpu solved the problem.
I just ran into this problem. What worked for me was to change Active Solution Platform to x86 instead of AnyCPU;
Click Build
Click Configuration Manager
Select x86 from the Active Solution Platform Combobox.
Just another reason why breakpoint might not get hit: I replaced the reference to the DLL by a reference to the project. Upon build, no PDB file got created and so no breakpoint got hit. The Problem was that I forgot to do the same with the other projects in the solution. After replacing the references (DLL >> project) in all projects, the PDB got created and breakpoints worked like expected.
click on Debug.
Select [Debugging].
Select the [General].
Disable the "Just My Code"
Click [OK] and rebuild the project.
To delete project's bin and objects folders may be helpfull
Another reason a breakpoint might not be hit is that you are not debugging the site that you think you're debugging, due to anomalies in your site links. Case in point: Assume, when starting the debugger, that it normally launches a localhost page (as shown in the browser address bar). If reaching the breakpoint code entails first clicking a link on that localhost page to go to a different page, you must ensure the browser is still pointing to localhost after the click. If it's not, then your breakpoint will never be hit and you have to fix your links first. Kind of an obvious problem, but easy to overlook.
I'm working on an ASP.net mvc project in Visual Studio 2012. Came across this issue, which is incredibly annoying when debugging my application. Say that I have n number of files open in my editor whenever I build and start a debug-session using F5. Ok, so the editor closes all the open documents as usual, and I do my debuggig tasks. Now; when I stop debugging and want to re-open the files that I had open earlier, I'm not allowed to do so. Nothing whatsoever happens when I click these files, until I restart VS2012.
If I close all of my open documents before debugging, opening them after works fine and the way it's supposed to. Also, this is the case for all of my new or existing projects. I run with ReSharper 7.1.2 installed.
Has anyone encountered this issue before?
To stop ALL files from being closed after debugging simply go to
Tools > Import and Export Settings > Reset Settings
This will fix this bug, I have the old settings saved that caused this error but I am unsure what specifically causes it within the settings. After frustratingly searching around for a clear answer to this problem I hope this helps others that might have this issue.
Note, I also had your error in my instance of VS 2012 but had neither of your extensions. I would propose that uninstalling your extension removed the setting causing the error.
Did you tried cleaning the solution?
Go to Build then click Clean solution
After a bit of trial and error, I found that AnkhSVN was causing the problem.
Whenever I tried to check in (or out) the code, it caused some exception.
I have no clue, why this prohibited me from opening files after debug but it works after removing AnkhSVN.
I've got this issue as well. I wasn't able to solve it. In my case, the file was open but it was invisible. After debugging again with the file still open but "invisible" I got an error that the file doesn't exist when I navigated to the page (I faced this issue while working on an ASP.NET project).
I recommend reinstalling VS, in case you've messed with all the debugging and window settings.