Skip to main content

Getting an AppleID Without a Credit Card

So you bought a new iPod Touch . You have heard a lot of those cool games and cool applications that runs over it . You opened up iTunes and excited to see what is in store for you . Last thing you know , Apple is asking you for a credit card number . Boom ! all that excitement is gone.

For an average iPod owner who does not have a credit card number or does not want to have one , applying for an Apple ID to get hold of those freebies and goodies Steve Jobs has to offer is a pain in the ass . But there are several ways to get over with it . One , you could buy a iTunes gift card and redeem it . This is good , if and only if , gift cards are available . Two, try jailbraking your iPod touch and risk voiding its warranty . Lastly , read on and follow the steps below. Just a note , I assume that you are responsible enough to take care of yourself . Take note that even if the software is free , a billing statement will be sent to you registered email address . And if you intend to buy one , pay for it.

1. Launch you iTunes application and go to the iTunes Store .
2. Scroll down to the bottom of the page and select the country. The country is significant , different country can mean different offered applications.

3. Go to the Top Free Apps widget and click on the top free application.
4. Clicking on the Get App button prompts you to enter your AppleID , select Create New Account.
5. Proceed and create a new AppleID account.
6. If you got all the previous steps working , you may be able to see the "NONE" option on the Payment method section.

7. Select the NONE option and provide the billing information . Make sure that your address is a valid address from the country you have choosen in Step 2.
8. Click CONTINUE and you are good to go.

Comments

Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :

"**/*.pyc":{"when":"$(basename).py"},"**/__pycache__":true

renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!



I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

Automatic Properties and Object Initializers in .Net 3.5

With the release of .Net 3.5 alongside with Visual Studio 2008 , new enhancements was again introduced . Some maybe well pronounced such as the inclusion of WCF, WPF , LINQ in .Net 3.0 and some just came unnoticed. If you have been accustomed of using a particular method or technique in implementing a certain code in .Net 2.0 , because of backward compatibility , you may not even notice that there are new ways of implementing it in .Net 3.5.

Here are two new concepts in .Net 3.5 that a developer may not notice ( at least in my opinion ) : Automatic Properties and Object Initializers . To illustrate these two , I am going to present the pre-.Net 3.5 way (.Net 2.0) and the .Net 3.5 way in creating a simple class with simple properties.

Automatic Properties

Creating a class can be tedious , especially when working with a list of properties , . One way to get around having to type the code for a private field and its public property getter and setter is to use a refactoring tool. However, …