I did a new WebService, moved around a few classes, added namespaces and then compiled it to get an error ‘Could not create type -’WebSvcProcessor.cs”

After a while of researching the problem turned out to be the I added a namespace to the class which sits in the App_code but the .asmx file doesn’t know about it. So the trick is to make sure you have the same class specified along with the full namespace in your .asmx file. Something like,

< %@ WebService Language="C#" CodeBehind="~/App_Code/WebSvcProcessor.cs" Class="MyNameSpace.Web.WebSvcProcessor" %>

For more check out this MSDN forum thread

1. What is a weak reference?
2. Why do we use “volatile” keyword?
3. What’s the difference - String and string in C#
4. What’s the difference - (MyObject) inputObj; and inputObj as MyObject
5. What is a positional property in a attribute?

Over and over again, I’ve realised what differentiates a successful IT project from a failure. Ofcourse thanks to the quintessential thing called - ‘experience’. It’s easy to believe in something of perceptory nature. Meaning, you believe what is common perception. But only when you experience you’ll realise how fact can differ from perception.

Long story cut short, the phase of ‘development’ of software is not the most important phase for a project’s success. Requirements analysis and Quality Assurance are. A project’s success hinges on collection and analysis of right requirements (what exactly the end user wants to gain) and solid quality assurance process (does the outcome conform to what was intended) ensure a project’s success. Most of us focus on Design and Dev and assume a high quality in here would ensure success (Design and Development by default should and must be of high quality)

A project’s success means, the software that you develop has reached the end user/customer in time, at the right time, enabling him to achieve his objectives for improved productivity, efficiency and cost savings over time.

Give the customer what he wants, not ‘what you think he wants’.

I am really inspired by Rajesh’s thoughts on an IT career and life beyond code. His ideas have got me thinking into what I always wanted to believe. One of the great things Rajesh did since the beginning of his career, what I think is, documenting his ideas, thoughts, lessons, experience which would enable him to come out with his book - life beyond code, years later. As he says it takes years to transform yourself from just good to better and better. If we never care much about long term goals - future and do nothing in present, our future is going to remain the same as the present is. It means we are doing nothing to do any value add to ourselves, and adding tech skills is not going to help us get any further.

In one of my earlier project, I learnt three of the biggest lessons of my career.

1. Problem solving is not something you inherit. You’ve to develop it - Consciously, by being persistent.
2. At work, even if you ‘think’ you don’t believe your current project is going to work or be successful, you’ve to believe in anything that you are currently doing anyway. Chances are you’ll be successful at it in long term. You got nothing to loose, in simply believing in whatever you do.

3. Challenges are opporunities to make you more confident about yourself than ever. Grab it and fulfill it.