Since I ran a build for production (and subsequently successfully published) I have a problem with debugging in VS Code. I am not hitting breakpoints and have to stop and relaunch the debugger for changes to be delivered to the browser. After this I can only apply breakpoints in a new tab in the editor marked as "read only inlined content from source map". I believe this has something to do with source map location and possibly down to a gulp process during the build. I'm sure it's down to my inexperience and not a Zero problem but it's as frustrating as hell.
Can anyone here throw me any pointers
- google has taken me to many places but I'm sure this is just ignorance and not rocket science....
3 Answer(s)
-
0
Hi @BobIngham,
I assume you are using ASP.NET Core & jQuery version of AspNet Zero.
If you run build for production, js files will be minified and bundled by gulp task which you can find in gulpfile.js (<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/blob/dev/aspnet-core/src/MyCompanyName.AbpZeroTemplate.Web.Mvc/gulpfile.js">https://github.com/aspnetzero/aspnet-ze ... ulpfile.js</a>).
Since the *.js.map files are not copied to related output folders, you are not able to debug. So, you can modify gulpfile.js o copy *.js.map files to output if they exist or you can work on dev mode.
-
0
@ismcagdas - I am using aspnet-core and angular. 5.1.0. This is not your problem. It's something to do with VS Code, currently I have reverted to a mix of stopping the debug process, sometimes I have to stop and restart ng-serve and sometimes I have to debug values in the browser. It's a bit of a pain but I am slowly making progress on how to solve the issue. When I find the answers I will post the results to help anyone else who is using a similar development setup (VS 2017 Community for aspnet-core and VS Code for angular). I'll keep you posted when I find out exactly what is happening.
-
0
cool! waiting your feedbacks ;)
