Looking to build an email list for your product or service? Try my new Email Marketing Tool - Listomo

Additional menu

DONN FELKER

Lessons Learned From the Software Industry

Visual Studio Project MSBuild Import Error Fix

posted on by

If you get this error:

Unable to read the project File <path.to.project>.csproj.

C:\<path>\<to>\<projecct>\Project.csproj 77, 11): The imported project “C:\Microsoft.CSharp.targets’ was not Found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.

As shown in this screen shot …

image

 

Take a look at your project file. Open it in a text editor (such as NotePad++) and look for the import statement.

Mine looked like this:

clip_image001

 

How to fix

Change the MSBuild Property $(MSBuildToolsPath) to $(MSBuildBinPath) and the project should load.

Like so:

clip_image001[7]

Get posts like this in your inbox.

Everything I share on my site will get sent out to my email newsletter first. This includes new articles, any things I’m working on, early access and discounts to products/books/ebooks and more. If you want it early, hop on the list below.

What kind of stuff am I going to be sharing?

I will teach you about how to start freelancing and consulting from a software developer perspective, how to work for yourself, increase productivity, find clients and make more as a freelancer/consultant. I'll also share the lessons I've learned in over 20 years in freelancing and consulting that will save you time, money and frustration. I look forward to chatting with you via email.

Powered by Listomo

Reader Interactions

Comments

  1. Aaron says

    You are a life saver. I did not have this error opening the project in Visual Studio, but I had a similar error using MSBuild on our build machine. I think we are using an older version of MSBuild.
    s:….xxx.csproj (74, 11): The imported project “s:Microsoft.CSharp.targets” was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.

    I changed the MSBuild property you suggested and my build works now.

  2. Aftab says

    you can also use the /p switch to override the MSBuildToolsPath to specify the .net framework folder where the msbuild.exe is located:

    C:WindowsMicrosoft.NETFrameworkv2.0.50727msbuild.exe yourProject.vbproj /p:MSBuildToolsPath=C:WindowsMicrosoft.NETFrameworkv2.0.50727

  5. JD says

    Thanks for the short tip. 2 days of research later, the key was to open the file in notepad not visual studio. Much appreciated!

  6. Christian Edholm says

    For those of you who still have this problem: I myself am running VS 2015 and fixed this by deleting the Microsoft.Net.Compilers.1.0.0 folder. VS restored the folder when i opened the project and it was able to load the project.

Leave a Reply