Posts Tagged: General Programming


29
Dec 11

Life cycle model of Windows Phone apps and Tombstoning

Life cycle of program instances differ greatly between desktop and mobile and Windows Phone is no exclusion.Its essential to understand the application life cycle model before writing apps. Of course there are quite a few article explaining this but none pointing out the difference between SDK7.0 and SDK7.1. This article, briefly lets you understand the different states and the life cycle model changes between SDK7.0 and SDK7.1.

States

In Windows Phone (WP), every app goes thru’ three different states after its instantiated. Continue reading →


29
Dec 11

Starting off with Windows Phone 7 Programming

Windows Phone 7

Windows Phone 7 - Wikipedia

As I had mentioned earlier that I am planning to start off with Windows 8 programming, I also thought it would be logical to start off with Windows Phone 7 programming. I know, Windows Phone 7 has got nothing to do with Windows 8 programming, except for the UI and thats the reason. User Experience is really important, especially for handheld devices.

Here are a few things you need  before you kick start with Windows Phone 7 programming.

  • .NET and Visual Studio – you ought to be familiar with .net and Visual Studio.
  • WPF (xaml to be precise) – at least the fundamentals. The book that I have linked underneath lets you learn the basics but still I suggest a book that talks just about xaml (?!?).
  • **Silverlight – not necessarily; ifyou know WPF, well, thats enough.
  • Visual Studio 2010 with SP1 and Windows Phone 7.1 SDK.
  • Book or some kind of tutorial – obviously we start off with a book. Programming Windows Phone 7 by Charles Petzold is what I am currently learning.
  • Windows Phone – even though you get an emulator with Visual Studio Windows Phone 7 SDK, the emulator is every simple and you might not find it useful if you are planing to write complex applications involving multi touch gestures, notifications, etc.

I just started off with Windows Phone 7 programming last week and is really cool. I am finding it very simple as I have been working on .NET, C# and WPF for quite some time now. If you are new to WPF, I suggest you learn it and get acclimatized to the XAML fundamentals and syntax before you start off with WP7 programming. I will also try and write about things which I find notifiable, out here.

So long, lets write some Windows Phone apps ;-)


18
Dec 11

Windows 8 – Build

Windows 8

Windows 8

Windows 8. I tried out the OS last month; pretty neat. So now, I am planning to start off with the app development.

This is where I am gonna start from. Hoping to write more soon.


8
Jan 11

From .net to iOS

Its been a week since I started off with application development using iOS. So far the experiences has been awesome. So if you want to write programs for iPhone/iPod/iPad, all you gotta do is,

  1. Get a Mac. You cannot develop apps from your pc. I tried using virtual machine, but it is NOT POSSIBLE AT ALL. Forget about your pc. Go get your mac !!
  2. Once you have your mac, navigate to http://developer.apple.com. You have so many resources out there which should get you on board immediately

Tips for beginners,

  • Development Center – is really neat and way ahead than MSDN
  • Programming Paradigm – is MVC and should be familiar if you were programming for quite a while
  • IDE – XCode and InterfaceBuilder are the IDEs with which you write programs for iOS. Thou’ they are not as good as Visual Studio, they are pretty good for beginners
  • Programming Language – ObjectiveC – so far is the biggest challenge for me. If you are new to this, you will find it to be really weird
  • Unmanaged Code – if you are a .net programmer with no experience writing C/C++ programs, you should be extra careful in here
  • Tutorials and Samples – development center has got everything for you. Do not worry about this

Overall, the experience is good and exciting so far.


27
Nov 10

Visual Studio Equivalent

For those who wish to write c# code and cannot afford to buy Visual Studio, you have “Sharp Develop“, a open source comparable to Visual Studio.

One more happy news, they even have a WPF designer is a quite awesome. Give it a try


13
Jan 10

DoUNo: MDI in WPF

WPF, out of the box doesn’t have provision for MDI windows. The reason is quite simple, MDI windows are outdated and most of the applications have been using tabbed documents, proving they are really easy to use. Although the framework is flexible enough for you to make such a feature, its better to move to tab based interface.


6
Nov 09

DoUNo: Setting expectations on nullable type, NMock2

Ever had a problem of setting an expectation for nullable objects?

If you wanna return false when .HasValue of a nullable object is called, then you cannot do it with the normal expect statement. Rather, try not returning any values, because NMock2 returns default value of HasValue (False) if nothing is set as return values in expect statements.

Here is a sample,

public interface IProduct  //Interface that has a nullable member
{
  int? ProductNo  //Member that I wanna test and I wish to test the scenario in which this will be null
  {
    get;
  }
}
IProduct aProduct= myMockery.NewMock<IProduct>();
//Stub.On(aProduct).GetProperty("ProductNo").Will(Return.Value(default(int?));  //this statement produces a runtime exception, so we have to use the following instead
Stub.On(aProduct).GetProperty("ProductNo");  //no return value is set, nmock2 returns false when .HasValue is queries

Hope this helped you.

Sudarsan Srinivasan
- on behalf of my friends (they found this hack :P )


31
Aug 09

Accessing Command Prompt from C#

Recently, I wanted to write a program in c# that should start the command prompt in the background (it should not show the cmd window), give inputs from my C# program and get the results redirected back to my C# application. I was googling around a bit and then came up with a solution.

