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
Unexpected character encountered while parsing number: W. Path '' - Visual Studio Mac #874
Comments
UPDATE: I right clicked in Visual Studio for Mac and updated the nuget package for
I can see if i expand the nuget package that its pulled down I'm sure this is something silly. Can someone point me in the correct direction? I used brew to update the CLI as described too. That didn't seem to fix anything either. |
Take a look at my post here The suggested fix worked for me. |
Thanks @ianadavies but unfortunately I had updated to the latest CLI too and still same error. |
I am experiencing the same problem. This has been recorded in https://youtu.be/v4DuNIA8dG4 I documented it in Azure/azure-functions-vs-build-sdk#218 though it seems issues on this repo are being ignored. I encounter this problem if
|
This SO post refers to the CLI version being to blame I tried reinstalling the utilities, however I see
|
@jthake-msft @LeviSchuck Have you tried to run |
Hello @JohnReeson |
Closing this as this was on a pre-release version of the core tools. Please retry and open a new issue if you're still running into problems. |
I have just installed for first time on my iMac Visual Studio for Mac 7.5.3 (build 7).
I created a new Azure Functions project. I run it up in a debugger. When I call the default httptrigger in postman I get this error
From searching around. There appears to be a related error around it using the 1.0.13 version of the
Microsoft.NET.Sdk.Functions
in a Windows version of Visual Studio. It just seems odd that the default new project would set these if they were not correct?The csproj file looks like this
My dotnet version is:
Full debug terminal window
The text was updated successfully, but these errors were encountered: