Even a blanc uwp project is not able to build on visual studio 2017 15.8. Two minor versions have been released since 15.8.1 and 15.8.2 since than but they show the same problem.
Behavior : when you just try to restore nuget packages or build the project, the Build windows shows no output, i.e : it is black as if no progress is happening in build, and it remains like this for infinite amount of time, until you cancel the build, then it says "The Build has been canceled".
The other way is to trace your code to git and then you should close the VisualStudio and use git bash input the code.
git clean -xdf
This code can clean all of your temp files and then you can use VisualStudio to rebuild.
You can also use the new VisualStudio 2017 project to build your UWP code.
The new VisualStudio 2017 project is Microsoft.NET.Sdk that can use nuget in your nuget folder and it needs do not copy nuget to the local folder.
See How to: Reference an MSBuild Project SDK - Visual Studio | Microsoft Docs
Old csproj to new csproj: Visual Studio 2017 upgrade guide
I fixed it with following steps:
delete obj and bin folders from the project.
Restart visual studio
Clean Solution.
Rebuild.
Related
I was developing my WPF projects using Visual Studio 2013 in my old window 7. But when I installed new Windows 10 and also Visual Studio 2017 and tried to open my project; my project fail to load and got this error message:
the imported project "C:\Program Files (x86)\Microsoft Visual
Studio\2017\Enterprise\MSBuild\Microsoft\Expression\Blend.NETFramework\v4.5\Microsoft.Expression.Blend.WPF.targets"
was not found. Also, tried to fiend
"Microsoft\Expression\Blend.NetFramework\v.4.5\Microsoft.Expression.Blend.WPF.targets
in the fallback searchpath(s) for $(MSBuildExtensionsPath) -
"C:\Progam Files (x86)\MSBuild" . These search paths are defined in
"C:\Users\AdminPC\AppData\Local\Microsoft\VisualStudio\15.0_51bebed7\devenv.exe.config"
. Confirm that the path in the declaration is correct , and
that the file exists on the disk in one of the search paths.
C:\Users\AdminPC\Documents\Visual Studio
2013\Projects\MyCustomMessages\MyCustomMessages.csproj
I Searched for some solutions I found I have to install BlendWPFSDKv4_en.msi Version 4, but still doesn't help also there is no BlendWPFSDKv4_en.msi version 4.5. What Should I do, Shall I install VS 2013 in order to fix this issue?
The imported project C:\…\v4.5\Microsoft.Expression.Blend.WPF.targets" was not found
Found it. You should launch the Visual Studio Installer from the start menu, switch to the "Individual components" page, under the "SDKs, libraries, and frameworks" heading, find the "Blend for Visual Studio SDK for .NET" and install it:
After the installation is complete, you will find it under the path:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\Expression\Blend.NETFramework\v4.5
Certified:Visual Studio 2017 - What happened to Expression interactions?
Hope this helps.
You can remove the reference to blend;
With VS 2019 - Right click on the (unloaded/load failed) project.
Select - edit your *****.csproj file.
At the bottom of the file, remove the following line
<Import Project="$(MSBuildExtensionsPath)\Microsoft\Expression\Blend\.NETFramework\v4.5\Microsoft.Expression.Blend.WPF.targets" />
Save, Reload the project & happiness.
I had solved the problem by installing
Install Microsoft Expression Blend Software Development Kit (SDK) for .NET 4,
without install an older version of VS
I had solved the problem by installing VS2015 in the same machine that has VS2017 and now the project works fine in VS2017.
I have a problem with autocompletion in VS 2017 Community.
Previously I had VS 2017 Enterprise from school, but the key expired so I moved to Community.
Before, everything works great, but now it doesn't work at all.
I found a solution on Stack Overflow here but it doesn't work, so found another solution at GitHub here.
And I got this:
Build FAILED.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1601,5): error MSB4036:
The "GetReferenceNearestTargetFrameworkTask" task was not found. Check the following:
1.) The name of the task in the project file is the same as the name of the task class.
2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface.
3.) The task is correctly declared with in the project file, or in the *.tasks files located in the
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin" directory.
0 Warning(s)
1 Error(s)
Time Elapsed 00:00:00.11
Do you know what to do next?
I had the same error message but for a different problem.
So, I'm using MSBuild to automate build/deploy process for Azure Functions. Everything was working fine until I updated both Visual Studio 2017 and Visual Studio Build Tools 2017 at which point I started getting this error. To be precise I got this error only when using MSBuild, building project manually from VS was working fine.
In my case I already had everything set as per #Programmer's answer.
But as I was using MSBuild it turned out that I also had to install NuGet targets and build tasks which are part of Visual Studio Build Tools.
Follow these to fix that error. This applies to VS 2017:
Fix 1:
1.Install Nuget PackageManager from here.
2.Restart Visual Studio.
If the problem is still there, continue below
Fix 2:
1.Download and start/run the Visual Studio Installer again.
2.While the Visual Studio Installer is still running, go to the "Individual Components" tab
3.Tick the "NuGet package manager" check-box that is under "Code tools" option.
4.Click Install to install it.
Screenshot of where this is located:
That should fix the error you see in this question. Restart Visual Studio and test the auto-completion function. If it's not working, see the answers from this question as that is a whole different issue.
I was seeing this issue with msbuild 15.6.82 on a build environment that does not have VisualStudio 2017, only VS Build Tools.
Here's a PowerShell script that resolves this issue, it pretty much does the equivalent of previous answers in the VS Installer, but silently and waiting for completion.
Start-Process "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe" -ArgumentList 'modify --installPath "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools" --quiet --add Microsoft.VisualStudio.Component.NuGet.BuildTools --add Microsoft.Net.Component.4.5.TargetingPack --norestart --force' -Wait -PassThru
I'm working with a headless build server on server core, resolved by installing chocolatey package choco install visualstudio2017-workload-webbuildtools from here:
https://chocolatey.org/packages?q=msbuild
I'm reporting an answer from a Microsoft techician
This usually indicates one of two things:
A failed VS installation. If that's the case, I would recommend running a repair on your VS install.
You have msbuild assemblies in the GAC. If that's the case, please ungac them.
Livar Cunha [MSFT]
I got the same problem in Visual Studio 2019, I solved it by simply install unity package
I installed .net core nuget package in order to create application based on this framework. When I create a solution in visual studio community 2017 in default vs projects folder everything seems to be ok, but when I change destination folder (or create new solution in different folder) then program cannot start because of bug: Assets file 'D:\c#\test\test\obj\project.assets.json' not found. Run a NuGet package restore to generate this file. Of course restoring doesn't help at all. Can you help me with this problem?
Visual Studio version 15.5.2, windows 10.
Regards.
I have Visual Studio 2013 Ultimate. Today when I opened it, it didn't load any of my solution's projects. Error message:
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- ETL_<Project name>, "<Project path></Project>.csproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
- <Project name></Project>, "<Project path></Project>.sln"
These projects are of types Class Library and Console Application. If I try to create a new project, these types are listed, but when I create it I get message <Project path> cannot be opened because its project type (.csproj is not supported by this version of the application. To open it, please use a version that supports this type of project..
So, Visual Studio is telling me it doesn't support a project it just created?! GJ M$!!
Unfortunately I was unable to solve this. I ended up uninstalling VS Ultimate. Now I use VS Express for Desktop, and it works with my old projects.
My assumption is that something on Windows broke some part of VS. I should have tried to uninstall and reinstall it but didn't have the opportunity.
I have the same thing in a Hyper-V VM. After repair did not work, I deinstalled and reinstalled VS 2017. Same thing.
In the host I can still open the same project with VS, so it is not the project, but the VS install that has a problem.
It puts this in the migration log:
src\DTOWEB\project.json: Failed to migrate XProj project DTOWEB. Could not find project.json at C:\DTOWeb\DTOWEB7\src\DTOWEB\project.json.
I have a second VM that is x86 iso x64, and it can open the project without problems. So again, my conclusion is there is nothing wrong with the project.
I have had a project in VS 2015 Update 3 with a lot of code logic behind. I upgraded it to VS 2017 RC successfully. The code implementation went on and on until getting to the point where VS 2017 RC exhibited a lot of issues and instabilities e.g. .Net Core DLL template removed! by installer or Resource file could not be compiled and so forth! I'd like to revert the solution back to VS 2015 to keep working flawlessly but it's impossible easily due to a lot of code implemented in VS 2017 excluding new Roslyn features. Any suggestions how to perform the downgrade?
You will also need to update your *.vcxproj files, to change the toolset referenced there to the one used by the earlier compiler.
What I found useful, is to create a small scratch project (just simple console app) in each version of visual studio, then use beyond compare or similar to contrast the .sln and .vcxproj files from each vs version. This will show you the toolset changes and maybe a few others that you need. For example going from vs 2017 to vs 2019 the toolset changes from 141 to 142.
So the lines
<PlatformToolset>v141</PlatformToolset> are for vs2017
and
<PlatformToolset>v142</PlatformToolset> is for vs2019
It's indeed a manual process and no there are no tools that can automate that.
I had the same problem and i fixed it using this solution:
1) create a solution of whichever project you want (winforms, etc)
2) browse to your project folder and find your .sln file.
3) open it using notepad.
4) copy the first 4 lines as shown
here.
5) find your .sln file for the project you wish to downgrade. for example : foo.sln (its found where your project is).
6) open it with notepad and paste the lines instead of the first 4 lines
7) save and open the sln. it should open it under visual studio 2015
i hope this works for you