unreal engine development using vscode without vs2019, 2017 - visual-studio-code

I'm wondering if I can make a C++ project in unreal engine without visual studio 2019, 2017 etc.
Currently I just use vscode. Is it necessary to install visual studio?

You can use visual studio code but you would need some compiler to compile your C++ project. For that the MSVC compiler that visual studio supports is often used. You can download the MSVC compiler and use visual studio code with it. when you create your project with visual studio code will generate a .vscode folder. In this folder you will have a
task.json [ for generating the build scripts you need to compile your program and create the exe files]
Launch.json [ for debugging your C++ classes]
Properties.json [ for finding the MSVC compiler ]
Unreal engine has a button in the editor that will compile your code. This equivalent to running
cd " Where you have your engine installed"
"Engine\\Build\\BatchFiles\\Build.bat" YourProjectNameEditor Win64 Development "C:\ThePathToYourProject\YourProjectName.uproject" -waitmutex
Visual studio provides other build task such as a DebugBuildGame and ShippingBuild
Visual studio code also provides these build task through task.json file, but it does not work out of the box
I ended up making a video about this and timestamped important events
https://youtu.be/fydvKedIxKk
You want to consider fixing the task.json if your want to run any build other than the editor one.

Related

How to set the icon of a c++ console application from Visual Studio Code

Previously I used to use Visual Studio 2019 for building my software and setting an icon in Visual Studio is easy. But due to some problem, we shifted to Visual Studio Code and Cmake to build my project. But now I cannot set the application icon. Please help.

Set make as project builder in Visual Studio Code

I have created simple Cmake project in Visual Studio Code. As default Cmake extension generates Ninja build system files. How to switch build system from Ninja to Make?
There are 2 possibilities to solve it:
Either you resolve by installing a relatively new Makefile tools extension in your Visual Studio Code.
Or may be you need to resolve caching issue.

VS Code editor intellisense doesn't work with UnityEngine.UIElements namespace

I can't get any types under UIElements to be picked up by Omnisharp when using VS Code or Vim. I've tried with a minimal project (clean 3d template) with Unity version 2020.3.20f1, Visual Studio Code Editor (Unity package) version 1.2.4, UI Toolkit version 1.0.0-preview.18. I've followed the guide here to get the correct compilation order of packages.
Build still works fine, but the editor's intellisense throws squiggles under all UIElements types (e.g. VisualElement, UIDocument).
Change the external script editor (Preferences > External Tools) from Visual Studio Code to Visual Studio Community 2019, then regenerate project files. This seems to work around whatever the issue with Unity is.
Downgrade to Visual Studio Code Editor v1.2.3. I have the same issue with .4

Open source file from NUnit's GUI Test Runner

Is there a plugin or configuration option that will open a source file in Visual Studio when the relevant line is clicked in NUnit's GUI test runner? It displays it in NUnit, but that still leaves me searching for the file in Visual Studio to actually fix the error.
You can use http://nunit.org/index.php?p=vsTestAdapter&r=2.6.2
NUnit adapter for integrated test execution under Visual Studio 2012
(all updates),and Visual Studio 2013 (all updates). Compatible with
NUnit 2.0 through 2.6.3.
Download

How do I create a deployment package for CodedUI Tests recorded in Visual Studio 2010 beta?

A few test scenarios have been recorded using CodedUI test template for my web application in Visual Studio 2010 beta. These run from within the Visual Studio successfully without any issues. I was looking for instructions to create a deployment package.
Configure an environment with a "standalone" MSTest
A series of new test tools is being introduced with Visual Studio 2010. Team Agents provides a very small footprint and includes MSTest (it will be installed in a Visual Studio path).
C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\mstest.exe
You can copy the contents of your test project(s) bin\ directory to the machine with Team Agents installed and execute MSTest against your test container.
mstest /testcontainer:x:\test-project\automated-tests.dll"
Coded UI tests use namespaces within libraries that are part of Visual Studio e.g. Microsoft.VisualStudio.TestTools.UITesting
This is unlike UI Automation which is part of the core .NET framework e.g.
System.Windows.Automation
Therefore as I understand it you cannot package Coded UI tests to run in an environment that does not have Visual Studio installed.