Building with .net framework 4.8 #80
Replies: 1 comment 42 replies
-
That's unfortunate :( I gave it a try myself, I ran into a few issues but they were easy to fix, however I couldn't reproduce your build error. Have you tried this command: |
Beta Was this translation helpful? Give feedback.
42 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, I am trying to decompile some files for Endwar which is based on UE3 and so I tried to open the .upk but I am getting some errors so I tried building the projet and debugging locally with vscode to see if I could figure out what is going on and maybe add support for the game if I figure it out.
I tried building with vscode at first but it seems to use dotnet cli which is not the way the .net sdk framework 4.8 works. It uses MSBuild (thanks MS for making this so confusing)
So I finally figured that running with the command
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\msbuild "E:\Development\UDK\UE-Explorer\UE Explorer.sln"
would allow to build with your specific .net version but I am getting an error from MSBuild that all of the .csproj are not supported by MSBuild. Does this ring any bell?
I am also getting errors like:
E:\Development\UDK\UE-Explorer\UELib\src\Eliot.UELib.csproj(1,1): error MSB4041: L'espace de noms XML par défaut du projet doit être l'espace de noms XML MSBuild. Si le projet a été créé au format MSBuild 2003, ajoutez xmlns="http://schemas.microsoft.com/developer/msbuild/2003" à l'élément <Project>. S'il a été créé dans des formats anciens comme 1.0 ou 1.2, convertissez-le a u format MSBuild 2003.
which seem linked to the issue. Saying something like the default XML project namespace must be the MSBuild namespace. I tried adding the xml element above but I am getting more errors.
Maybe you ran into such an issue before?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions