Skip to content

Expose new module targets in Project properties and build targets #3033

Closed

Description

We have added two new module targets, umd and system, we need to expose both in:

  • Project properties in C#/VB project -- Dev12
  • Project properties in C#/VB project -- Dev14
  • Project properties in JSProj project -- Dev12
  • Project properties in JSProj project -- Dev14
  • build targets -- Dev12
  • build targets -- Dev14
  • tools\options page -- Dev12
  • tools\options page -- Dev14

One thing to figure out, is if TypeScriptToolsVersion is below 1.5, do we still pass in the module value, should it be an error?

Activity

  1. added this to the milestone on May 5, 2015
  2. mhegazy commented on May 5, 2015

    @mhegazy
    ContributorAuthor

    updates to expose new flags tracked by #3034

  3. paulvanbrenk commented on May 12, 2015

    @paulvanbrenk
    Contributor

    We allow the user to specify unsupported modules even if they target an older version of the compiler, the compiler will display a useful error when that happens.

  4. paulvanbrenk commented on May 19, 2015

    @paulvanbrenk
    Contributor

    Should be in 1.5 RTM for VS 2013 and VS 2015

  5. locked and limited conversation to collaborators on Jun 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugA bug in TypeScriptFixedA PR has been merged for this issueVisual StudioIntegration with Visual Studio

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions