DECLARE @DatabaseTable VARCHAR(255)
DECLARE @sql NVARCHAR(500)
DECLARE @fillfactor INT
SET @fillfactor = 80
DECLARE TableCursor CURSOR FOR
SELECT TABLE_SCHEMA + '.' + TABLE_NAME AS DatabaseTable
FROM INFORMATION_SCHEMA.TABLES
WHERE TABLE_TYPE='BASE TABLE'

OPEN TableCursor
FETCH NEXT FROM TableCursor INTO @DatabaseTable
WHILE @@FETCH_STATUS = 0
BEGIN
SET @sql = 'DBCC DBREINDEX('''+ @DatabaseTable + ''')'
PRINT (@sql)
EXEC (@sql)
FETCH NEXT FROM TableCursor INTO @DatabaseTable
END
CLOSE TableCursor
DEALLOCATE TableCursor
GO

Doc? has come and filled the void, and it does more than just providing references for Flex framework.  It is a parser that parses through online/offline ActionScript documentations, index and store the documentations in local database, which is extremely useful as I collect a bunch of open-source libraries, and the documentations come in handy.

So hit the link and give the program a try.  Don’t forget to send the project donation (or beer ) if you find it cooler than I say in the blog.

After a few minutes of googling, I came to realize that there is this free software called AirPrint Activator, which allows my Mac to become an AirPrint server.  After a minute of download and following the step, and also remember to enable print sharing, my wife was thrill to see her iPhone pictures slowly emerge from my laserjet.

Looks like Windows users are not left in the cold, there is this post showing steps to enable AirPrint on PC.  They are not as streamline as AirPrint Activator, but I am sure one day some genius is going to spend the time get it quick and easy for the mass.

Normally I would not have to synchronize my applications, but when it comes to deploying my iOS application to my device, I would have to go through iTunes.  This forces me to look into alternative to avoid all the hassles.  My Google search quickly led me to TestFlightApp.com, within minutes, I am able to upload app, distribute it to team for testing, and even collect statistics and crash data.  It just works!

Error #2044: Unhandled securityError:. text=Error #2048: Security sandbox violation: file:///some_path/.metadata/.plugins/com.adobe.flash.profiler/ProfilerAgent.swf?host=localhost&port=### cannot load data from localhost:###

I have tried to install/uninstall Flash debug player as well as Flash Builder, but both still yielded the same error.  It has taken me some time to find out a solution to get profiler working.

Step 1: Make sure the ProfilerAgent.swf is allowed in Flash’s global security setting

This is done by adding the location of the ProfilerAgent.swf in Flash Player’s Trusted Location Settings.  The setting may be changed in Windows’ Control Panel as screenshot below:

Step 2: Edit mm.cfg file to enable Profiler

To locate the mm.cfg, type in %HOMEDRIVE%%HOMEPATH% in Windows Explorer’s address bar, or follow the instruction here.  Open the mm.cfg in Notepad or your favorite text editor.  The configuration in mm.cfg is a bunch of simple setting=value.  Adobe only provides a subset of settings in their instruction, but there are a lot more undocumented settings.  To cut to the chase, make sure the following settings are in mm.cfg

 ProfileFunctionEnable=1
 ProfilingOutputFileEnable=1
 RendererProfilingEnable=1

Save the changes, and restart the profiler (no computer restart necessary), and ditto!

Traditional Approach

Traditionally, assigning a value to a server control involves a code-behind assignment, for example, assigning a label with a person’s birthday would have code similar to the following:

<!--ASPX-->
<asp:Label id="lblBirthdayDate" />

//C#
lblBirthdayDate.Text = person.Birthday.ToLongDateString();

If somewhere in the page the birthday should also be displayed as short date, developer would then have to create another label, and assign it:

<!--ASPX-->
<asp:Label id="lblBirthdayDate" />
...
<asp:Label id="lblAnotherBirthdayDate" />

//C#
lblBirthdayDate.Text = person.Birthday.ToLongDateString();
lblAnotherBirthdayDate.Text = person.Birthday.ToShortDateString();

Let’s say later, customer would like to see birthday information displayed different, such as removing one label or another, developer would have to remove the label from the ASPX markup as well as the code behind, recompile the DLL and deploy both the DLL and the markup.

Things can quickly get out of hand and any changes would take long time to develop, test and deployment.

The new databinding approach comes to rescue this mess.

The New Approach

The address the scenario above, only two additional lines of logic need to be introduced to the code behind:

public class MyPage : System.Web.UI.Page

{

public PersonModel Person { get; set; }

protected override void OnPreRender(EventArgs e)

{

base.OnPreRender(e);

Person = new MyPageController().GetCurrentPerson();  // for the purpose of the page, we are not discussing how the data is retrieved.

DataBindChildren();

}

}

The aspx markup would look like this:

Person's Birthday:  <%# Person.Birthday.ToLongDateString() %>
...
Person's Birthday Date in Short Form: <%# Person.Birthday.ToShortDateString() %>

Why the New Approach

The new approach offers a few advantage over the old approach:

1. Separation of Concerns

The new approach has the code behind focus on gathering the raw data the page would need to render its content.  It, however, does not have to concern about how the content should appear (ie. color, css, or even data formatting).

The markup of the page concerns about how the content (in a model like class) should be rendered, it is not responsible for gathering the data but rendering data as is.

This saves back-end developers from concerning the appearance of the page, but focusing on gathering all the data the page needs, and exposing the data to the markup.

2. Clarity

Because of separation of concern, the markup code becomes clear how the data should be rendered, instead of being intertwined with a page’s life-cycle.  The sample above issues the databind at OnPreRender, this allows all controls properly initialized before data is bound to the controls.

3.  Testable

For developers, because the code-behind is now responsible for data gathering, it is possible to develop unit test to test if the page model has the correct values; as for designers, they can develop mock page model values to ensure that controls are properly rendered.

The Eclipse way: StartExplorer plugin

The Visual Studio way: PowerCommands for Visual Studio Addin from Microsoft

For those who hate plugin’s and wish to add such feature manually in Eclipse, there are approaches through External Tools over here, and here.

To fix this error, one of the ways is through changing the Web.config to allow larger request size limit, this can be achieved by changing the setting under system.webServer / security / requestFilter / requestLimits @ maxAllowedContentLength . For example:

Remedy:

<system.webServer>
  <security>
    <requestFiltering>
      <requestLimits maxAllowedContentLength="56700000" /><!-- in bytes -->
    </requestFiltering>
  </security>
</system.webServer>

Related Post: Large file uploads in ASP.NET

http://yerii.wordpress.com/2010/12/15/why-has-flex-sdk-4-x-x-become-sluggish-for-some-and-how-you-can-get-it-rolling-again/

The error – “TypeError: Error: #1034: Type Coercion failed” seems to throw even before the Flex application is initialized as none of stack trace information indicates code error from my Flex application.

I then created another empty Application in the same Flex project, strangely enough, I have the same error; but with a different project I see no issue.  This leads me to believe that something is  wrong with the library I have used.

Eventually, I have located the code:

/** Flag for initializing the styles */
private static var classConstructed:Boolean = classConstruct();

/** Initialize styles to default values */
private static function classConstruct():Boolean
{
if ( !FlexGlobals.topLevelApplication.styleManager.getStyleDeclaration( "SomeComponent" ) )
{
// If SomeComponent has no CSS definition,
// create one and set the default value.
var newStyleDeclaration:CSSStyleDeclaration = new CSSStyleDeclaration();
newStyleDeclaration.setStyle( "selectorColor", 0xFF0000 );

FlexGlobals.topLevelApplication.styleManager.setStyleDeclaration( "SomeComponent", newStyleDeclaration, true );
}
return true;
}

Apparently the code above causes the problem, which might have something to deal with deprecated code since Flex 3.

Through the exercise of hunting down this runtime error, I concluded the steps of troubleshooting such kind of error.

1. Create an empty project with an empty movie, if it runs, that means Flex Compiler is healthy.
2. Create an empty Application with the problematic application, if it runs, that means the Project has issue with its libraries; otherwise, the problem may lie in the code of the application.
3. One-by-one, remove the SWC libraries referenced by the application, and run the empty Application everytime an SWC is removed until the error disppears.
4. Troubleshoot the issue in the problematic SWC.

Happy Flexing!