You've already forked UnrealEngineUWP
mirror of
https://github.com/izzy2lost/UnrealEngineUWP.git
synced 2026-03-26 18:15:20 -07:00
7d6564285d
#jira UETOOL-4858 #rb JeanLuc.Corenthin #preflight 6267da64853fdb6fddb7cbf0 #lockdown jeanmichel.dignard [FYI] emil.kirichev #ROBOMERGE-OWNER: jeanluc.corenthin #ROBOMERGE-AUTHOR: emil.kirichev #ROBOMERGE-SOURCE: CL 19940216 in //UE5/Release-5.0/... via CL 19946838 #ROBOMERGE-BOT: UE5 (Release-Engine-Staging -> Main) (v943-19904690) [CL 19952412 by jeanluc corenthin in ue5-main branch]
// Copyright Epic Games, Inc. All Rights Reserved. Since the Datasmith Revit Exporter is programmed in C#, the standard build process just runs a post-build step to build in batch the release configuration of Visual Studio C# project file DatasmithRevit<year>\DatasmithRevit<year>.csproj. To develop the C# code, it is preferable to directly open DatasmithRevit<year>\DatasmithRevit<year>.csproj in Visual Studio. The Visual Studio C# project automatically includes all the Datasmith Revit Exporter C# files from project directory Private and all the Datasmith Facade C# files from directory Enterprise\Binaries\Win64\DatasmithFacadeCSharp\Public. Outside of Epic Games, environment variable Revit_<year>_API must be set to the Revit API third party directory on the developer's workstation. Inside of Epic Games, when opening the Visual Studio C# project directly, environment variable Revit_<year>_API must be set to the developer's Perforce workspace directory Enterprise\Source\ThirdParty\NotForLicensees\Revit\Revit_<year>_API. At this time, <year> can be in the range [2018..2022].