fbpx

Strange exe-naming

More
1 year 4 months ago #1 by Karl Faller
Strange exe-naming was created by Karl Faller
Chris,
by chance i had a look into my bin\debug folder and found some "strange" files like:
bcc5f20a-a180-4b27-823b-7abf0367d4e6__SQL.exe or
d20e51d5-b630-4f65-bee9-f7ba8612cfd6__TomLibVirt.dll
The "regular" ones are named like: __TomLibVirt.dll
I suspect that may be result of some problems i had, but i'm curious ;)- probably i should simply delete them and forget?

Karl

Please Log in or Create an account to join the conversation.

More
1 year 4 months ago #2 by Chris Pyrgas
Replied by Chris Pyrgas on topic Strange exe-naming
Hi Karl,

I had such files too from time to time and was wondering where they are coming from. Just yesterday I realized they are created when you try to compile an app that is already running, when this happens, the existing dll/exe gets renamed to that strange file name.

Guess that's a feature of roslyn, tried to search about this, but did not find anything. Maybe Robert has further info?

Chris

XSharp Development Team
chris(at)xsharp.eu

Please Log in or Create an account to join the conversation.

More
1 year 4 months ago - 1 year 4 months ago #3 by Robert van der Hulst
Replied by Robert van der Hulst on topic Strange exe-naming
Chris,

Yes this is what Roslyn does: when there is a sharing violation writing the output file then the existing file is renamed and marked for deletionSee:

https://github.com/dotnet/roslyn/blob/master/src/Compilers/Core/Portable/CommandLine/CommonCompiler.CompilerEmitStreamProvider.cs , line 80.

The files should be hidden. I guess Karl has the option to show hidden files enabled.
The files normally should automatically be deleted when they are no longer in use.

Robert

XSharp Development Team
The Netherlands
This email address is being protected from spambots. You need JavaScript enabled to view it.
Last edit: 1 year 4 months ago by Robert van der Hulst.

Please Log in or Create an account to join the conversation.