You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to run the solution provided in Visual Studio for Mac. I don't think that it works anymore. My steps to reproduce are to run the application and send a "test" message in the bot-emulator.
I appreciate the detailed lab and just wanted to know if there's now an additional step required to get this working on macOS. Details below and Thanks!
Details{
"message": "An error has occurred.",
"exceptionMessage": "Value does not fall within the expected range.",
"exceptionType": "System.ArgumentException",
"stackTrace": " at System.Net.Http.Headers.Parser+Token.Check (System.String s) [0x00019] in /Users/builder/data/lanes/4992/mono-mac-sdk/external/bockbuild/builds/mono-x64/mcs/class/System.Net.Http/System.Net.Http.Headers/Parser.cs:57 \n at System.Net.Http.Headers.ProductHeaderValue..ctor (System.String name, System.String version) [0x0000a] in /Users/builder/data/lanes/4992/mono-mac-sdk/external/bockbuild/builds/mono-x64/mcs/class/System.Net.Http/System.Net.Http.Headers/ProductHeaderValue.cs:45
The text was updated successfully, but these errors were encountered:
Hey, sucks that this workaround for bots on VS Mac stopped working.
It looks like this is still an open issue (https://github.com/dotnet/corefx/issues/19914). I'm not sure there is anything I can do to fix that within this project, but something in the dotnet issue might work for you.
Also, as the bot framework documentation pointed out "The Bot Builder SDK for .NET currently supports C#. Visual Studio for Mac is not supported." So this was a bit of a long shot anyway.
I tried to run the solution provided in Visual Studio for Mac. I don't think that it works anymore. My steps to reproduce are to run the application and send a "test" message in the bot-emulator.
I appreciate the detailed lab and just wanted to know if there's now an additional step required to get this working on macOS. Details below and Thanks!
The text was updated successfully, but these errors were encountered: