Ye gads, another error!

[Thunderbirds747]

G'day mates,
While I was researching how to make an error-free code, I ran into error MSB4062: The "VCMessage" task could not be loaded from the assembly Microsoft.Build.CppTasks.Common, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a. Could not load file or assembly 'Microsoft.Build.CppTasks.Common, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. I have tried to uncheck then check .NET Framework, but it didn't work.
Any suggestions?
Cheers,
Tim Williams.

[MollenOS]

This is caused due to corrupt configuration. I would advise you to clean your system from ANY visual-studio installations using Forced Uninstaller that microsoft provides to remove anything related to VS, then doing a full reinstall of visual studio

[Thunderbirds747]

Well, I guess I will have to do a code reset with GCC. The bootloader is already good, so I only have to reset the kernel to a cross-Windows and Linux style.

[Thunderbirds747]

The bug strikes back after copying several files in the MSBuild command prompt.
How do I fix it?

[dozniak]

Use a proper environment?

[Thunderbirds747]

Use a proper environment?

FYI, I used MSBuild to compile the OS with .NET Framework 4.0. While compiling I got MSB4062.

[MollenOS]

I have to agree with dozniak, use another environment than MSBuild or CI.exe. I currently use that environment with visual studio, and always have, but I would never recommend it. Use GCC instead through bash on windows using Developer Mode.

Or do as I already told earlier in this thread and perform a reinstall, it sounds like a corruption of the installation

[Thunderbirds747]

I have to agree with dozniak, use another environment than MSBuild or CI.exe. I currently use that environment with visual studio, and always have, but I would never recommend it. Use GCC instead through bash on windows using Developer Mode.

Or do as I already told earlier in this thread and perform a reinstall, it sounds like a corruption of the installation

Okay. It sucks that VS has to barf out errors while compiling. But with GCC, it all works!!!