I checked the means three times, Google didn`t tell me anything that really helps. I tested the whole thing by moving the sources to a test project called testprojgit, after checking and configuring the build, it immediately succeeded. How is this possible, do you have any advice? I suggested the underscores in the name, but in terms of name instructions, they are fine if they are not at the beginning of a name. The text was successfully updated, but the following errors occurred: `EnergyPlatforms.ESP.Business.Query.QueryPortfolioData.QueryUserAccount()` hides the inherited member `EnergyPlatforms.ESP.Business.Query.Query.QueryUserAccount()`. Use the new keyword if masking was planned. How did you call MSBuild from a Python subprocess? Did you specify the MSBuild path in the Python subprocess? I`m trying to restore a project from repo github.com/dnnsoftware/Dnn.Platform with a command like this: After searching for this bug in the Xamarin community, people mentioned resaving the file or changing the custom tool, nothing has really helped so far. C:Program Files (x86)MSBuildMicrosoft.Cppv4.0V140 I think that`s where the path comes from. I compared it to one of our various work projects that relies on vc140 and has no construction issues there. So I think our overall direction was not quite the right one. The problem lies elsewhere. And I`m back to square one! This happens because something in the Nuget pipeline is the path. » /. /.nuget » as an argument in the github.com/NuGet/NuGet.Client/blob/7463c26de6e6065a2b49d0ace20af973bca05968/src/NuGet.Core/NuGet.Configuration/Settings/Settings.cs#L832 method It enumerates the following directories [ « .
/. /.nuget », « . /.. », « . / », « »]. In the .Net Framework, calling Path.GetDirectoryName with an empty string as an argument will cause an exception with the text « The path is not of a legal form », so I propose to change the cycle condition from « root != null » to « !string ». IsNullOrEmpty(root) » So, if you upgraded the project files to vc140 using msbuild, you should use MSBuild from: with the full path (surrounded by quotation marks), also I run VS as administrator, According to the error log, it looks like you are using the old MSBuild, which comes from the .NET Framework, to build your project. Also, I see that you are getting the same error messages as me. Compiling a VC++ project with msbuild fails because VCTargetsPath. I don`t get an error when using the version in debug mode. I want to build the solution in release mode as well as in debug mode, the build size is quite large. @toast12 you are always welcome.
I`m glad to know that we found the reason and solution on MSBuild, but not for the Python subprocess. Sorry, I`m not familiar with Python, so I couldn`t give a direct solution on how to use the right msbuild of the subprocess. As I suggest, you can open a new thread with this last issue in the python forum or on stackoverflow with the python tag. More community members and MVPs in this forum can take a closer look at your problem and make more suggestions. MainPage.xaml.cs(15,13,15,32): Error CS0103: Name `InitializeComponent` does not exist in current context Edit: If you have NuGet 3.0, then this is the problem. Just update NuGet and everything should work. The following steps apply to NuGet 3.0, which is painful and error-prone. Do not go through such pain, choose the simple step, update your Nuget! What is this error that occurs when I try to create an app package? Microsoft Build Engine (MSBuild) is the build platform for .NET and Visual Studio.