After I've used a github UE4 version for a while now, I noticed that I wasn't able to build the engine again without having this error complaining about ShaderCompileWorker. Is there anyway to solve this?
Here is the error message after building the engine in Visual Studio 2019:
Related
I'm trying to set up a global environment for react native (I assume you can do this as opposed to setting up environments on a project by project basis)
I'm on windows 11 and I've just used chocolatey to download visual studio. I've installed visual studio community 2019, the latest version and I've uninstalled visual studio build tools, because I read somewhere that the package can interfere with pathing priority..
When I run the command below. I'm not entirely sure what it's meant to do. Is it setting up a single project or is setting up a suitable environment for the windows OS?
"Set-ExecutionPolicy Unrestricted -Scope Process -Force;
iex (New-Object System.Net.WebClient).DownloadString('https://aka.ms/rnw-vs2019-deps.ps1')"
Regardless, I get the error 'Checking Compilers, build tools, SDKs and Visual Studio: Failed' when I run in an elevated powershell terminal.
I have no idea how to trouble shoot this. The problem could be in build tools, sdks or visual studio..
I have added 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Community' to my global path.
I'm not sure where the most authorative voice on this is. I've read countless github forums from microsoft.
My original problem was a possbible unhandled promise rejection
Apologies if the problem is too broad, I've done my best to explain what I'm trying to achieve and the problem that I'm running up against, but honestly I do not know if this is even necessary as I'm able to use the create-react-native-app command without any problems, however there may be some issues later on if my environment isn't correct. It's just hard for me to know what those would be..
I recently used the repair function in my Visual Studio Installer that I thought could fix the error message: Microsoft data transformation services designer package did not load correctly. However it turns out there is a new error message when I wanted to load my previous project: The "Package" package did not load correctly.
If I continue the loading, I will receive some other warning message in the solution Explorer saying my project is "incompatible" and "the application is not installed":
I initially also tried to follow some online solution and tried to repair Microsoft SQL Server Data Tools in control panel. It doesn't allow me to repair and says Setup Failed almost immediately after I click on the repair button.
Initially I was trying to add an WCF extenion in Visual Studio but seemed failed and threw the first error message to me. Then when I try to repair, the first error message is gone and I was given the second error message. Now I stuck in there.
I have also checked if SSDT is included in the installer and New project types:
It seems the SSDT is selected in the Visual Studio Installer and all my current project types are listed in the screenshot as well (previously I was able to see Integration services as well but now after the repair I can't).
I'm using Visual Studio Enterprise 2017 on a test server that a few people have access to (I've also tried to restart the Visual Studio and the server but it didn't help).
Hope I can get some suggestions here, really appreciated.
I'm getting the following error when connecting to visual studio online with tfs plugin:
org.apache.axis2.databinding.AFBException: Unexpected subelement InheritLevel
It seems like it does connect to VSO and this problem occurs when its loading the project information. I'm using the alternate connection method, which is already enabled on VSO. How can I fix this problem or do I have to switch to eclipse?
The IntelliJ plugin for TFS is based on the 2010 api and is not well supported. As TFS and VS 2010 are now no longer supported I would expect breakages. Other than putting pressure on JetBrains to fix it you can:
use Eclipse that has fully supported first part plugin
Use the command line out side of IntelliJ
Nether will be what you want, but it may be the best that you can get without Jet Brains fixing it.
I just created a new empty universal app (windows 10) and checked it in on my visual studio online project.
The configured build is constantly failing on following error...
The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\WindowsXaml\v14.0\8.2\Microsoft.Windows.UI.Xaml.CSharp.targets"
was not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.
I set build configurations to use VS2015 but without any luck.
I keep thinking there's a simple configuration I'm missing here... but can it also be that it's not yet supported?
The project itself is just the standard template from Visual Studio.
I'm having a similar issue running with MSBuild 8.2 target missing under VS2013 Update 5 under Windows 10 TH1. Except my target is Microsoft.Windows.UI.Xaml.Cpp.targets. So not necessarily an issue with Visual Studio but rather the substitution for $(TargetPlatformVersion) in the targets definition:
<Import Project="$(TargetPlatformVersion)\Microsoft.Windows.UI.Xaml.Cpp.targets" />
I'm building a project from Microsoft (https://github.com/Microsoft/winsdkfb), so I don't think this is your problem (meaning you've not done anything incorrect).
I know this isn't an answer, but I suspect we're caught in a gap in the Windows 10 SDK & Tools. Those aren't scheduled to be complete and available until 29 July even though VS2015 has RTM'd. I tried to track down something in the VS2015 release notes without luck.
Just inform the solution I found on this thread.
At the time of writing, it appeared that VSTO serves were not yet updated with
the Windows 10 SDK.
The only way back then to make it run was by creating your own Build VM (through Windows Azure) and link it to your VSTO builds.
I posted the thread and got the answer on the MSDN TFS forum.
I have not tried it right now, but since Windows 10 is officially released now, I guess it may work out of the box.
We now support building Universal Windows Platform (UWP) projects on the hosted build service.
I am trying to build a sample Win8 app with Visual Studio Express 2012 for Windows 8. This sample was posted before the final release of Win8 and VS2012. I have changed all the callouts for "//Microsoft.WinJS.0.6/..." to be "//Microsoft.WinJS.1.0/..." yet I still get this build error: Could not find SDK "Microsoft.WinJS.Version=0.6", in file Microsoft.Common.Targets. The Error List says this file is at C:\Windows\Microsoft.NET\Framework\v4.0.30319\, but there is no such file there.
My other builds of JS apps I code from scratch work without a problem. How can I fix this old sample app?