Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change the default Additional Tasks options when the Firebird is installed [CORE3562] #3917

Open
firebird-automations opened this issue Jul 21, 2011 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @luronumen

Attachments:
Setup-Firebird.png

IMPROVEMENT 1: [Use the Gardian to control the server?] option should be disabled by default.
- As the default Firebird server option is set to [Run as s Service?] and Based on http://www.firebirdfaq.org/faq31/ comments the Guardian is not necessary and should be disabled by default.

IMPROVEMENT 2: ["Install Control Panel Applet" ] option should be disabled by default.
- Since Windows Vista the Firebird Control Panel Applet is not working well. Based on Bug CORE3390 comments the Firebird Control Panel Applet is not necessary and should be disable by default.

IMPROVEMENT 3: [Generate client library as GDS32.DLL for legacy app. support?] option should be disabled by default.
- The Firebird already have several native driver to connect with the database (Java, .NET, Python,C/C++, Delphi etc) and do not need to keep compatible with the Interbase. who are still using a Interbase application with a Firebird application needs to install GDS32.DLL library. Most of new Firebird Project do not need the GDS32.DLL library.

@firebird-automations
Copy link
Collaborator Author

Modified by: @luronumen

Attachment: Setup-Firebird.png [ 11976 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @reevespaul

Overall the binary installer is designed to produce a click through installation for the widest audience. I'm not convinced that disabling any of these options helps new users. And consistency is something that is appreciated by existing users that are not Firebird experts.

Point 1 - Really the question ought to be whether we continue to ship the guardian. If we do then it should be enabled by default for SS. It is already disabled by default for CS.

Point 2 - I've already made a comment on CORE3390 that the problem may not be caused by the cpl applet.

Point 3 - There are still a lot of applications out there that expect to find gds32.dll.

BTW, the installer will undergo a major overhaul for Firebird 3.0 so it would be better to wait for the first official Alpha/Beta release of that. That will be the time to discuss changes and improvents.

There is little point in changing the installer up til 2.5 because 2.1 and 2.5 are now in maintenance mode.

@firebird-automations
Copy link
Collaborator Author

Commented by: @luronumen

Point 1 - I think that the Firebird do not need more the Guardian and it can be removed in the next version.
Point 2 - I will try to reproduce the CORE3390 bug based in your comments but I still thinking that the Firebird does not need a Control Panel Applet to start/stop the Firebird Server.
Point 3 - I think that compatibility with Interbase can block the Firebird improvements in the future. I think we should forget this compatibility in the Firebird 3.0.

For me, the main features of the firebird are:
1 - SQL standards compliance;
2 - Small install package and easy to install/configure;
3 - low level of corruption of data;
4 - high capacity data processing;
5 - A powerful procedural language;

and I think that if we continue investint in it we will have more Firebird users.

Please take a look at these suggestions when you will have creating the Firebird 3.0 Installer package.

Best Regards,
Luciano

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

Regarding the Guardian functionality. Support already exists for Windows (starting with Windows 2000) to automatically restart services should they fail/die for any reason.

Since this is the main function of the Guardian, we should be replacing it (when "install as a service" is selected) with changes to the install kit which would activate the Recovery options of the Windows Service manager.

The Recovery options are managed using the ChangeServiceConfig2 Function of the service control manager (OpenSCManager) interface. Here is a link to a post on an MS site which contains a code snipet showing how the changes can be applied.

http://social.msdn.microsoft.com/Forums/en-US/csharpgeneral/thread/93b084d7-f7e9-49b9-8f88-b8f8e3c49aa5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant