-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Legacy .csproj files always show "Invalid static method invocation syntax" error #14
Comments
I wonder if this is related to #1... Let me have a look and get back to you. |
What version of the extension are you using? |
The latest: 0.2.51
|
Hmm, looks like I need to upgrade the If I build a custom VSIX would you be willing to try it out for me? |
Of course! |
You can download the VSIX here (instructions for install are listed there, too). |
I'll try it out and let you know the results. Thanks so much for the quick response! |
Yep! That works perfectly. I intellisense and autocomplete are working as expected now. |
Ok, thanks - will publish it then :) |
I am always seeing this error when looking at "older" .csproj files (those not using the new structure that includes
<PackageReference>
s.Invalid static method invocation syntax: "[Microsoft.Build.Utilities.ToolLocationHelper]::GetPathToStandardLibraries($(TargetFrameworkIdentifier), $(TargetFrameworkVersion), $(TargetFrameworkProfile), $(PlatformTarget), $(TargetFrameworkRootPath), $(TargetFrameworkFallbackSearchPaths))". Microsoft.Build.Utilities.ToolLocationHelper.GetPathToStandardLibraries Static method invocation should be of the form: $([FullTypeName]::Method()), e.g. $([System.IO.Path]::Combine(
a,
b)).c:\repo\master\FileSystem\FileSystem.csproj(MSB4186)
Here is an example .csproj file that generates the issue:
I haven't been able to identify the root cause (I'm unfamiliar with the
ToolLocationHelper
).Am I missing an upgrade or dependency somewhere?
I have the following installed:
And this is the output for
dotnet --info
:The text was updated successfully, but these errors were encountered: