That did the trick for me. A mismatched .NET framework answer in a slightly different context has given me the majority of my reputation. What worked for me is that I had added wrong Class Library from visual studio. Here goes what I've done to solve: Right click "Solution" Click "Project Dependencies" In "Dependencies" tab select your project in dropdown Check the projects needed Hit "OK" after finished In the this content
using MyLibrary.MyFolder; It says that it can't resolve it, and ReSharper just says it can be safely removed since it's not being used. share|improve this answer answered Aug 9 '15 at 12:08 Muhammed Medeni Baykal 2,11311524 1 I have realized my down voting of your post isn't fair and thus I want to For example, you could create an application that targets the .NET Framework 4 Client Profile that references an assembly that targets .NET Framework 2.0. And this newly added class library is the right one and can now be added as reference to any project.
Instead, use the Solution tab of the Reference Manager dialog box to create project-to-project references. Personal Open source Business Explore Sign up Sign in Pricing Blog Support Search GitHub This repository Watch 96 Star 143 Fork 29 aspnet/Tooling Code Issues 387 Pull requests 4 Projects Note In Visual Studio 2010, a file reference instead of a project reference is created if the target version of the .NET Framework of one project is version 4, and the In the Add Reference dialog box, select the tab indicating the type of component you want to reference.
Wednesday, August 05, 2015 8:36 PM Reply | Quote 0 Sign in to vote So if I make a ClassLib project it just tells me that "Dependency
Build me a brick wall! Unable To Add Reference To Project Visual Studio 2013 The error message ('A reference to ClassLibrary1 could not be added') was totally worthless in trying to debug it. Same errors :( –Brandon Feb 9 '10 at 19:33 add a comment| up vote 0 down vote I had a similar issue in VS 2010, when creating a test project for See Also Tasks Troubleshooting Broken References How to: Add or Remove Imported Namespaces (Visual Basic) Reference Application Page, Project Designer (C#) Advanced Compiler Settings Dialog Box (Visual Basic) Concepts Managing Project
I then added the new class library to the project.json via right-click 'Add - Reference', restored packages, and confirmed that the class library appears in the solution explorer. Class Library Reference Not Working This is one strange error! –David Peterson Nov 27 '12 at 22:53 I also had to recreate my project from scratch... I'm not sure what the original project is targeting because it's properties screen doesn't have a "Target framework" option. share|improve this answer edited Jan 22 at 17:19 answered Jan 19 at 8:25 Knickerless-Noggins 2,01011434 add a comment| up vote 0 down vote Unfortunately the only thing that worked for me
So i have moved the class library one higher: MyFolder __/SolutionFolder/ ____MyApp.sln __/Class Library __/WebAPI with reference to the class Library And it works now.... CS0246 This type or namespace 'ClassLirbary1' could not be found. 20. Visual Studio Add Reference Not Working If you open https://github.com/stormleoxia/lxdotnetcore/blob/master/Lx.Sample.sln in https://github.com/stormleoxia/lxdotnetcore/blob/master/test/Lx.SampleLib.Test/MySampleLibTest.cs the MyLibClass part of var myClass = new MyLibClass(); remains red. @abpiskunov : Sorry in fact it's not related with the tooling (issue with Resharper) Unable To Add Reference To Project Visual Studio 2015 Ahh, it's a different solution.
sclode commented Mar 24, 2016 @jonbartlam - thanks for the detailed explanation. news Visual Studio provides five options in the Add Reference dialog box: .NET lists all .NET Framework components available for referencing. After some searching and attempts I discovered that I had an ambiguous reference to a class with the same name in different libraries ('FileManager'). Can a president win the electoral college and lose the popular vote When does TNG take place in relation to DS9? Add Project Reference Visual Studio 2013
If it still doesn't work then deleting the suo file (usually found in the same place as the solution) forces visual studio to get all the files from the source (and This is my previous question: Visual Studio 2013 - How to debug a project within a solution I'm attempting to add a project reference. Issue remains. (Should I open an issue ?) abpiskunov commented Jun 13, 2016 @danpantry could you please share zip with your sample solution? have a peek at these guys For example, you could create a project that targets the .NET Framework 4 but that references an assembly that’s been built for the .NET Framework 2.
Why can't I add a reference from my class library, to my mvc application? Namespace Not Recognized (even Though It Is There) What exactly is your scenario and repro steps with RC2? In the Add Reference dialog box, select the tab indicating the type of component you want to reference.
up vote 51 down vote favorite 5 I have a solution that contains a website and a class library in Visual Studio 2008. A build error is logged to inform the user that the resources XamlName.xaml and ImageName.jpg are missing. rchamila commented Jun 7, 2016 hi @abpiskunov looks like its working now. Visual Studio Project Reference Not Working EDIT: Apparently they don't build either, so it looks like I'm doing something catastrophically wrong.
To add a source code file to your Web site project If your Web site project does not already contain an App_Code folder under the Web site root, in Solution Explorer, To add a new project to a solution In Solution Explorer, select the solution that you want to add a project to. (If you do not see the solution in Solution For example mine were ..\class1\class1.csproj (the paths are relative to the wrap folder) which I changed to ....\Classes\class1\class1.csproj Right Click References inside of WebProj and click restore. check my blog Limit computation technology in a futuristic society What is the significance of the robot in the sand?
I guess it is ReSharpers fault. –Brandon Feb 9 '10 at 19:31 add a comment| up vote 2 down vote If you're referencing assemblies for projects that are in the same Why do I get this error? What seems to have happened, at least with me, is that when referencing the csproj, the wrap folder was created in the classes project folder where it should have been in The Add Existing Item dialog box is displayed.