Altitude Blog

Visual Studio allows the creation of a new project type call Web Application Project. This is different from the standard ASP.NET web site project. The WAP is based more on the application model of setup. Class and component files can be added anywhere within the project and they will be compiled normally.

For more information on converting your 2005 web site to a WAP site visit http://msdn2.microsoft.com/en-us/library/aa983456.aspx.

I recently upgraded a Linq beta product from the Beta to Final Release.

Lucky there were very few errors except for the default methods of add and delete on the System.Data.Linq.Table. The replacement methods are now InsertOnSubmit or DeleteOnSubmit. It is interesting to think that the conversation's that took place to make such a fundamental change to one of the methods. Obviously it the new methods are more descriptive but the amount of coding hours it has cost beta developers makes you wonder. I now always think twice about naming public methods. 

I received this message while creating my first ASP.NET AJAX web service.

The call to the asyncronise method has changed from (userparameters, onComplete, onTimeOut, onError) to (userparameters, onSuccess, onFail, userContext).

Obviously this is an improvement as you can now track userContext of the Webservice calls.

To fix the above message make sure you are defining your userContext even if it is null. For example:

 <script language="javascript" type="text/javascript">

 var userContext1;       

 WebContentFlow.AJAX.ContentflowAJAXAPI.BuildPage("String parameter",onSuccess,onFailed,userContext1)      

 function onSuccess(result,userContext,sender)        {            alert(result);        }        

 function onFailed(result)        {            alert("Failed request >"  + result.get_message());       

}