I'd like to make a suggestion to Clint: You need to contact the splendid folks, because your team clearly does not know how to deliver an application on the Windows platform. I'm going to prove my point by documenting what it takes to install the latest SugarCRM 4.5 build for Microsoft and the latest build from the splendid folks.
Splendid goes first because it is easier, faster and it works the first time:
1) Download splendid setup.
2) Run splendid setup.
3) Click Next a few times until setup begins installing files.
4) The configuration application is automatically run, so you have to click Next a few more times to configure the application.
5) The application is launched at the end, and all is working well.
It is important to note that the splendid install automatically installs .NET, IIS and SQL Server. It does everything necessary so that a novice can install the application.
Now we contrast the Splendid install with a Sugar Suite for Microsoft install:
1) Download SugarSuite-for-Microsoft-4.5.0.zip.
2) Download PHP5.
3) Download SQL Server Express.
3) Unzip PHP5, read documentation, search net for configuration instructions, pray.
4) Unzip SugarCRM 4.5, read documentation, search net for configuration instructions, pray more.
5) Install SQL Server Express. No praying necessary as Microsoft knows how to install an application on Windows.
6) Configure IIS to allow PHP pages to run. This typically takes an experienced Windows developer.
7) Run http://localhost/sugarcrm/install.php, things look like they are going to work, but experience suggests that we should pray more just in case.
8) Click next a few times, provide critical configuration information, click next, then BLANK SCREEN.
9) Curse some, pray more, hit back button, hit next button . . . NOTHING.
10) Search SugarCRM forums for issues with install.php and blank screens, try some PHP.INI suggestions . . . NOTHING.
11) Laugh a little bit given that Sugar Suite cost $29M in venture funding to develop, and it still does not work.
12) Give up and post message for Clint on SugarCRM forums.
So who is to blame for this fiasco? Is it the developer that could not get the code to work, or at the very least, tell us what is wrong instead of the blank screen? Is it the QA team that should have tested this and not let the product out the door until it worked? Is it the installation guy who created the setup application? Actually, scratch that last one as Sugar does not employ anyone who can create a Windows setup application. Is it Clint who saw fit to post the SugarSuite-for-Microsoft-4.5.0.zip on CodePlex as a way of say "Yes, SugarCRM will run on Windows IIS and SQL Server", when clearly it can't? While we are at it, we could blame Clint for not hiring someone that could write a Windows setup application. You would think that with $29M in funding, they could afford to pay a guy $60K/year to write a Windows setup application. The Splendid folks can, and I don't think that they are as well funded, if at all.
My evaluation is over. Splendid has won.


LinkBack URL
About LinkBacks
Reply With Quote




Bookmarks