Its damn simple. Usually to start any process from C# applications, we use the Process object. The process object has two properties called StandardInput and StandardOutput. These properties will allow the C# application to get the input stream of the process that needs to be started. So to mock inputs and outputs, we need to do the following,

Process aProcess = new Process();
ProcessStartInfo aStartInfo = new ProcessStartInfo();
aStartInfo.FileName = Environment.GetFolderPath(Environment.SpecialFolder.System) + "\\cmd.exe";
aProcess.StartInfo = aStartInfo;
aProcess.StandardInput.WriteLine("dir");  //will open a cmd process and feed the command "dir" to it

By this way you could give inputs to a process that you start from C#. What if you wanna see output of the cmd prompt in your own prompt ?? For this we use the StandardOutput property. But there is yet another simple way to get the output from the command prompt. This is done by subscribing for the event, OutputDataReceived.

aProcess.OutputDataReceived += new DataReceivedEventHandler(Process_OutputDataReceived);
private void Process_OutputDataReceived(object sender, DataReceivedEventArgs e)
{
  textBox1.AppendText(e.Data);
  textBox1.AppendText(Environment.NewLine);
}

Note: These ways are possible only if,

aProcess.RedirectStandardOutput = true;
aProcess.UseShellExecute = false;
aProcess.BeginOutputReadLine();

are set to the mentioned values. BeginOutputReadLine method will start async read operations from the C# application stream instead of the standard input devices. So next time you wanna clone a command prompt, start the cmd process and give your own look and feel to it.


25
Jun 09

WMI (Windows Management Instrumentation) in C#

In my previous post, I had written about ManagementEventWatcher with some WMI querries. In this post we will try to figure out what this WMI is.

WMI stands for Windows Management Instrumentation. Its a set of functionalities provided by the OS (Windows) for the applications to control / manage the administrative tasks (check this out for a formal definition).

For example, if you wanna retrieve information about the CDROM drive on a machine, you can write some simple queries in c# and get that job done.

Using WMI in C#

Its fairly simple  in C# to use WMI infrastructure services. C# comes with a class called, ManagementObjectSearcher with which we can query for any information. Lets take the fore mentioned example, the CDROM example. To get information about the CDROM,

  1. Create a WqlObjectQuery object with the query statement, SELECT * FROM Win32_CDROMDrive

    WqlObjectQuery aWMIQuery = new WqlObjectQuery("SELECT * FROM WIN32_CDROMDrive");
  2. Create an object of ManagementObjectSearcher and assign the created query to this object
    ManagementObjectSearcher aManagementObjectSearcher = new ManagementObjectSearcher();
    aManagementObjectSearcher.Query = aWMIQuery;
  3. Run the query by calling the Get method in the ManagementObjectSearcher
    aManagementObjectSearcher.Get();
  4. The Get() method returns a ManagementObjectCollection. Iterate thru’ it to get the reults of the query. Each ManagementObject’s Properties field (ManagementObject.Properties) will contain a PropertiesDataCollection. Iterate thru’ this for additional results on the query
    foreach (ManagementObject aObject in aObjectSearcher.Get())
    {
      Console.WriteLine(aObject.Properties.ToString());
      foreach (PropertyData aProperty in aObject.Properties)
      {
        Console.Write("\t");
        Console.WriteLine(aProperty.Name + "----->" + aProperty.Value);
      }
      Console.WriteLine();
    }
  5. Change the query according to your need. You can query USB Drive information, Hard Disks, Processes and so on. Check out the MSDN for the list of WMI classes

25
Jun 09

ManagementEventWatcher and WqlEventQuery in c#

Yesterday, I was searching for some kind of snippet that will throw some notification when the system starts / stops some processes, thats when I came to know about the ManagementEventWatcher in c#.

ManagementEventWatcher allows us to subscribe for specific events and notifies us when those events occur.

For example, in the fore mentioned example, we need to create a ManagementEventWatcher for the events related to the spawning of processes. This is done using the WqlEventQuery class.

So first we start off writing the WqlEventQuery. This class helps us in constructing WMI event queries. For getting a notification when a process is started or stopped, we shall write a query as follows,

WqlEventQuery aProcessCreationQuery = new WqlEventQuery("SELECT * FROM
Win32_ProcessStartTrace");

or

WqlEventQuery aProcessCreationQuery = new WqlEventQuery("__InstanceCreationEvent",
new TimeSpan(0, 0, 1), "TargetInstance isa \"Win32_Process\"");

The above query shall be used to subscribe for WMI events for Win32 process creation.

Now that we have created a query, we need to use the ManagementEventWatcher to assign this query so that we can start listening for the subscribed events. So we create an object of the ManagementEventWatcher for the query that we formed earlier.

ManagementEventWatcher aWatcher = new ManagementEventWatcher(aProcessCreationQuery);

After creating an object of the ManagementEventWatcher, we need to subscribe for the events that willbe raised by the watcher. So we go for,

aWatcher.EventArrived += new EventArrivedEventHandler(ProcessStarted);

Thats it. All we have to do now is just trigger the watcher. We do this by calling,

aWatcher.Start();

This is an asynchronous call and the reply comes thru’ the event, EventArrived. So whenever the OS spawns a process, the event will be raised.

WqlEventQuery might have solved the fore mentioned problem, but I really don’t know how effective it is. If I get to know about them more, I will post it in here.