In my previous post
on “Using CVS with VS.NET”, I've discussed the need to switch to CVS and also the problems faced in doing so.
After long time (nearly 2 months) my team has finally become very comfortable with using CVS and VS.NET. Looking back 2 months from today, I get reminded of those days when a whole day would be spent by me wondering who did what and what went wrong. With good push from my team-mate, Jimson, CVS was finally chosen as our Source Control. We did find a good plug-in called “Push-Ok
” for VS.NET 2003. An excellent plug-in I should say. But, it came for a price.
We chose to stick on to Tortoise CVS
and take the hard way around. We found that apart from files being edited by us, the VS.NET IDE also changed some files (like .csproj). Then with the help of Jimson, found out the right files to got into the CVS repository. Thus, after a half day session for the team on how to use “CVS with VS.NET” things got settled and now everyone seems to be comfortable with the “Copy-Modify-Merge” way of doing things.
A great feeling and a great relief....
Good going team.....
I had a requirement to develop a quick partially functional demo application. I chose to do the application using ASP.NET. Oh! It was a nightmare to create a web page with nearly 30 controls. The culprit was the requirement to place the controls aligned within tables. I thought it would be easy to do that once I had the controls on the page. It turned out to be a mess later when tables came into existence.
First, the controls could not be compacted within each cell of the table.
Second, confused whether to use the HTML view of Design view to create the pages.
Finally, I gave up and took the help of an expert (who had expertise in such table-driven web pages design using ASP). Even she had some surprises in store working with the Design view. It eventually turned out to be a remake of the entire web page loosing the existing controls.
In parallel, one of my team members discovered some way to create the aspx pages using the latest Dreamweaver MX. It looked far decent than the page we had done using VS.NET
Now that I need to work on some more ASP.NET applications, I am at the cross roads having many choices but just dont know which direction to take.
I don't get the process followed in creating ASPX pages. Is it that the web pages should be created by one person with all the necessary controls and then the functionality be added by another person or both the aspx and code-behind be done by a single person.
Just waiting to see a lighthouse........
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.....)
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.
While having discussion with my friend yesterday, I realized that “There's plenty of room in C# Types”.
Some of the questions i faced were:
Why did they go for Value Types?
What is actually a Stack and Heap?
Many more fundamental doubts arised. I am now in quest for answering those fundamental questions.
The First, among the plethora of doubts would be to clear “How much memory is allocated in Stack and in Heap for a simple program like the one below?”
internal class Simple
public static void Main()
x = 7;
Also wondering at
Is x a Value Type? (B'cause it is within a Reference Type)
Ok. Out to read some basic stuff from Jeff Richter.