Prevents renaming folders (Windows)

[tflanitzer]

I have noticed that I cannot rename folders within my project as long as the language service is active. This is the error I get when I try:

As soon as I deactivate the extension and reload, it works as expected.

Using Process explorer I found out that indeed Code.exe has open handles on each folder in my project:

Here is the Angular Language Service log output:

Search path: c:/dev/XXX/Sources/Frontend/src/app/data-import/data-import-editor
Config file name: c:/dev/XXX/Sources/Frontend/tsconfig.json
Angular Language Service: 5.1.0
TypeScript: 2.6.2
getTemplateRefrences: 2942ms
Add recursive watcher for: c:/dev/XXX/Sources/Frontend
Opened configuration file c:/dev/XXX/Sources/Frontend/tsconfig.json
getDiagnostics: 20ms

[Darkein]

Hello,
the problem is still here. I have to deactivate this extension to rename my files and folders on Windows 10.

[jonaskuske]

Same issue. :(

[techy2493]

This is a much larger issue than just renaming, the service is leaving open file handles all over the place. I'm having trouble deleting things, re-building projects with libraries that npm link & unlink, git rebases... It's gotten worse recently, which may be partly due to windows updates but the extension itself is keeping these handles open.

[techy2493]

This is an example of attempting to rebase with the extension on, (after failing and re-starting VsCode) and below is an example after the extension is disabled in the worksapce.

[techy2493]

Here is an example where the Angular Language Service blocks an NPM Unlink of a package library due to these same open file handles.

[techy2493]

These things separately impact workflow and performance, but when working quickly in large projects these things together make working with the angular language service enabled nearly impossible.

[Darkein]

This issue is opened since more than one year, and this annoying problem is still here (I just can't use this great extension).
What do you need to take a look on it ?

[JohnnyDevNull]

Well i have also the problems since a long time and the plugin in the actual state is in bigger projects especially with local angular libraries not usable. I have disabled it and work without it.

I think the problem is the duplicate TS-Server which is running and maybe it's fixed with that one here: #338

[kyliau]

This is the same as #224, will track the issue there.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}