JavaScript Web and Express Web roles fail to package

Open
#2,290 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, javascript
Domain
build-system, cloud

Research direction

Start by reproducing the failure with an Azure Cloud Service project containing a JavaScript Web Role or JavaScript Express Web Role, then invoke Package from the Azure Cloud Service project node. Trace the packaging entry point to determine why the command fails; done means the Package command succeeds for both role types.

Written by the indexing model from the issue text.

Description

Expected Behavior

Expected Package command to succeed.

Actual Behavior

Package command fails.

  • NTVS Version: 1.5.20902.1
  • Visual Studio Version: 16.8.0 Preview 4
Steps to Reproduce
  1. Create new "Azure Cloud Service" project and add either a JavaScript Web Role or a JavaScript Express Web Role
  2. Right click on the Azure Cloud Service project node and select "Package"
Dominant language
C#
Stars
1.8k
Forks
355
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/nodejstools

All issues in microsoft/nodejstools

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.