Extension info not completed deleted on deletion of extension

[EPTamminga]

Description of bug

Installed Language Pack as extension, deleted it (with file removal) and installed it again: it mentioned that I will do a repair, which is not corect

Steps to reproduce

List the precise steps to reproduce the bug:

1. Go to Extension
2. Install a LP as an extension
3. Delete the LP extension with the removal of files
4. Install the same LP again

Current behavior

It tells me in 4. that I am doing a repair

Expected behavior

No repair, a normal install

Screenshots

Error information

Provide any error information (console errors, error logs, etc.) related to this bug.

Additional context

Provide any additional context that may be helpful in understanding and/or resolving the bug.

Affected version

• 10.00.00 alpha build
• 09.07.02 release candidate
• 09.07.01 latest supported release

Affected browser

• Chrome
• Firefox
• Safari
• Internet Explorer 11
• Microsoft Edge (Classic)
• Microsoft Edge Chromium

[TopCat6]

I believe this is related to the dll files not being deleted because they are "in use" by w3wp.exe.
Please see my comments in these other posts:
#4205
DNNCommunity/DNN.Blog#174

[stale]

We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically.
If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!

[sleupold]

@TopCat6
no, there are no .dll files in language packs.
Obviously, the package info or extension info is not properly deleted.

@EPTamminga
have you been able to identify remaining records in any of the database metadata tables (Packages, Extensions) after deletion of the LP?

[TopCat6]

@sleupold Good point. However, I think I have traced the problem to a bug in the DNN Telerik Identifier module that I was using. It was holding file locks:
https://github.com/IowaComputerGurus/DnnTelerikIdentifier/releases/tag/V1.0.2

[sleupold]

@TopCat6 ,
I agree, that's a valid issue.
However, this item here is specifically about DNN Language Packs.

[TopCat6]

@sleupold Got it. DnnTelereikIdentifier should only be looking at .dll files. Presuming that is true, my point is not relevant.

[EPTamminga]

@sleupold I did not test it specifically for LP's. but I remember that the Delete Files option (in general) did not delete files as expected. I am not sure if this has been fixed,

[stale]

We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically.
If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!

[stale]

This issue has been closed automatically due to inactivity (as mentioned 14 days ago). Feel free to re-open the issue if you believe it is still relevant.