Revit Macros and Microsoft Application Virtualisation

[RPTHOMAS108]

Currently a version of Revit running in Microsoft Application Virtualisation bubble doesn't allow Macros to run due to so called copy on write restrictions on the placement of dll files. Copy on write is the creation of files in the App-V bubble while the application is in use.

Is there an awareness of this or a solution for it? Such as changing a setting for the temporary dll output path to one not present when the package is being sequenced (one not subject to CoW restrictions on the user profile).

In summary when a Macro is run a dll file is created in certain locations depending on macro type. These locations within the App-V bubble don't allow the creation of .exe and .dll files, so the Macro will not run.

http://virtualvibes.co.uk/cow-and-its-exclusions-in-app-v-5-0/

[jeremytammik]

Dear Richard,

Thank you for your report.

Sorry to hear about this.

I logged the issue REVIT-126963 [Revit Macros cannot execute in Microsoft Application Virtualisation -- 13893632] with our development team for this on your behalf to ensure they are aware and see what they have to say about it. Please make a note of this number for future reference.

You are welcome to request an update on the status of this issue or to provide additional information on it at any time quoting this change request number.

This issue is important to me. What can I do to help?

This issue needs to be assessed by our engineering team and prioritised against all other outstanding change requests. Any information that you can provide to influence this assessment will help. Please provide the following where possible:

• Impact on your application and/or your development.
• The number of users affected.
• The potential revenue impact to you.
• The potential revenue impact to Autodesk.
• Realistic timescale over which a fix would help you.
• In the case of a request for a new feature or a feature enhancement, please also provide detailed Use cases for the workflows that this change would address.

This information is extremely important. Our engineering team have limited resources, and so must focus their efforts on the highest impact items. We do understand that this will cause you delays and affect your development planning, and we appreciate your cooperation and patience.

Best regards,

Jeremy

[RPTHOMAS108]

Hello Jeremy,

Thanks for the reply and logging the issue. I've answered the parts below which are appropriate to me:

Users affected: Just me with no direct revenue impact. Away from work I have a local copy of Revit, so it isn't a problem there (although I wouldn't typically be creating macros in that environment). The main impact is where I need to automate something on the fly at work. There is dynamo but some people just prefer lines of code.

The potential revenue impact to Autodesk: I can't really assess revenue to Autodesk either. All I can say is that macros are most peoples introduction to programing with the API, so it's important day to day users don't come up against barriers to becoming developers. The macros they create and they are helped with here gives an insight into what they would like to do in Revit (how the base product could be improved). I think it is becoming more common that IT departments are looking to virtualise software in order to create quick convenient deployments across multiple offices.

I have no real timescale in mind for a fix or advise that could be given to better sequence the virtual package. I think it was just important to highlight the issue, if there wasn't an existing awareness. I think there are similar issues with AutoCAD where it creates dll files at start-up, perhaps it just requires a CoW working group to focus on this virtualisation compatibility issue and other virtualisation issues (if there isn't already one). I'm assuming Autodesk have an idea from surveys how many organisations are virtualising their software and what virtualisation products are used for this, so they can weight the need for action accordingly.

Regards

Richard

[jeremytammik]

Dear Richard,

Thank you for your update, business case and background info.

I added it to the issue REVIT-126963 [Revit Macros cannot execute in Microsoft Application Virtualisation -- 13893632].

Cheers,

Jeremy

[jeremytammik]

Dear Richard,

Thank you for your patience.

The development team completed analysis of the issue REVIT-126963 [Revit Macros cannot execute in Microsoft Application Virtualisation -- 13893632] that I raised for you and say:

A new macro project including the .dll files will be created in a temp folder. In Windows, that folder would be in anywhere on Disk C. In App-V, it seems that location doesn't allow the creation of .exe and .dll files.

Microsoft Application Virtualisation is not officially supported by Revit. Virtual machines supported by Revit are:

• VMware Horizon 6.1 or later
• VMware vSphere 6 or later
• Parallels Desktop 11 for Mac or newer

For more details please refer to the system requirements:

https://knowledge.autodesk.com/support/revit-products/troubleshooting/caas/sfdcarticles/sfdcarticles...

So it's recommend to use the virtual machines listed above.

Cheers,

Jeremy

[RPTHOMAS108]

Hello Jeremy

Thanks to yourself and the development team for looking into this issue.

I don't believe we'll be changing virtualisation software to suit one feature of one product that only affects one known user. It is a bit odd that it isn't classed as supported given that it generally works quite well in terms of the average Revit functionality.

I was kind of looking for a solution where the dll files could be compiled elsewhere but I understand the sharp development environment is a third party product and may be restricted in how it interfaces with Revit.

Regards

Richard