Now I'm going to write the file paths in the pre-build event, and then read from this file in the code, but I wonder if there is a more elegant way.
edit: It’s kind of like Help with one step to create all projects + installer (.NET + WiX) , since I really didn’t get an answer to this, seeing if I can get an answer to a simpler question.
Here is a dirty hack: dump them into a file.
Add an action to the pre-build events to display the solution path to the file:
echo $(SolutionDir) > SolutionDirFile.txt
SolutionDirFile.txt #.
SolutionDirFile.txt
, , - - PostSharp. , - , .
Source: https://habr.com/ru/post/1702261/More articles:The right technique for writing reusable interface objects? - oopHow to set null field in Quest Toad "Browse Database Objects"? - databaseСобытие для захвата, когда пользователь, прошедший проверку подлинности, не аутентифицирован - asp.netC # define macros - cКак предотвратить изменение размера формы в Delphi? - delphiC # and SQL Server: passwords. Where to do what? - c #Help with one step to create all projects + installer (.NET + WiX) - build-processUnit analysis of data flow in ssis pakage - unit-testingCalculation of a person’s time zone (GMT offset) by phone number? - sqldollar-finished strings - assemblyAll Articles