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've created a new bot service instance (C#) and downloaded the source code. When attempting to run it in VS through F5, I get the error stating that I'm trying to debug a release build and I should try a debug build instead. Huh?
The debughost.cmd file contains:
`@echo off
set size=0
call func settings list -data > %temp%\settings-list
call :filesize %temp%\settings-list
if NOT %size% == 0 goto show @echo ---------------------------------------------------------------------- @echo To fetch your bot service settings run the following command: @echo func azure functionapp fetch-app-settings [YOUR_BOT_SERVICE_NAME] @echo ----------------------------------------------------------------------
goto start
:show
type %temp%\settings-list
erase %temp%\settings-list
I've created a new bot service instance (C#) and downloaded the source code. When attempting to run it in VS through F5, I get the error stating that I'm trying to debug a release build and I should try a debug build instead. Huh?
The debughost.cmd file contains:
`@echo off
set size=0
call func settings list -data > %temp%\settings-list
call :filesize %temp%\settings-list
if NOT %size% == 0 goto show
@echo ----------------------------------------------------------------------
@echo To fetch your bot service settings run the following command:
@echo func azure functionapp fetch-app-settings [YOUR_BOT_SERVICE_NAME]
@echo ----------------------------------------------------------------------
goto start
:show
type %temp%\settings-list
erase %temp%\settings-list
:start
@func host start -p 3978
goto :eof
:filesize
set size=%~z1
exit /b 0
`
Never seen this one before. I'm missing something stupid probably but can't find what.
Azure Functions Core Tools (1.0.0-beta.99)
Function Runtime Version: 1.0.11002.0
The text was updated successfully, but these errors were encountered: