Assembly version as property - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

fisheye
Posts: 7
Joined: Sun May 10, 2009 12:54 pm

Assembly version as property

Hello,

I have used "Register .Net assembly for COM interop.." with synchronization to pull out the registry keys then set the synchronization to disabled. This is because I only need a subset of those keys and I don't want to go and tidy it all up every time I do a build. I haven't tried this but I would assume that the registry key properties would also need to be reconfigured each build if they were synchronized.

This leaves me to ask whether I can set a property to reflect the current version of my .NET assembly which I can subsequently use in the registry key or if theres a better way to achieve this.

Cheers
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Assembly version as property

Hi,
I haven't tried this but I would assume that the registry key properties would also need to be reconfigured each build if they were synchronized.
If synchronization is used, the registry entries are re-added when the project is built.
This leaves me to ask whether I can set a property to reflect the current version of my .NET assembly which I can subsequently use in the registry key
I'm afraid Advanced Installer doesn't have a property for this. You could use a custom installer property, but you would need to manually modify all registry entries which use the .NET version.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”