tremara1 Active Member Licensed User Longtime User Jun 7, 2022 #1 I have just tried to create a standalone package and got an error no permission to write exe...When I check Bitdefender it was blocked...I have attached a screen shot from bit defender. I just created a package from a different project with no issues...I have scanned all the files in the project I have problem with, and no issues. The project is a relatively simple sql data base front end. It runs from b4j ok. I had a look and I have many versions of csc.exe. I scanned the one used by b4j and no issues. I am fairly certain it is a false positive but need some reassurance.... Attachments bitdef.png 47.4 KB · Views: 438
I have just tried to create a standalone package and got an error no permission to write exe...When I check Bitdefender it was blocked...I have attached a screen shot from bit defender. I just created a package from a different project with no issues...I have scanned all the files in the project I have problem with, and no issues. The project is a relatively simple sql data base front end. It runs from b4j ok. I had a look and I have many versions of csc.exe. I scanned the one used by b4j and no issues. I am fairly certain it is a false positive but need some reassurance....
MegatenFreak Active Member Licensed User Jun 7, 2022 #2 This might help: Bitdefender detects my console application as Gen:Variant.Ursu.56053 I've developed a console application that does a lot of routines, but the Antivirus detected it as a malware of type Gen:Variant.Ursu.56053. How can I fix this without touching the antivirus policy stackoverflow.com Upvote 0
This might help: Bitdefender detects my console application as Gen:Variant.Ursu.56053 I've developed a console application that does a lot of routines, but the Antivirus detected it as a malware of type Gen:Variant.Ursu.56053. How can I fix this without touching the antivirus policy stackoverflow.com
Erel B4X founder Staff member Licensed User Longtime User Jun 7, 2022 #3 The packager calls csc.exe = C# compiler, to create the program executable. You can see it in B4JPackager source code. It is of course harmless. Upvote 0
The packager calls csc.exe = C# compiler, to create the program executable. You can see it in B4JPackager source code. It is of course harmless.
tremara1 Active Member Licensed User Longtime User Jun 7, 2022 #4 Thanks guys...I have contacted bitdefender and supplied them with all the relevant info. I have used the packager before and since with no issues. Upvote 0
Thanks guys...I have contacted bitdefender and supplied them with all the relevant info. I have used the packager before and since with no issues.