General
Apex SQL Audit
Apex SQL Clean
Apex SQL Code
Apex SQL Data Diff
Apex SQL Debug
Apex SQL Diff
Apex SQL Diff API
Apex SQL Doc
Apex SQL Edit
Apex SQL Enforce
Apex SQL Log
Apex SQL Log API
Apex SQL Recover
Apex SQL Refactor
Apex SQL Report
Apex SQL Script
Apex SQL Source Ctl
Apex SQL SSIS Compare
Developer Diary Home
Apex SQL Audit
Apex SQL Clean
Apex SQL Code
Apex SQL Data Diff
Apex SQL Debug
Apex SQL Diff
Apex SQL Diff API
Apex SQL Doc
Apex SQL Edit
Apex SQL Enforce
Apex SQL Log
Apex SQL Log API
Apex SQL Recover
Apex SQL Refactor
Apex SQL Report
Apex SQL Script
Apex SQL Source Ctl
Apex SQL SSIS Compare
Developer Diary Home
|
Developer Diary Posts, comments, and articles straight from ApexSQL Developers and Analysts Even better ApexSQL Edit 2008 in 2009 A quick retrospective - we are aware that there's been an inexcusable release gap between last ApexSQL Edit 2005 version and the first ApexSQL Edit 2008. We're also aware that we have more to improve the quality of Edit 2008 to surpass all previous releases. The immediate next Edit 2008.03 release in January 2009 will do that and the following releases will be even more improved, both old and new features. As soon as we clear the first milestone mentioned in yesterday's post to achieve and surpass previous Edit releases quality and make sure all new Edit 2008 features function well, our immediate next milestone will be simplifying the Source Control implementation. For now we are focused on the first step ahead, ApexSQL Edit 2008.03 release. Daily QA testing is steadily closing reported issues but also finding some new ones. Good thing is that we are receiving less and less new priority issues and almost closed off all of the old ones - almost fixed all of the features which worked in Edit 2005 / 2008.01, and now all are in even better quality. One of the major faults of the new Intellisense engine was auto-replacements feature which just stopped working. Today we corrected this and reintroduced it back. Both internal and some external QA will make sure no new issues have been introduced and the fix is valid. More bugs were fixed today, including Insert Object Owner Intellilist option functionality, a number of special cases when using F2 to script objects and an exception. Thanks to the outside QA help we found that there was a F9 shortcut conflict with Show/Hide Explorers Pane and Show/Hide Results when CtrlRHideResults option is not set. This is now fixed by refactoring some default shortcuts and setting the F7 as Hide/Show Explorers Pane keyboard shortcut. Happy New Year from all of us in ApexSQL and thanks for helping us make Edit the best SQL editor out there! Thanks, Goran Bogdanovic ApexSQL Edit Development Team Leader Get your developers the tools they need to do the job fast and right - ApexSQL Developer Studio is the ultimate combat multiplier for SQL Developers. 7 Best of Class tools - one download, install and discounted price. Click Here for more info. Labels: ApexSQL Edit |
© 2008 Apex SQL Tools All Rights Reserved | 1.919.968.8444 | Contact Us | Terms of Use | Privacy Policy
