We at Icetips wish you all Happy Holidays and a Happy New Year!
We hope that 2019 will be a good and prosperous year for all of us!
Clarion 11 Builds are ready!
It's taken a while, but all our product installs are now compatible with Clarion 11 and available for download!
This process took quite a bit longer than I expected, mostly because this required considerable amount of work for most of the templates to make them look better in Clarion 11. But I think it was definitely worth it! While I did not do a lot of design work, what needed to be done was duplicating a lot of code to make it work with both Clarion 10 and older as well as with Clarion 11.
I also took the opportunity to add more standardization to the Setup Builder install scrips as well as my Build Automator scripts to make builds easier in the future. Same applies to the templates, where for example template headers look exactly the same in all our templates now, and the support tab is now 100% identical everywhere to make it easy to access.
Another task was to change all the templates from using .hlp help files to use .chm help files. .hlp files are not really supported any more on Windows 10 and the IDE has supported .chm for a few versions now so there is no reason not to use it. So I decided to pull the plug and change all the templates that had help file access to use .chm files. This required a minor change also to every HLP link in the templates.
For the first time I did not do any testing with the old IDE, i.e. Clarion 6, apart from making sure the templates registered, since I still have a few Clarion 6 apps that I need to maintain for a while longer, so I still need them to work in the old IDE 😉 But by the end of the year, I will ONLY support the new IDE and generally just the last 3 versions. So 9.1, 10 and 11 by the end of the year. Keeping everything backward compatible has limited me in certain visual design aspects. Clarion 6 is 15 years old (2003) and Clarion 6.3 is 9 years old (2009) and it's time to let it rest 🙂
Since there have been quite a few changes in both the templates and in the build process, I would really appreciate if you would let me know as soon as possible if you have any problems with the installers - or the templates!
Enjoy 🙂
Clarion 11 testing
Clarion 11 testing is going well! But I'm still not done with updating to Clarion 11 compatibility - close but not quite there.
On a very positive note, I have not found any issues at all in Clarion 11! I'm running C10 and C11 side by side and both have worked without a glitch! Softvelocity is releasing Release Candidate (RC) 2 today and announced that Clarion 11 Gold is close, see their latest blog post here: http://clarionsharp.com/blog/clarion-11-rc-2-released/
I apologize how long it's taken me to get these builds out!
Clarion 11 builds
Clarion 11 builds are getting closer and I hope to have them all sorted this weekend and push them out next week, starting Monday, October 1st.
One of the changes in Clarion 11 is in the template interface. After many years it has finally happened - the template window has been widened! That presented a bit of a problem with the presentation as now we have two distinct visual designs - one for Clarion 11 and later and one for Clarion 10 and older. The old format we have grown accustomed to over the past 25 years without much change still looks like it always has.
The new template window is considerably wider and fits much better with today's large and high resolution monitors.
Some of our template windows will be updated to take advantage of the added real estate, but I'm not sure if that will all be included in the initial builds for Clarion 11.
One change that will be across all our products - the version number will change to be year.month.build. That will help immediately identify the release time of the template to help with support. As always the version numbers and support information will keep being included on every template window.
Another change that is coming is that by the end of this year we will no longer test or support backward compatibility with the old 16bit Clarion IDE. I have to maintain several 32bit Windows virtual machines, which gets to be quite expensive and the 3GB memory limitation in 32bit operating systems doesn't leave much room for the new IDE along with other development tools. So after January 1st, 2019 we hope to have all demo apps etc. upgraded to Clarion 9 or 10 only and the last builds of 2018 will be the last builds that support Clarion 6 and older. We may leave the installers to support the older IDE for now, but we will no longer support the old IDE. Clarion 6.3.9059 was released in early 2009 and I think 10 years is a pretty good run for a development environment. Time to move on 🙂
Improve performance when compiling with Build Automator
Build Automator uses MSBuild to compile projects and solutions no matter if they are in Visual Studio or in Clarion. By default, MSBuild is a single thread program, but there is a way to tell it to start multiple processes to compile.
After some experiments on a virtual machine, I'd say it's definitely worth it to try it out and see if it helps. What you need is the /maxcpucount parameter which you can add to the "Additional Parameters" tab on the "Call MS-Build" action in Build Automator.
The benefit may not be as much as you had hoped for, but it definitely does improve performance. Here are some numbers. This was tested on a Windows 10, 64bit virtual machine in VMWare 12.5. It is set up with 5.7GB of RAM. In the first test it was set to use 1 CPU and 2 cores.
| 15:42:59.898 | ||
| 15:45:54.809 | 00:02:54.911 | without /maxcpucount |
| 15:33:22.832 | ||
| 15:36:04.000 | 00:02:41.168 | with /maxcpucount:2 |
| 15:52:48.811 | ||
| 15:55:21.083 | 00:02:32.272 | with /maxcpucount:8 |
In this test, I was able to shave off about 38 seconds with the 8 CPU setting. Your milage may certainly wary as this may be different outside of virtualized environment and it may be different depending on what CPU you have and a lot of other configurations. No errors were reported and everything seemed to compile correctly.
All generated files were destroyed before each test and ClarionCL.exe was used to generate. The Clarion IDE was not involved at all in this process and was closed while the testing was performed. Only command line utilities.
Bottom line is if you are compiling larger solutions with Build Automator, then you should check out the /maxcpucount parameter. For more information about this parameter, please see the information on the MSDN Website
SSL Expired and renewed!
Yesterday, Saturday, a customer contacted me and told me that icetips.com was not working. Sure enough the SSL certificate had expired!
It has been fixed now, but it took me a while to figure out exactly where and how I had set up the certificate originally! Icetips is hosted on hostgator.com and after looking at comodo and godaddy and not finding any information about my last certificate I finally figured out that hostgator.com is kind enough to give one SSL certificate for free to their business and re-seller customers! So it was a quick fix after all and the website should be working correctly again - at least it is from our office!
Apologies for any inconvenience this temporary problem may have caused!
Code signing – warm and fuzzy?
Couple of days ago I stumbled on an excellent article about the pitfalls of code signing!
Couple of excerpts:
"Now, researchers have presented proof that digitally signed malware is much more common than previously believed."
"Surprisingly, weaknesses in the majority of available AV programs prevented them from detecting known malware that was digitally signed even though the signatures weren't valid."
"The third key weakness in the code-signing ecosystem was the failure of certificate authorities to verify the identities of people applying for code-signing certificates. "
"Malware with the same digital DNA as Stuxnet—Duqu discovered in 2011 and the Duqu 2.0 that infected Kaspersky Lab's corporate network starting in 2014—also used code signing."
Just because an executable is code signed does not really tell much. You can EDIT code signed executables and they will run just fine - assuming that you do not change the binary code that actually makes them run;)
You can protect your software by validating the code signature inside the application. That way if the signature is tampered with, you can prevent the program from running.
Build Automator 2016 build 6.2.1359 released
We have released Build Automator 2016, build 6.2.1359
The full install can be downloaded from the Build Automator website at http://www.buildautomator.com/downloads.php or by using the "Check for Updates" option under the Help menu in the program.
This build has several fixes including:
- Clarion 9.0 installs were not always detected correctly.
- Clarion 10.0 installs did not always show up as available version if only one more Clarion version was installed.
- Icons were missing from some buttons as well as from some windows.
- Maintenance Plan verification did not always work correctly.
- Registration window was too short to show all the information.
- In some circumstances {#INCLUDE(FileName)} could add 2-5 characters at the end of the resulting file.
There were some bugs in the Clarion 9 and 10 implementation. I have simplified it so it should be easy to add new versions of Clarion as they are released.
The {#INCLUDE()} statement for the "Write Text To File" action had a bug in it causing extra characters to be written at the very end of the final file.
For more information, and some extra tips please read the full blog post on buildautomator.com
Build Automator 2015 build 5.12.1344 released
We have released Build Automator 2015 build 5.12.1344
The full install can be downloaded from the Build Automator website at http://www.buildautomator.com/download.php or by using the "Check for Updates" option under the Help menu in the program.
There are several new features in this build, but there are also a lot of fixes behind the scene that make the program more stable than it has ever been. The new feature list includes:
- Full support for Clarion 10
- Full support for SetupBuilder 10
- Support for Code generation before build in Clarion 8, 9, 9.1 and 10
- Drag and drop from Explorer is now supported on all entry and lists that use file names.
- Generate Manifest now fully supports Windows 10.
- Both the install and the program files are dually code signed with both SHA-1 and SHA-2 code certificates, prepared for Microsoft dropping support for SHA-1 certificates in 2016.
But the main change is that Build Automator 2015 is completely built in Clarion 10. We had decided that Build Automator 2014 would be the last build we did in Clarion 6.3. It had served us well, but it really was time to move on.
It was not a pain free move! Clarion 9.1 would consistently throw a non-descript "internal compiler error" on one of our classes and no matter what I did, it would never compile that particular code file. Clarion 10 came around and lo and behold it would compile this particular file with no issues. So on went the conversion process. I found a few bugs along the way, both in Clarion and Build Automator! Window resizing changed between Clarion 6.3 and Clarion 10 - don't know when - and it caused problems with most of the action windows causing quite a bit of work to get around that.
I would have liked to have more new actions and features in this build, but it has taken so long to get it together that I didn't want to wait any longer! But with Build Automator now in Clarion 10 it will be much easier to dive back in and get some new things going.
FTP and Email are two of the things that I want to add and improve. Currently you can only upload files, not download or do any other fancy stuff. It would also be nice to be able to send emails from it in case of errors and attach the log file. Version control is another thing that needs better support. Although I have implemented TortoiseSVN using "Run Program" and it runs great, it would be nice to have a more native support for the most popular version control programs today.
Our support for Clarion 6 is coming to an end. While the actions to compile with the old IDE will stay in the Build Automator IDE there will be no further development on them. One of the features I want to add is more flexibility in the MSBuild action, so that it could for example be used to build multiple solutions or multiple projects, in a similar way as the "Compile Multiple Clarion Applications" where there is a list of items to compile.
Arnor Baldvinsson
Save on renewals – last chance!
On October 15th, 2015 the renewal prices for expired Icetips subscriptions will go up. Until then you can renew for the same price as non-expired subscriptions and save money!
If you go to http://www.icetips.com/compare.php and look at the second table from the top, "Prices for Gold & Silver Subscriptions" you see a column with "Renewal Price Expired"
Those prices do not take effect until October 15th, 2015!
On October 15th all subscriptions that have been expired more than 30 days will have to be renewed at a higher price.
Check it out and log into your account to check your subscription status.
Arnor Baldvinsson