Crank! I will watch that soon!

This article supposedly will help good developers develop good design for their websites. I have always had this problem. I always felt I lacked this "good designing capability".

http://peterkellner.net/2006/08/28/msprofcsshowto/

I did not go through it yet. But once I am home I would study that and make some observations.

Speed launch of Studio products

Its been around 6 months since I used Visual Studio and worked on any .NET application. So I am having problem of amensia - memory loss!! :D I have been using the /nosplash option with Visual Studio since long, since I started real coding on .NET! But sitting idle in my office and browsing the internet, it took me a long time to recall "what was the option that I used to quickly launch Visual Studio?". It is the "/nosplash option, which you can give in the TARGET of your Visual Studio project. For example, you can launch the Visual Studio from Start->Run and type "devenv". You can see the usual Splash screen. Its very elegantly designed, but still I dont want to see it everytime I start Visual Studio(I used to launch Visual Studio around 20-30 times a day!) So you can use this handy tip. Type
"devenv /nosplash" and press enter. And Splash!!! your Visual Studio is straight up! and working fine!

This post is just to make sure that incase I forget that myself, I know where to look out !

Signing a weak assembly in .NET 2.0

Just came across this post on MSDN Blogs. It says "Signing an unsigned assembly in .NET 2.0". Usually I dont find such things interesting, but gone are those student days and being a professional, there are some "corporate" things to be learnt. So recently I borrowed a book from library "Introducing .NET Framework" by O'Rielly. It was an old book, dated .NET 1.0 beta 2 release!! but still I felt I learnt a lot of new details regarding .NET Framework, especially about the CLR and stuff like that. So I found this one interesting. I have made some notes which I would post it in the future.
For now, take a look at this.
http://blogs.msdn.com/neerajag/archive/2006/10/12/signing-a-existing-net-assembly.aspx

Height of Sincerity!

well the title would not make any sense for another two to three days. Thanks to my colleagues that I am nominated for the Best Learner and Best Guide awards for the FLP batch. Friday, the 13th! is a big day for us, FLPites. Its our Graduation day and the day when we get a hint of our "what next?"

Old habits die hard and my taste for .NET still remains. So I often keep browsing about Microsoft and .NET. In that process I read some excellent blogs. One such blog is here. Its an index of Various "How-to-deploy" on Visual Studio. It is a must-look!
http://blogs.msdn.com/astebner/articles/574618.aspx

I would not change the heading of my blog. But I would like to post few comments on the currently technology I am working on! Surprisingly, inspite of not liking the platform, I am doing pretty well on Mainframes! As a developer who fine tuned his programming skills among OBJECTS, working on COBOL, developing applications with CICS appears awful. But still, you have to do it.

One thing that we should appreciate about coding Cobol on Mainframes is, with the tools I used so far, I now feel that I can survive coding without the help of Visual Studio or Eclipse or any IDE for that matter. If you can manage a project on TSO, trust me, you can do wonders with Visual Studio and other IDEs.

There is a lot to learn about Mainframes - CICS, COBOL and JCL! But still somehow I feel I dont belong here. I plan to move to .NET professionally too....

More insights later. I also plan to post tips/guide for mainframe beginners! Now - I aint a beginner anymore and I do have valuable suggestions and tips on Mainframes too!