jquery, ajax, and .NET Web Services
Recently, I have been working on a few projects that require an ajax friendly life cycle for an ASP.NET web application. Much of the work I did is based on Rick Strahl's post: http://www.west-wind.com/weblog/posts/896411.aspx.
Working on top of what I learned from this article, I decided to leverage the rich capabilities of .NET's Web UI components as part of my ajax implementation using HTML injection. I used jquery to bind a standard button to make a call to my Web Service method.
The service created and populated a standard GridView object. The service would then render that object and return the HTML that was generated. This HTML, once returned by the service call, would be injected into a DIV tag that served as the container for the results table.
My initial implementation is a naive solution that renders full HTML on the server side and passes that back to the client-side. My ASP.NET page already has a script manager so I added a reference to my web service (simple .asmx in this scenario).
<asp:ScriptManager ID="ScriptManager1" runat="server">
<Services>
<asp:ServiceReference Path="~/Services/MyService.asmx" />
</Services>
</asp:ScriptManager>
namespace Client.Project.Services
{
/// <summary>
/// Summary description for ConceptServices
/// </summary>
[WebService(Namespace = "http://tempuri.org/")]
[WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1, Name = "MyBinding")]
[System.ComponentModel.ToolboxItem(false)]
[System.Web.Script.Services.ScriptService]
public class ConceptServices : System.Web.Services.WebService
{
[WebMethod]
[ScriptMethod]
public String Foo()
{
return "<table><tr><td>Hello World!</td></tr></table>";
}
}
}
var i = 3
var s = "bar"
Client.Project.Services.Foo( i, s, successMethod, failureMethod )
Continuous Integration with Cruise Control .NET + NAnt
UPDATE CruiseControl.NET 1.5 RC1 has been release and is available here.
My Cruise Control .NET implementation consists of numerous development projects each with multiple different CCNET projects associated with it (one per environment per branch). In order to make the projects more maintainable, I have created a separate configuration file for each development project.
Defining variables and separating ccnet.config configuration file into smaller files allows for easier maintenance as the number of projects as time went on.
Defining and using variables
Variables can be defined using the following format
<cb:define KEY="VALUE" />
To reference that variable later in the configuration file, simply use $(KEY)
Check out the Cruise Control .NET website for complete explanation of variables using the pre-processor.
Separating the configuration files
<!DOCTYPE cruisecontrol [
<!ENTITY PROJECT_NAME SYSTEM "file:project.xml">
]>
<cruisecontrol xmlns:cb="urn:ccnet.config.builder">
&PROJECT_NAME;
</cruisecontrol>
project.xml would, then, contain the regular xml configuration for a Cruise Control .NET project:
<?xml version="1.0" encoding="utf-8"?>
<project name="My Project" category="A Category">
<workingDirectory>MyProject</workingDirectory>
<artifactDirectory>MyProject</artifactDirectory>
<webURL></webURL>
<triggers>
<intervalTrigger seconds="900" buildCondition="IfModificationExists" />
<scheduleTrigger time="04:00" buildCondition="ForceBuild" />
</triggers>
<labeller type="svnRevisionLabeller">
<pattern>Version {major}.{minor}.{build}.{revision}</pattern>
<major>1</major>
<minor>0</minor>
<url>$(SvnBaseUrl)</url>
</labeller>
<sourcecontrol type="svn">
<trunkUrl>$(SvnBaseUrl)</trunkUrl>
<workingDirectory>$(BaseDirectory)</workingDirectory>
<cb:SvnOptions />
</sourcecontrol>
<tasks>
<nant>
<executable>$(NAntExecutablePath)</executable>
<baseDirectory>$(BaseDirectory)</baseDirectory>
<targetList>
<target>dist.deploy</target>
</targetList>
</nant>
</tasks>
<publishers>
<xmllogger />
<cb:include href="EmailConfig.xml"/>
</publishers>
</project>
On caveat with this idea is that changes to the separate configuration files are not recognized until the cruise control is restarted by either restarting the service or modifying the ccnet.config file.
Building and Deploying ASP.NET Web Applications
The NAnt target below is a full parameterized call to MsBuild.exe to compile any solution. ThoughtWorks.CruiseControl.MsBuild.dll provides an MSBuild logger that allows Cruise Control .NET to report the bulid output.
Parameters
MSBuildPath - The path to the MsBuild executable.
For .NET Framework versions 2.0 and 3.5 on a 32-bit Windows OS, use C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\MsBuild.exe
For .NET Framework version 4.0, use C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MsBuild.exe
SolutionFile - The relative path from the build file to the solution file. Fully qualified paths are also allowed.
SolutionConfiguration - "Release" or "Debug".
BootBootReboot.com
I have been working on a website to aggregate funny technology related content across the internet. So far, I have been able to integrate pictures, YouTube videos, and some RSS content from fmylife and clientcopia
I have created the site using ASP.NET and SQL Server. I made this decision solely because I use Microsoft's platform every day for my professional work.
Picture Uploads and Thumbnails
The pictures page (http://www.bootbootreboot.com/pictures) allows visitors to add their own pictures. Upon uploading a picture, a thumbnail is also generate for that picture. The code below shows how to create a thumbnail of an uploaded image.
{
Ajax using jquery + .NET Web Services
Recently, I have also been introducing some new ajax functionality using jquery and .NET web services. This combination has allowed me to easily introduce a "preview" feature for uploading images and YouTube videos.
Content Management
Youtube Videos
The site is being updated to use the Youtube play list as the content manager for the videos page. Comments and ratings will be retrieved for the detail page and visitors to bootbootreboot.com can add their own comments and ratings.
Adventures in WCF
(Windows Communication Foundation)
My latest project at work has me working with WCF for the first time and it has been an interesting experience. Over the next few weeks, I will be discussing configuration, debugging, and deployment of the WCF service and connecting to it.
Microsoft provides a few tools that can help debug your WCF services.
Error Handling
Typically, I add Global.asax to a web application in ASP.NET and use the Application_Error event to handle any uncaught exceptions.
protected void Application_Error(object sender, EventArgs e)
{
//Insert your application's exception logging here
}
This doesn't work (still looking into why) for WCF services, even when hosted on IIS. A good work around is to wrap each service method with a try...catch block and calling the exception logger in the catch block.
public Object MyWcfWrapperMethod( int i )
{
try
{
//Call the method being exposed by WCF
}
catch( Exception e ){
//Log the exception
}
finally
{
//do your clean up here
}
}
Testing
Unit tests are especially helpful (aren't they always?) in the development of your WCF services as messages from errror and exceptions can (and will) be hidden by subsequent errors. An invalid parameter to a stored procedure call can result in a high level System.ServiceModel.CommunicationObjectFaultedException.