JetBrains.ReSharperCpp.RiderPlugin Defines a bundled plugin which drives adding the referenced packages as a plugin for Rider. Supports classes, structs, enums, functions and global/class member variables For some reasons UCLASS() macro gets split between MacroCall ("UCLASS") and CppUE4Metadata ("()") nodes. This method finds an actual node before which the doc comment could be inserted ("UCLASS" identifier) Node before which a comment should be placed Actual comment node True, if ue4 metadata macro is present Handle situations when something goes wrong and comment node appears to be part of DeclarationSpecifiersNode to prevent spamming comment nodes (in situations like ) Finds a node, before which we can insert a comment node. Skips all the meta-macroses until the next line Whether message is an error Removes text formatting (CSI sequences) from the incoming text Similar to RadProjectHost with specifics for Rider. The actual interactions go as follows: - Rider starts opening a CMake project on a frontend. - Rider creates CMake project/solution marks on a backend. - Rider backend sends a request to the frontend to start opening a project. The backend thread will be blocked until the project snapshot is received from the frontend. - Frontend sends compilation arguments; we unblock the thread doing the async project load on the backend in return. - We recursively add all files from content roots to the project model so they would show up on the frontend. - We start watching for file system events in content roots so we could add new files on-the-fly. Similar to RadProjectHost with specifics for Rider. The actual interactions go as follows: - Rider starts opening a CMake project on a frontend. - Rider creates CMake project/solution marks on a backend. - Rider backend sends a request to the frontend to start opening a project. The backend thread will be blocked until the project snapshot is received from the frontend. - Frontend sends compilation arguments; we unblock the thread doing the async project load on the backend in return. - We recursively add all files from content roots to the project model so they would show up on the frontend. - We start watching for file system events in content roots so we could add new files on-the-fly. mirror of CLionWorkspaceModelRootsBuilder#addContentRoot logic parent of each external file is included as a root, but they merge if they are prefixes of each other Similar to RadProjectModelHost with specifics for Rider. While it doesn't actually reload any project it clears some ReSharper/C++ caches when new file is added (or removed) to project model via user action. Creates a project descriptor for the backend project model. Adds only (C++) files from the specified snapshot. Used for projects, which do not have correct configuration for current solution configuration Only for debugging purposes. Loads `rscpp-snapshot.yaml` projects. See documentation of CppProjectSnapshot for more details. Project files which are stored in the same directory as the main project file and which should be added to the project view. Works when .uproject is opened. 1. Adds new files to the modules and plugins on the fly (when they appeared on the filesystem) 2. Adds new modules and plugins when they are created in the filesystem 3. Triggers project properties regeneration when target file is changed Returns true if specified project can contain Build.cs and/or Target.cs files Util component for initializing UnrealSolutionMark when opening .uproject Performs different diagnostic checks and fetches solution configurations Actual project model generation happens in UnrealProjectHost Util component for initializing UnrealSolutionMark when opening .uproject Performs different diagnostic checks and fetches solution configurations Actual project model generation happens in UnrealProjectHost In case of error returns null. Diagnostics will contain one or more errors. Otherwise engineRoot will be returned and Diagnostics will be empty. Set of paths which should not be traversed when looking for program Set of paths to .Build.cs files which are used by other C# programs. But their C++ code should not be loaded by Rider Set of filepaths to .csproj files or to folders which should always be included to the solution Entries expected to be from the same source root FolderPlugins Themed Icon generated identifiers: — identifier class, for use in attributes, XAML, and generic parameters; — identifier object, as a field in the identifier class, for use where an value is expected. `_rrrrrrrrrrrrr `"L\:``````````cc ((((((((((((((*:............(( 77..........................77 JJ--------------------------JJ zz--||||||||||||||||||||||--zz .V6Eqqqqqqqqqqq777777777777::[[ ~AKT*;;;;;;;;;OO????????zzzz::II 9#\!!!!!!!!!!!## TTtttt__22 DD============DD }}3333""jj 88************88 33eeee~~VV WWrrrrrrrrrrrrWW``````VVEEEE~~KK DB|cccccccccccBB``````ww;;;;;;66 =$OC7)))))))))$$mmmmmmmmwwwwwwww :2DQQQQQQQQQQQQ For details on Themed Icons and their use, see Remarks on the outer class. <Image Source="{icons:ThemedIcon myres:HuvanupThemedIconsThemedIcons+FolderPlugins}" /> <!-- XAML --> [Item(Name="Sample", Icon=typeof(HuvanupThemedIconsThemedIcons.FolderPlugins))] // C# Type attribute IconId iconid = HuvanupThemedIconsThemedIcons.FolderPlugins.Id; // IconId identifier object themediconmanager.GetIcon<HuvanupThemedIconsThemedIcons.FolderPlugins>() // Icon image for rendering FolderSettings Themed Icon generated identifiers: — identifier class, for use in attributes, XAML, and generic parameters; — identifier object, as a field in the identifier class, for use where an value is expected. ,************* `"r!-``````````rr cccccccccccccc\:````````````cc TT``````````````````````````TT 77..........................77 JJ--7eeeeeescccccccccccccc--JJ 55!"nk; _k2s[327TTTTTTTTT--}} `zhr)2h2- `fhjT*EEFJJJJJJJJ::xx y4=`````.~~-`````~44{{{{{{{{::33 ,7be;``(#t[#1``~3b4Vnnnnnnnn,,22 -rdw*``v6)L6C``/6dwk55555555""yy pmc.....,;!".....=mmVVVVVVVV^^kk -X#L7ede,'':2dk7rdAr~~~~~~~~~~XX `DD#d#8c--=8Dd#DDb9999999999999 :MMMMMM; For details on Themed Icons and their use, see Remarks on the outer class. <Image Source="{icons:ThemedIcon myres:HuvanupThemedIconsThemedIcons+FolderSettings}" /> <!-- XAML --> [Item(Name="Sample", Icon=typeof(HuvanupThemedIconsThemedIcons.FolderSettings))] // C# Type attribute IconId iconid = HuvanupThemedIconsThemedIcons.FolderSettings.Id; // IconId identifier object themediconmanager.GetIcon<HuvanupThemedIconsThemedIcons.FolderSettings>() // Icon image for rendering FolderShaders Themed Icon generated identifiers: — identifier class, for use in attributes, XAML, and generic parameters; — identifier object, as a field in the identifier class, for use where an value is expected. `_rrrrrrrrrrrrr `"?/:``````````cc ))))))))))))))*:````````````)) TT..........................TT JJ--------------------------JJ XXXXXXXXXXXXXXXXXXXX||||||||--ll 99 wwww wwww9977777777::{{ bb bbbb bbbbbbiiiiiiii::ff ddAAAA````AAAA````ddxxxxxxxx,,22 mmmmmm....mmmm....mm33333333""55 DD----DDDD----DDDDDDeeeeeeee^^aa DD::::8888::::8888DDkkkkkkkk~~PP 888888::::8888::::88;;;;;;;;;;XX MMNNNN""""NNNN""""MMwwwwwwwwwwww $$$$$$$$$$$$$$$$$$$$ For details on Themed Icons and their use, see Remarks on the outer class. <Image Source="{icons:ThemedIcon myres:HuvanupThemedIconsThemedIcons+FolderShaders}" /> <!-- XAML --> [Item(Name="Sample", Icon=typeof(HuvanupThemedIconsThemedIcons.FolderShaders))] // C# Type attribute IconId iconid = HuvanupThemedIconsThemedIcons.FolderShaders.Id; // IconId identifier object themediconmanager.GetIcon<HuvanupThemedIconsThemedIcons.FolderShaders>() // Icon image for rendering FolderUnrealEngine Themed Icon generated identifiers: — identifier class, for use in attributes, XAML, and generic parameters; — identifier object, as a field in the identifier class, for use where an value is expected. ,+++++++++++++ `_r!-``````````rr cccccccccccccc\:````````````cc ||``````````````````````````|| 77..........................77 JJ--cc8888888888cccccccccc--JJ ll--TTDD DDTTTTTTTTTT--ll [[:_kOmmmm mmmmmZ{JJJJJJJ::[[ dddddd2"``````````"2ddddwt{{::33 bb``bb``````````````bb`*bEff,,22 66.....................:6X22""ee KK--KK------------------KKVV^^kk VVVVVVVVT"-------------:Vj~~~~hh 44444XVjT^::::::::jj:=jk444444 .ruuuuuuuuuuuuux` For details on Themed Icons and their use, see Remarks on the outer class. <Image Source="{icons:ThemedIcon myres:SelafixThemedIconsThemedIcons+FolderUnrealEngine}" /> <!-- XAML --> [Item(Name="Sample", Icon=typeof(SelafixThemedIconsThemedIcons.FolderUnrealEngine))] // C# Type attribute IconId iconid = SelafixThemedIconsThemedIcons.FolderUnrealEngine.Id; // IconId identifier object themediconmanager.GetIcon<SelafixThemedIconsThemedIcons.FolderUnrealEngine>() // Icon image for rendering identifier class Loads the image for Themed Icon FolderUnrealEngine theme aspect Color. Loads the image for Themed Icon FolderUnrealEngine theme aspect Gray. Loads the image for Themed Icon FolderUnrealEngine theme aspect GrayDark. Loads the image for Themed Icon FolderUnrealEngine theme aspect RiderLight. Returns the set of theme images for Themed Icon FolderUnrealEngine. FolderUnrealProject Themed Icon generated identifiers: — identifier class, for use in attributes, XAML, and generic parameters; — identifier object, as a field in the identifier class, for use where an value is expected. ,/************ `_*!- rr LLLLLLLLLLLLLL=-````````````LL ))``````````````````````````)) TT``````````````````````````TT 77..Lr "rLLLLLLLLLLLLLLLL..77 ii--((c;`'((((((((((((((((--ii F3Jo#mbZ--ZwR#bX[777777777--FF Z#3:``~rJlL~.`:}#U}}}}}}}}::ff -Ay `:` ;! FAeCCCCCCC::33 uw,``*n!```77````'692222222__jj :Xz................rXKSSSSSS""VV (k;---:!73333J\:---_k3~~~~~~~~ZZ 7e;:"*2yPXXXXKy2r":~ey6666666666 `?C3[|, ,)F3f)- For details on Themed Icons and their use, see Remarks on the outer class. <Image Source="{icons:ThemedIcon myres:HuvanupThemedIconsThemedIcons+FolderUnrealProject}" /> <!-- XAML --> [Item(Name="Sample", Icon=typeof(HuvanupThemedIconsThemedIcons.FolderUnrealProject))] // C# Type attribute IconId iconid = HuvanupThemedIconsThemedIcons.FolderUnrealProject.Id; // IconId identifier object themediconmanager.GetIcon<HuvanupThemedIconsThemedIcons.FolderUnrealProject>() // Icon image for rendering Should be used as a fallback, when no target information is available Looks for the path on disk regardless of given case, works on all platforms. Unc paths are not supported. Throws if several entries match given path. The path to look for, should be absolute The path on disk if it exists. Null if not found.[CanBeNull] C++-related MSBuild known tags/values All constants are converted to lower case in order to ease lookup since MSBuild is case-insensitive Contains some common values which is expected by standard C++ preserver Some system .targets/.props files are using macro variable $(LangID) for referencing to some subdirectory. Basically, LangID is a generic identifier (and 1033 stands for English language). For us important fact is that xmls for C++ project properties are located in the subfolder with LangID based on C++ tools language. Since this macro is used only for project properties: - we will find all possible languages for project properties and - we will use either english language or language with lesser LangID Reads rules which describe view of project properties window. Doesn't cause IO operations if file was already read by this reader. NOT multi-threaded. Default Default Don't know what this is. Can be found in: folder.xml Represents main rule and any rule which extends it Default Rules is a data driven approach to describe what properties can be edited for specific project There are two approaches on where to place rules-related logic and data: either in R#-backend or in MSBuildTask. Currently such logic and data are placed in our backend. Placing it in R# backend has following reasons: - Rules are needed only for providing visual editing for project properties. So it makes sense to place them closer to the place where visual controls are created. - Though rules are "included" in MSBuild files (.targets/.vcxproj/...) they are just plain .xml/.xaml files. - It is easier to scope with project properties editing session when it is in backend. The minus of this approach: - Backend have to contains some logic related to MSBuild machinery (ItemTypes, Labels, ...) Value specified in project file Either inherited value (by project value) or currently active value (if project value is not specified) Not specified -- just and ordinary string See: https://docs.microsoft.com/en-us/cpp/build/reference/msbuild-visual-cpp-overview#support-file-directories and: https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuild-reserved-and-well-known-properties See: https://developercommunity.visualstudio.com/content/problem/251846/where-is-windows-sdk-installed-to.html https://stackoverflow.com/questions/35119223/how-to-programmatically-detect-and-locate-the-windows-10-sdk https://github.com/microsoft/microsoft-ui-xaml/blob/master/build/Install-WindowsSdkISO.ps1 __ProgramFiles__\Microsoft Visual Studio\20XX\Professional\Common7\Tools\vsdevcmd\core\winsdk.bat Holder for reflection information generated from ir.proto File descriptor for ir.proto Field number for the "key" field. Field number for the "prettyName" field. Field number for the "attr" field. Field number for the "attr" field. Field number for the "attr" field. Field number for the "attr" field. Field number for the "signature" field. Field number for the "record" field. Field number for the "isNullable" field. Field number for the "record" field. Field number for the "substitution" field. Field number for the "isNullable" field. Field number for the "irType" field. Field number for the "irTypeWithSubstitutions" field. Field number for the "irPrimitiveType" field. Enum of possible cases for the "irtype_type" oneof. Field number for the "intConstant" field. Field number for the "valueConstant" field. Field number for the "boolConstant" field. Field number for the "strConstant" field. Enum of possible cases for the "constant_type" oneof. Field number for the "value" field. Field number for the "value" field. Field number for the "attr" field. Field number for the "value" field. Field number for the "value" field. Field number for the "type" field. Field number for the "varRefExpr" field. Field number for the "constantExpr" field. Field number for the "unknownExpr" field. Field number for the "nullExpr" field. Enum of possible cases for the "expr_type" oneof. Field number for the "variable" field. Field number for the "location" field. Field number for the "const" field. Field number for the "location" field. Field number for the "comparisonCondition" field. Field number for the "constantCondition" field. Field number for the "instanceofCondition" field. Field number for the "customEvaluationCondition" field. Field number for the "unsupportedCondition" field. Enum of possible cases for the "condition" oneof. Field number for the "left" field. Field number for the "right" field. Field number for the "kind" field. Field number for the "branch" field. Field number for the "variable" field. Field number for the "type" field. Field number for the "operands" field. Field number for the "location" field. Field number for the "localVarDeclarationStmt" field. Field number for the "assignmentStmt" field. Field number for the "loadStmt" field. Field number for the "storeStmt" field. Field number for the "recordCopyStmt" field. Field number for the "mapGetStmt" field. Field number for the "mapSetStmt" field. Field number for the "requirementStmt" field. Field number for the "newRecordInstanceStmt" field. Field number for the "newArrayStmt" field. Field number for the "loadRefStmt" field. Field number for the "storeRefStmt" field. Field number for the "getReferenceStmt" field. Field number for the "staticCallStmt" field. Field number for the "virtualCallStmt" field. Field number for the "unknownCallStmt" field. Field number for the "returnStmt" field. Field number for the "uncontrolledVarStmt" field. Field number for the "varInvalidationStmt" field. Field number for the "varDereferenceStmt" field. Field number for the "customEvaluationStmt" field. Field number for the "varMayBeNilAssumptionStmt" field. Field number for the "castStmt" field. Field number for the "joinStmt" field. Enum of possible cases for the "stmt" oneof. Field number for the "name" field. Field number for the "isTempVar" field. Field number for the "result" field. Field number for the "value" field. Field number for the "result" field. Field number for the "receiver" field. Field number for the "receiverDeclaredRecord" field. Field number for the "field" field. Field number for the "receiver" field. Field number for the "receiverDeclaredRecord" field. Field number for the "field" field. Field number for the "value" field. Field number for the "source" field. Field number for the "dest" field. Field number for the "record" field. Field number for the "result" field. Field number for the "map" field. Field number for the "key" field. Field number for the "map" field. Field number for the "key" field. Field number for the "value" field. Field number for the "condition" field. Field number for the "result" field. Field number for the "record" field. Field number for the "result" field. Field number for the "length" field. Field number for the "result" field. Field number for the "reference" field. Field number for the "reference" field. Field number for the "value" field. Field number for the "result" field. Field number for the "variable" field. Field number for the "referenceKind" field. Field number for the "result" field. Field number for the "callee" field. Field number for the "arguments" field. Field number for the "returnType" field. Field number for the "result" field. Field number for the "receiver" field. Field number for the "receiverDeclaredRecord" field. Field number for the "signature" field. Field number for the "arguments" field. Field number for the "returnType" field. Field number for the "result" field. Field number for the "arguments" field. Field number for the "isLibraryCall" field. Field number for the "value" field. Field number for the "variable" field. Field number for the "variable" field. Field number for the "variable" field. Field number for the "requireNotNullAfterDereference" field. Field number for the "result" field. Field number for the "operands" field. Unable to represent "function" field in protobuf Field number for the "variable" field. Field number for the "variable" field. Field number for the "type" field. Field number for the "result" field. Field number for the "exprs" field. Field number for the "instructions" field. Field number for the "nextBlock" field. Field number for the "condition" field. Field number for the "trueBranch" field. Field number for the "falseBranch" field. Represents either a conditional or an unconditional jump Field number for the "unconditionalJump" field. Field number for the "conditionalJump" field. Enum of possible cases for the "jump" oneof. Field number for the "block" field. Field number for the "jump" field. Field number for the "blocks" field. Field number for the "jumps" field. Field number for the "startBlock" field. Field number for the "exitBlock" field. Field number for the "decls" field. Field number for the "location" field. Field number for the "functionDecl" field. Field number for the "recordDecl" field. Field number for the "globalVarDecl" field. Enum of possible cases for the "decl" oneof. Field number for the "name" field. Field number for the "parameters" field. Field number for the "parametersMayBeAliased" field. Field number for the "isPrivate" field. Field number for the "isStaticInitializerFunction" field. Field number for the "body" field. Field number for the "returnType" field. Field number for the "name" field. Field number for the "location" field. Field number for the "type" field. Field number for the "filePath" field. Field number for the "offset1" field. Field number for the "offset2" field. Field number for the "line" field. Field number for the "col" field. Field number for the "mayBeAliasedSet" field. Field number for the "name" field. Field number for the "superRecords" field. Field number for the "fields" field. Field number for the "virtualMethods" field. Field number for the "isMap" field. Field number for the "name" field. Field number for the "location" field. Field number for the "type" field. Field number for the "name" field. Field number for the "functionId" field. Field number for the "name" field. Field number for the "isPrivateOrConst" field. Field number for the "type" field. Allows to wait until CLion finishes the initial project load. Also handles incremental project updates. Interacts with CLion over the Rd protocol to get compilation arguments for C++ files and mock R# project model. The actual interactions go as follows: - CLion project is opened on the frontend. - CLion sends a request to the backend to open a solution of a special kind. - R# creates the corresponding solution mark and attempts to load the project inside on a separate thread, we block the thread until we get compilation arguments from the frontend. - CLion sends compilation arguments, we unblock the thread doing the async project load on R# side in return. Deliberately compared only on framework, name and suite, the rest is considered metadata for the index. Radler is a CLion plugin that provides general C++ support based on R++ language engine. Starts unconditional UBT suppression which will be finished on cookie Dispose Prolongs UBT suppression until specified file will be saved Checks if folder is suitable for new unreal module. CppUE4ProjectsTracker might not be initialized at this point of time, so we check for collisions with other modules on the frontend Checks if folder is suitable for new unreal plugin. CppUE4ProjectsTracker might not be initialized at this point of time, so we check for collisions with other plugins on the frontend lives in Cpp project, but we can't reference it from Rider.Backend. This is a copy-paste of - same requirements, but it's needed only for deactivation of