Microsoft is working on the next version of Windows Installer. In today's Windows Installer chat, Microsoft told that a first public beta version of MSI 3.0 should be available mid August. An announcement will be posted in the related public Microsoft newsgroups when it's available.
The future of MSI: http://www.installsi...hat20030204.htm
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
MSI 3.0 Beta Coming in August
Started by
Stefan Krueger
, Jun 05 2003 20:48
1 reply to this topic
Stefan Krueger
-
- Administrators
- 13,269 posts
InstallSite.org
Posted 05 June 2003 - 20:48
Stefan Krüger
InstallSite.org twitter facebook
Guest_James Hancock
Guest_James Hancock
-
- Guests
Posted 13 June 2003 - 21:53
Two things I would love them to add. Maybe someone can send these to MS:
1. Direct attachment of SQL Server databases and security setup for these databases with simple commands. Pre-built dialogs etc. would be a huge benefit. The current way of doing this with custom actions is horrible.
2. Support for writting to a .NET application's App.config file. This would replace most registry settings. Currently we would have to write a custom action to do this, but I Think it should be included in msi because this is the new normal way of storing application settings.
3. Have someone actually test and make a high priority the SQL Server merge modules. They are HORRIBLY bug ridden as it stands right now.
1. Direct attachment of SQL Server databases and security setup for these databases with simple commands. Pre-built dialogs etc. would be a huge benefit. The current way of doing this with custom actions is horrible.
2. Support for writting to a .NET application's App.config file. This would replace most registry settings. Currently we would have to write a custom action to do this, but I Think it should be included in msi because this is the new normal way of storing application settings.
3. Have someone actually test and make a high priority the SQL Server merge modules. They are HORRIBLY bug ridden as it stands right now.