NATIVE ENGINE: Previously working build failed.

[NigelG]

Having just upgraded to IA10, I thought I would try out your new "NATIVE ENGINE" build on an existing project.
This project builds perfectly well without the Native Engine.

I switched on the Native Engine by adding the following line to the top of the MSI code (as recommended):
Set Variable NATIVE_ENGINE to TRUE

The build now fails right at the end with:
Error during build: Unable to sign installation executable

I am signing my package with Authenticode.
Does this mean that Authenticode does not work with the Native Engine on IA10?
Are there any settings I need to adjust to get the build to work?

[bokkie]

I tried the same setting in a test project and it built ok. I don't use Authenticode however.

I'm still puzzled about the native engine. The online help says you can switch in and out of it as you want. I can't quite understand under what actual conditions that might be necessary. I think I interpreted it to mean in case the Windoze installer is missing? If so, would you not want to enable the native engine for the lifetime of the script? I'm sure I need to take more time reading the online help and the finer details behind the new pre-defined variables. In the excitement to download 10 and play with it I think I'm ahead of myself in the frenzy to get started on it.

Edit: I enabled Authenticode and added a password only. I too can confirm the build fails at the end. I've never used authenticode before so perhaps I'm not doing it the same way. Either way, I get the same error but possibly for different reasons?

[mills]

I don't have a certificate handy to test with today. I'll be able to work on one and reproducing this on Monday.

[mills]

I'm still working on a certificate. You could try setting NATIVE_ENGINE to FALSE just before Apply Install...

[NigelG]

You could try setting NATIVE_ENGINE to FALSE just before Apply Install...

If you switch it ON at the top of the script and then OFF again immediately before "Apply Install" isn't that the same as not having switched it on at all, with the net result that you compile an MSI install?

[mills]

I should be able to work on a certificate tomorrow, being a holiday.

Does the build fail if you remove the NATIVE_ENGINE line or set it to FALSE?

I have some testing to do on the native engine (you're supposed to be able to switch modes throughout the script). For instance, I'm going to try to trick it to see if I can't somehow get a file installed with Install File and native engine mode, then switch to Win mode and hit Apply Install to see if I can't get duplicate work done or something like that.

The point is to try to isolate whether setting NATIVE_ENGINE is the cause of this problem or something else.