[MSCEU16 VBA] Need to Sign VBA Macros

Joerg Teresniak said:

You must now sign all .mvba files in MicroStation using the VBA Editor tool or MVBASign.exe.

I think this statement is pretty clear, isn't it? ;-)

Every MicroStation VBA macro will have to be signed using digital certificate.

If the rule, that self-signed certificate is accepted for MVBA, it's not big change, because everybody can create it using MicroStation SDK or Microsoft Office (and probably some others too) tools.

In my opinion this change only follows general practice when not signed code is automatically not trustworthy.

Regards,

  Jan

Jan Šlegr said:

because everybody can create it

• The final step (5) of that wiki are not clear. 
• This NOTE is not clear: Microsoft VBA Tools > Digital Signatures…; is not required and is not a substitute for a .cer file. 

Particularly for the casual developer, this raises a new barrier for development.  I too look forward to a comment from Bentley Systems.

Prefer VBA. Yeah sure. Will it even work in Powerdraft in future...

Oto said:

Will [VBA] even work in Powerdraft in future...

Please don't hijack a thread!

If VBA doesn't work in PowerDraft then file a Service Request with Bentley Systems.  If you want to discuss that new topic, then start a new thread.

Not hijacking just worried when Microstation Powerdraft U16 will come out.

Hi Jon,

Can you provide a link to the wiki you are referring to so we can take a look.

For update 16 when MicroStation loads an unsigned vba application in low or none security mode it will warn the user that its not trusted and do they want to continue with loading it, the user can then choose to load the vba or not (we also remember your choice across sessions). This is currently controlled by a feature aspect and is not the default behaviour, it will become the default behaviour in Update 17. 

You should request this feature aspect token from us such that you can work on signing your applications and delivering updated applications to your users in preparation for this becoming the default behaviour in Update 17 so they would not receive this warning in the future.

The same also applies to mdl applications. I believe we didnt deliver Rsign.exe in the SDK for Connect edition, this will now be delivered.

Thanks

Paul

Paul Chater said:

Can you provide a link to the wiki

The link is already in this thread, but here it is again: communities.bentley.com/.../sign-microstation-vba-applications

Paul Chater said:

You should request this feature aspect token from us

How do we go about making that request?

Hi Jon,

The text refers to the workflow using the vba editor application to create a digital signature.

See below image.

Thanks

Paul

Hi Jon,

There will be an announcement on this once Update 16 is released.

Regards

Paul