Installing Microsoft signtool.exe on Windows 7- Part 2

November 19, 2013

I recently upgraded to a Windows 7 machine and needed to install the signtool on my new pc. This is a followup to the post Installing Microsoft signtool.exe posted in May 2012.

I searched the web for the download location for the Windows 7 version of the SDK and found this url: Windows SDK for Windows 7 and .NET Framework 4.

I downloaded the winsdk_web.exe file and tried to install a minimal version of the SDK since I only wanted the signtool.exe. I was not able to successfully install this version since I did not have the correct .NET version. I was getting the error message “Some components cannot be installed” message.

So instead of upgrading to .NET 4 version I returned to the previous download link and perused the archived versions. I found the download for the Windows SDK .NET Framework 3.5 SP1 archived version which is preinstalled on all Windows 7 machines. I downloaded the new winsdk.exe for this version.

I selected the same settings as I did for Windows XP version:

Windows 7 SDK options Selected

Windows 7 SDK options Selected

This installation ran smoothly and in a similar manner to the one for windows XP.

I can now access the signtool on my new desktop with a minimal windows SDK installation.


Flashbuilder 4.7 and ASUS Nexus 7 Device Driver

November 8, 2013

I am currently doing development work on a Windows 7 Machine. Based on my previous XOOM device driver installation for flex, I started out by doing the following steps:

  1. Downloaded and installed Nexus 7 usb device driver
  2. Installed the USB device driver
  3. Enabled Nexus 7 Device to allow USB debugging

Nexus 7 Device Drivers
Googling brought up the following ASUS site where I downloaded the drivers:
http://www.asus.com/Tablets_Mobile/Nexus_7/#support

I selected the support link right above the device.
The new page came up with “FAQ” selected.
I then chose “Driver & Tools”.
The OS I selected was “Others”.
I then selected the USB driver for windows and downloaded it and extracted the files from the zip file.

Nexus Website Download

Nexus Website USB Driver Download

Installed USB Device Driver
I then proceeded to loosely follow the installation instructions for the Nexus device using the following link I found in the FAQ. http://www.asus.com/support/Knowledge-Detail/28/2/Nexus_7/D53452AE-143C-42F1-BDC1-7F168085F0D7/

Enabled USB Device Debugging Device Setting
I then went to the device settings on the Nexus 7. Selected App Development and selected enable usb debugging.

Finally I was ready to debug my code on the Device. I brought up Flashbuilder 4.7 and proceeded to run my app in debug mode on the device. ACK! – I got the message that my device was recognized but it was offline!

Adobe Air Not Installed and Device Offline

Adobe Air Not Installed and Device Offline

A quick google brought up the following links from Stack Overflow:

Sooo
I read the two answers and determined that I needed to download the latest SDK for Android which I found at SDK Download from Android Developer site

Followed the instructions to copy the files to the new directories (files to copy were not exactly the same but I also kept the old ones just in case)
nexusDriverUpdatesSdk

I brought up Flashbuilder 4.7 and proceeded to run my app in debug mode on the device. And Voila it recognized my device and I was on my merry way!

EXCEPT the next day I came back and tried to debug on the device but now no devices were listed in the Flashbuilder Dialog device listing box where you choose the device to run your code.

The NEXUS was being detected as a media device and apparently I needed to change the storage mode settings to make it a camera per this online posting http://android.stackexchange.com/questions/48309/how-do-i-get-my-nexus-7-to-show-up-in-the-adb-devices-list:

I discovered that it was necessary to change my USB transfer mode.

You can do this on the Nexus 7 by going to Settings > Storage, clicking on the strange menu icon in the top right hand corner and selecting “USB computer connection”. I then changed the storage mode to “Camera (PTP)”, and it immediately prompted me with the permission dialog as shown in your post above. I was then able to deploy apps, debug, etc and it all worked.

I don’t know what I would do without all the information sharing that the internet allows individuals to provide to one another!


Creating Flex Component View using Flash CS5

September 27, 2012

We created some Flex based component views using Flash CS5 by following the instructions in the Adobe Article Combining animation and ActionScript using Flash Professional CS5 and Flash Builder 4 which we used inside our course player. These View components had text fields which would dynamically resize when the player was resized on the fly(Only for firefox and safari, IE and chrome do not allow resizing). These views also had images which would scale appropriately as well.

Note this led to my series on embedding fonts due to conflict messages with respect to flex based textfield and flash based textfields(This is explained in detail in Part 3 of the series).


Flex Mobile Device Back Button – Approach 3

July 17, 2012

In my previous post, Flex Mobile Device Back Button – Approach 2, I provided a brief overview of using states to dynamically display the appropriate device based “Back” button. I was not happy with this approach because the view ran like a dog. The responsiveness was very slow. At the end of the this post, I realized that the creation complete event would allow us to inject the child component before the view becomes visible to the user.

Despite the discussion in this post Air Mobile Performance Tip Using Flex about not recommending using creation complete event because it causes your view to render slowly, I found that this event actually provided me with the behavior I desired. The action bar “Back” button was injected before the view was made visible and the view rendering was very fast as well.

Approach 3 will copy the method used in the first approach, but will replace the ViewActivate method handler with a CreationComplete method handler.

Continue reading


Flex Mobile Device Back Button – Approach 2

July 17, 2012

In my previous post, Flex Mobile Device Back Button – Approach 1, I provided a brief overview of the ViewActivate approach to the button creation process which dynamically adds the correct “Back” button based on the device where the code was running.

Approach 2 will use states to render the appropriate button on the device.
Continue reading


Flex Mobile Device Back Button – Approach 1

July 17, 2012

In my previous post, Flex Mobile Action Bar Back Buttons, I provided a brief overview of the history of “Back” buttons for Android and Apple devices.

Approach 1 uses the Dynamic UI Pattern approach described in the previous article. In essence, I need to toggle the button to be displayed based on which device the code is currently running. This detection occurs in the ViewActivate portion of the life cycle creation of a view.

Continue reading


Flex Mobile Action Bar Back Buttons

July 17, 2012

Brief history of action bars on mobile devices:
1) Apple devices always had a “Back” button on the top action bar defined for their mobile devices.

2) Android devices depended on the hardware based back button to provide this functionality so a software based “Back” button was not included on the action bar.

This button behavior was described in a mobile skinning article on Adobe called Mobile Skinning Part 3.

Continue reading