Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

No TypeScript files in VS2017

See original GitHub issue

[moved from https://github.com/Microsoft/msbuild/issues/1354]

Just downloaded VS2017 and migrated my project.json-based project. This was created using the Angular 2 template that can be found in https://github.com/aspnet/JavaScriptServices.

Now my TypeScript files are not shown and there are many .js and .map.js files created automatically.

What would be the correct configuration to have what I had before this?

After posting the original question I found these settings are enough for my scenario, but the migration experience still wasn’t complete and that’s a bug in my opinion:

<PropertyGroup>
  <TypeScriptCompileBlocked>true</TypeScriptCompileBlocked>
</PropertyGroup>

<ItemGroup>
  <None Include="ClientApp\**\*.scss" />
  <None Include="ClientApp\**\*.ts" />
</ItemGroup>

Thanks!

Issue Analytics

State:
Created 7 years ago
Reactions:2
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

SteveSandersonMScommented, Nov 21, 2016

Seems like it should be possible to migrate:

Preserve the <TypeScriptCompileBlocked>true</TypeScriptCompileBlocked> value if it’s is present in the .xproj that’s being migrated
Ensure that all original files show up in solution explorer (.ts, .js, .json, .css, .less, .sass, .png, etc.), like they did with .xproj

0reactions

livarcocccommented, Jan 13, 2017

Ok, seems like migration will get it for free then. I am closing this issue. If there is something else we should do as part of migration for this, please, re-activate.