ASP.NET Core section recommends copying *.ts files into wwwroot

[dsaf]

https://www.typescriptlang.org/docs/handbook/asp-net-core.html

Why would they be needed there? Surely *.map files should map to the source path?

[dsaf]

var paths = {
    scripts: ['scripts/**/*.js', 'scripts/**/*.ts', 'scripts/**/*.map'],
};

[DanielRosenwasser]

CC @sandersn - if the .ts files weren't in wwwroot, how would they be accessible when debugging? Does IIS serve from other directories?

[dsaf]

@DanielRosenwasser do you recommend creating a separate task for production build?

Also how about this?

http://stackoverflow.com/a/35804824

public void Configure(IApplicationBuilder app, IHostingEnvironment env, IApplicationEnvironment appEnv)
{
    app.UseStaticFiles();
    if (env.IsDevelopment())
    { 
        app.UseFileServer(new FileServerOptions()
        {
            FileProvider = new PhysicalFileProvider(System.IO.Path.Combine(appEnv.ApplicationBasePath, "App")),
            RequestPath = new PathString("/App"),
        });
    }
}

[DanielRosenwasser]

A separate production build task seems reasonable.

[dsaf]

Understood, thank you.

[DanielRosenwasser]

Reopening because I think we should consider documenting this.

[dsaf]

@DanielRosenwasser is it OK to ask related questions here? I guess stuff I am clarifying will be relevant for other developers on the same stack going forward.

What I don't understand is whether Gulp will automatically push changes when editing and saving *.ts while running - without complete re-building?

Am I correct in my understanding that:

1. Client-side application should be served from wwwroot\
2. Ideally wwwroot\ should not contain (editable) *.ts files
3. Source (editable) *.ts files should reside outside of wwwroot\
4. Gulp (or Grunt) should be used for copying *.js/*.map files resulting from compilation into the wwwroot\

Is it reasonable to expect:

1. Clean wwwroot
2. Incremental compilation
3. Semi-automatic browser updates on *.ts file saving
4. Step-through debugging of *.ts in Visual Studio

Some questions I still have:

Should Gulp be responsible for invoking tsc or should Visual Studio do it on save?
Will Gulp make change propagation incremental? At the moment it seems to be taking substantial time.
Do I need to stop and build project every time I want to serve changed files to browser?

Thank you.