Menu
Sometimes, VS wont let me do edit and continue, and it turns out it's because my project Eric.Controls has a reference to Eric.Controls. It's a project reference, which I never added. Steps to reproduce are inconsistent, but generally, i think it happens when I use the designer and add a control from a different project which I reference.
This occasionally also causes me to be unable to compile at all until I restart Visual Studio which has the target executable locked.
First of all, why would VS even allow a project to reference itself?
Any ideas?
I'm happy to answer any questions which could lead to an answer.
230
To fix a broken project reference by correcting the reference path. In Solution Explorer, right-click your project node, and then select Properties. The Project Designer appears. If you're using Visual Basic, select the References page, and then click the Reference Paths button.
SOLUTION. When you add your first test to a new test project in Visual Studio, references to the required assemblies are automatically referenced. By default, Visual Studio references assemblies stored in the GAC (Global Assembly Cache) with their specific version number.
A reference is essentially an entry in a project file that contains the information that Visual Studio needs to locate the component or the service.
Yeah, I've noticed this too. It is is a visual studio bug: http://connect.microsoft.com/VisualStudio/feedback/details/613502/automatically-add-self-reference
It happens when you drag something onto a designer from the toolbox. To work around it just delete the self reference.
151
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
