support for package references (PackageReference) in project files #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Package references, using the PackageReference node, manage NuGet dependencies directly within project files (as opposed to a separate packages.config file).
https://docs.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files
When this is used the tools folder location changes to /packages/{package_name}/{version}/tools. Furthermore the default packages location moves to the windows Users folder.
Therefore the existing logic for getting the transformer.exe location is not correct for the projects using ProjectReference.
I suggest using the powershell automatic variable $PSScriptRoot to get the path to the running script to locate transformer.exe.