Basic Integrated App using UIPAB and Forms Authentication

Just yesterday afternoon, when I thought of having a difficult weekend to crack the problem with UIPAB, lightning struck. I got a reply to my question posted to news.microsoft.public.dotnet.distributed_apps redirecting me to GotDotNET workspace where a fix to the Back button problem with UIPAB was posted. God, that was timing. Had the reply come at sometime evening, I would have been spending my entire day today searching for alternatives for UIPAB (specifically Maverick) and working on it. ( I think i'll take some time off and try Maverick some time before UIPAB v 2.0 release).

As such, the Fix for Back button problem ( http://groups.msn.com/BDotNet/general.msnw?action=get_message&mview=0&ID_Message=12337&LastModified=4675459353602606026 for a description on the problem) did infact work out very well. I guess, the fix has been taken care in UIPAB v2.0.

With this fix, I managed to complete a Demo application integrating UIPAB and Forms Authentication yesterday evening.

The demo application will be used in my presentation on Monday to share my knowledge on UIPAB and Forms Authentication to my collegues.

Currently trying to use Data Access Applicaton Block in my demo application.

Also listening to DonBox's .NET Rocks Internet Audio Show (talking about Indigo,SOAP.....)

My Kata - Forms Authentication

Today's task of the day was to enjoy. So, the Kata was to experiment with Forms Authentication.

It has taken nearly a week to understand the Security Issues related with the ASP.NET application. Finally got a hang on Roles, Users,IPrinciple,Encryption and all other simple matters related to security.

The best part of today's Kata was that it got over is just 60 minutes (The last 60 minutes of the day).

Two more kata's are pending. One is to integrate the previous kata on Storing Encrypted passwords in Database with today's kata. The second is to integrate the resulting kata with User Interface Process Application Block.

Off to meet a friend and discuss C# Types.

The No-Linker concept in .NET

Yesterday night while returning to my home, dropped in to my friends startup company. It so happened that I had to talk about “Gettting started with C#”.

I thought it would be great to write the HelloWorld program and start disecting it. It so happened that, we went on to discuss on topics like:

• Whats the difference b/w compiler and interpreter?
  
• What happens from the time of double click of an windows application till some output is got? We had gone as far as to see what is an OS loader, how processor executes instructions, where are instructions stored and all those stuff which should have been discussed at the college days.
  
• Defination of Object.
  
• Seing the anology of an object and me.
  
• Seing the anology of a class and human class.
  
• Class methods and Instance methods.
  
• Whats the difference b/w an *.exe and *.dll file
  
• About PE file format.
  

The most important point of the talk was when I understood that .NET does not have the concept of a Linker .

There is no linker because there is no such thing like statements in C/C++.

I could not resist to go deep further into the Metadata Tables and related basic stuff. Realized as to why Jeff Richter has given priority to Metadata and Assemblies in his excellent book “Advanced .NET programming”.

I am out to see whats the scenario in Java Technology case. (Recently lots of comparison is happening b/w Java Technologies and .NET) The best link of all is http://www.dwheeler.com/java-imp.html