WebService compilation issue

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

Revisiting basics

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?

Project’s success

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’.