Adam Ralph

marked as **feature**

@vvolkgang can you please provide a full example which recreates the problem?

@seesharper thanks for raising this! It would certainly be nice to provide some kind of no-brainer experience for debugging scriptcs in VS Code. I haven't had time to play with...

@filipw the circular dep is a good point. Moreover, I think `IScriptServices` should be a dedicated interface for this purpose and crafted appropriately, only exposing the things that we think...

I've manually uploaded a build for analysis - https://scan.coverity.com/projects/2356 So far it's yielded some basic output and says: > Note: Lines of code and defect density statistics will be calculated...

The current defects can be seen at https://scan.coverity.com/projects/2356/view_defects

In fact, https://github.com/scriptcs/scriptcs/issues/721 should be part of this.

Yeah, the former was what I was thinking, grab stdin and play with it. I'll give it a shot. It will be great if it works.

@MSK61 thanks for raising this. It's something we've discussed a few times but we've never really made any progress on it. It's probably something we need to spike as I'm...

Did you add it to a local `scriptcs_nuget.config`?