We are encountering an issue running RDAT after publishing it with the given build script, or after publishing it with Visual Studio:
We tried debugging the published version with Visual Studio, but could not get more information than is displayed there, it is unclear what the path is, and why it is empty only with the published version. It is not the --path from the command line arguments as that file exists, and works with the compiled (not published) version.
Steps to reproduce:
download the Exchange Webservices dll either with dotnet packages add or NuGet in Visual Studio
build solution and publish in Visual Studio, or use build script on Kali
run the published standalone RDAT with the required arguments
On the other hand, running the built version that is not standalone and requires the other files, (RDAT.dll, RDAT.runtimeconfig.json, RDAT.deps.json, etc) works without that issue.
Hi,
We are encountering an issue running RDAT after publishing it with the given build script, or after publishing it with Visual Studio:
We tried debugging the published version with Visual Studio, but could not get more information than is displayed there, it is unclear what the
pathis, and why it is empty only with the published version. It is not the--pathfrom the command line arguments as that file exists, and works with the compiled (not published) version.Steps to reproduce:
dotnet packages addor NuGet in Visual StudioOn the other hand, running the built version that is not standalone and requires the other files, (RDAT.dll, RDAT.runtimeconfig.json, RDAT.deps.json, etc) works without that issue.