Skip to content
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

Problem with running Composer created project from VS2017 #1816

Closed
vovanb opened this issue Dec 30, 2019 · 4 comments
Closed

Problem with running Composer created project from VS2017 #1816

vovanb opened this issue Dec 30, 2019 · 4 comments
Assignees
Labels
R8 Release 8 - March 16th, 2020

Comments

@vovanb
Copy link

vovanb commented Dec 30, 2019

We use windows service to host bot. Before test it in windows service I decided to use Composer output in IISExpress host: I created in Composer new empty project and just added simple response on beginning, then tried to open Composer output from BotFramework-Composer\MyBots\ folder using VS 2017. It compiled correct but then when I tried to debug it in IISExpress I got below error: System.InvalidOperationException: 'Could not find 'UserSecretsIdAttribute' on assembly 'BotProject'. Check that the project for 'BotProject' has set the 'UserSecretsId' build property. –

Version

4.6.0-preview2

Windows

To Reproduce

Steps to reproduce the behavior:

  1. Create new Empty project in composer
  2. Test it in Emulator
  3. Open new project VS2017
  4. Compile and execute
  5. Will be exception :
    System.InvalidOperationException: 'Could not find 'UserSecretsIdAttribute' on assembly 'BotProject'. Check that the project for 'BotProject' has set the 'UserSecretsId' build property.

Screenshots

CompserBug

@vovanb vovanb added the Needs-triage A new issue that require triage label Dec 30, 2019
@hibrenda
Copy link
Contributor

@vovanb Thanks for the suggestions. At this moment, the bot runtime created under each bot folder could not be executed as many resources have not been included. eg. bot assets - SecretsId and also other assets - luis related. Could you share the requirements why you are using VS instead of composer run ?

@vovanb
Copy link
Author

vovanb commented Dec 30, 2019

@hibrenda below number of reasons:

  1. I want to add storing state into on-Premise MS SQL Data
  2. I want to deploy Bot to be running from on-premise server and not from Azure and hosted in IIS
  3. I want to add custom c# libraries we need to interact from Bot (not https API)
    So idea is to use Composer to create Dialogs Flow and then use VS2017 to modify/add libraries as we usually doing in c# SDK.

@hibrenda
Copy link
Contributor

@vovanb Thanks for sharing the requirements. Yes. Bring your own bot runtime is on our roadmap. After #1672 PR integrated, you can do it much easier.

@a-b-r-o-w-n a-b-r-o-w-n added Type: Enhancement and removed Needs-triage A new issue that require triage labels Jan 2, 2020
@hibrenda hibrenda added the R8 Release 8 - March 16th, 2020 label Jan 3, 2020
@hibrenda
Copy link
Contributor

hibrenda commented Feb 4, 2020

@vovanb this issue has been solved, please sync with latest updates.

If your bot is using luis, please make sure do following steps before run by VS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R8 Release 8 - March 16th, 2020
Projects
None yet
Development

No branches or pull requests

5 participants