This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Feature Events Creation Bug?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 21, 2009
05:30 PM
Feature Events Creation Bug?
InstallScript MSI Project
Create a new feature with the following notation:
Name.Subname.anotherName
(This component name follows our namespace inside of CSharp)
When you go into the InstallScript Setup.Rul file and select the new project name from the event drop down list under the section "Move Data". When the new method is created, it will name it accordingly to whatever the feature is called.
Typically this isn't a problem, but unfortunately it doesn't seem like the InstallScript engine supports functions with periods in the name; therefore, shouldn't it automatically replace those periods with something it can understand instead of throwing compilation errors?
Create a new feature with the following notation:
Name.Subname.anotherName
(This component name follows our namespace inside of CSharp)
When you go into the InstallScript Setup.Rul file and select the new project name from the event drop down list under the section "Move Data". When the new method is created, it will name it accordingly to whatever the feature is called.
Typically this isn't a problem, but unfortunately it doesn't seem like the InstallScript engine supports functions with periods in the name; therefore, shouldn't it automatically replace those periods with something it can understand instead of throwing compilation errors?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 22, 2009
12:29 PM
I've submitted this under issue IOA-000053233. You should be able to work around this behavior for now by renaming the feature events manually and selecting the renamed function in the appropriate feature event select in the Setup Design or Features view.