xsharp.eu • Error XS7038
Page 1 of 3

Error XS7038

Posted: Wed Mar 20, 2019 7:45 pm
by Juraj
Hi All,

I copied the Visual Studio project from the damaged hard disk. VS2017 opens the project correctly, but returns the error when compiling
Error XS7038 Failed to emit module 'MOWPF'. MOWPF XSC.

Juraj

Error XS7038

Posted: Wed Mar 20, 2019 8:01 pm
by wriedmann
Hi Juraj,

do you have tried to execute first a "Clean" process in the project?

Wolfgang

Error XS7038

Posted: Wed Mar 20, 2019 8:06 pm
by Juraj
Hi Wolfgang,

yes, I execute "Clear Solution" and "Clean <projectName>, but it did not help

Juraj

Error XS7038

Posted: Wed Mar 20, 2019 8:21 pm
by wriedmann
Hi Juraj,

MOWPF is the name of your executable?
Maybe you have specified a path that does not exists on the new disk?
Wolfgang

Error XS7038

Posted: Wed Mar 20, 2019 8:32 pm
by Juraj
Hi Wolfgang

yes, MOWPF is the name of executable. In "Properties" MOWPF is path OK

Juraj

Error XS7038

Posted: Wed Mar 20, 2019 8:55 pm
by Chris
There are a couple compiler bugs causing this, sometimes it has to do with pointers. Please try enabling the "Allow Unsafe code" option in your project settings, does this make a difference?

If not, can you zip and send me the solution to have a look?I

Error XS7038

Posted: Wed Mar 20, 2019 8:56 pm
by robert
Juraj,
Does the file already exist in the OBJ or BIN folder ?
You write that the hard disk was damaged. When you copied the folder over did you make sure that you have enough rights to write to the copy of the folder structure on your machine ?

Robert

Error XS7038

Posted: Wed Mar 20, 2019 9:14 pm
by Juraj
Hi Chris

enabling the "Allow Unsafe code" option it did not help. I don't have your e-mail address.

Juraj

Error XS7038

Posted: Wed Mar 20, 2019 9:57 pm
by Chris
Juraj,
hsc wrote:Hi Chris

enabling the "Allow Unsafe code" option it did not help. I don't have your e-mail address.

Juraj
It's in my signature below :)

Did you also check Robert's advice?

Error XS7038

Posted: Wed Mar 20, 2019 10:46 pm
by Chris
For anybody following this, the problem turned out to be a small typo in the code that the compiler did not catch as an error and then failed to report a correct error message. Should be easy for Robert to fix for the next build.