Blog: Posts from January, 2012

Blog

Posts from January, 2012

Saturday, January 21, 2012Print Subscribe

Code On Time release 6.0.0.19 includes new code generation project SharePoint Factory and miscellaneous product enhancements.

This release includes the following features and enhancements:

SharePoint Factory web application project.
Theme page of the project wizard now offers an index of all theme samples.
New themes: Mission, Laminate, Grapello, Graham, Convention, Construct, Cay, Bittersweet, Berry, Municipal.
DotNetNuke Factory will produced a Visual Studio 2010 project if Visual Studio 2010 is detected.
New "strongNameKey" code generator instruction creating a random key pair with the help of Strong Name Utility is integrated in the code generator. If the SNU is not available then the standard key is copied from the library to the output. This feature is provided to support SharePoint Factory.
EASE EventTracker class has been updated to ensure compatibility with Visual Basic.
Alias Field Name property of data fields is left blank if the Discovery Depth is set to zero.
Suppression of duplicate foreign keys is now performed by the code generator in all project types. Duplicate foreign keys were previously causing erroneous code generation.
"Project Refresh" window now offers Select All/None buttons to allow quick selection of all items.
Quick Find performs a case-insensitive search in projects using Oracle backend.
Settings "Features | Grid | Enable standard action column in all grid views" will add an action column to all views of an application.
Click on a "View Details" link next to a lookup field in a master view will not stop refreshing of child views when the selected master record has changed.
Slow running detail views will automatically cancel data requests if the master has changed. The previous implementation may have resulted in the wrong detail data displayed if the selected master record has changed before all details were retrieved.
It is now possible to process "Report..." actions in business rules.
Designer log progressing progress in now displayed in the log box of the code generator. This will be noticeable with large change longs only when the project is refreshed.
Batch Update in grid view will not raise an "Unauthorized command..." exception when user tries to save the changes.
Connection String Name defined in the data controller properties is correctly used in the generated apps. Read about implementing multi-database projects at /blog/2012/01/multiple-databases.html.
Check for updates is automatically initiated when an activation code is registered.

Labels: Release Notes, SharePoint, Web 2.0, Web Application Generator

Tuesday, January 10, 2012Print Subscribe

Multiple Databases

Multiple Database support has been added in Code On Time web applications. The feature will be available in the next release. If you want the capability now, submit a ticket and request the multiple database hotfix.

Learn how to set up a web application that accesses data from multiple databases at /Documents/UG-Multiple_DB.pdf.

Monday, January 9, 2012Print Subscribe

Converting Designer Spreadsheet to Baseline

Code On Time’s Designer Spreadsheet has been a popular tool for editing Code On Time applications in a rapid fashion. Unfortunately, it uses a different method for saving changes and has been phased out of use. However, this feature will soon be replaced with a new and improved version – Code On Time Tools for Excel. Those of you who used Designer Spreadsheet on your projects will need to migrate a few files to make sure all your changes are migrated to the newest version of Code On Time Generator.

First, you will need to find the folder location of your project. This can be easily done by running Code On Time Generator, selecting the project name, and press Open. Alternatively, you can navigate to My Documents/Code OnTime/Projects, and find it there. The folder should look like this.

You will need to delete the following four files:

Application.Baseline.xml

Application.Cache.xml

Controllers.Baseline.xml

Controllers.Cache.xml

All the changes made to the application in the Designer Spreadsheet are recorded in the file Controllers.Master.xml. Make a copy of the file, and rename the copy to Controllers.Baseline.xml.

You will need to make one more change to ensure that categories are processed correctly. After the Designer Spreadsheet was released, an id parameter was added to all categories. This field will need to be added to all of the old categories in the baseline file. Otherwise, Code On Time Designer will not place any data fields in the categories, as shown below.

Open this file in your preferred editor (we used Visual Studio). Find the first category, and add an id parameter to this category.

You will have to perform this operation on the rest of the categories as well. Find and Replace (Ctrl + H) is highly suggested at this time. Each category in the same view must have a unique id. If you have added multiple categories to the same view, you must manually change the id.

Once all the categories have an id, it is safe to save this file and open the project in Code On Time Generator. You can see that the data fields are now correctly nested in the proper category.

We apologize for any inconveniences this move may have made, but we believe that you will find Code On Time Tools for Excel to be a vast improvement, and well worth the upgrade.

Labels: ASP.NET, COT Tools for Excel