I had the pleasure to help launch Office365Training.com today. It's a site, powered by DotNetNuke, focused on training folks new to Office365, Microsoft's hosted Office solution. The neat thing about the site is that it's been a collaborative effort between the site owner, myself and other developers. While we still need to spit and polish a few things, the functionality is there. Looking forward to turning the corner toward offering more robust functionality.

If you have need of any web design or development services, please leave me a message on our Contact Us page.

Happy Coding!!

I had the opportunity to compare and contrast usage of two HTML slicing programs recently.  I started using Adobe Fireworks to slice a single-layer PSD with the inten to create a W3C compliant HTML/CSS layout.  I sliced the PSD into several key components and found the hotspot utility to be helpful in highlighting areas of my images that were to become links to other site pages.  I exported the slices to HTML and CSS but found that my PSD really had some overlapping slices, that were not conducive to CSS layouts.  My sliced HTML file opened in Dreamweaver as a multitude of table tags - did I mention that I am not a Table layout fan?

That's when I turned my attention to Expression Design and Expression Web 4.  The slicer in Design had a few less features than Fireworks, such as the slice could only be rectangular, whereas Fireworks offered a polygon slice.  Also, the hotspots were defined after slices were exported to Expression Web, instead of being part of the slicing procedure.  The cool thing was that...

We've read a lot of articles recently about client side technologies, their shortcomings, their predicted lifetime and when it's suggested to do certain tasks on the server instead of through a client side solution.  I recently wrote an ASP.NET web service for completerentalls.ca to enable their Flash CS5 application to obtain query results from their database.  Here are a few things I learned through the process:

First, since we were using an Access database, it was important to place the .mdb file in the App_Code folder of the ASP.NET web service solution.  In doing so, this took away the guess work of where the database file would be located once deployed to the server. 

Second, I strongly encourage utilizing a query if you're going to be working with an Access database.  It's never a good idea to directly hit your database table with queries, and this situation was no exception. 

Finally, the web service itself need not be complicated.  Since we were executing one query against the...

The New Year has started with a bang here at WebDBApps.  We've partnered with some awesome clients including VendorsBay, Hotel Management Resources Limited, CompleteRentAlls, DFCharts, Uniform and Tunics and others.  We've also expanded our service offering to include Sharepoint 2010 development.  This version of Sharepoint has some incredible flexibility.  As data-minded folks, we are especially interested in the ability to develop business content sources for Sharepoint 2010 to infuse non-Sharepoint data sources into a given portal. 

Another area of keen focus thus far in 2011 has been in the development of Flash CS5 sites integrated with server-side technologies such as ASP.NET.  We have found that Flash is an awesome user experience development tool.  Coupled with server-side technolgies, we've been able to bring in data from SQL Server data sources into Flash applications for a truly data-rich Flash application.

We hope your 2011 has started on the right foot.  Please contact us to discuss any...

Since Christmas is coming in just a few days, I wanted to share with you not one, but two, musings on current development tasks.  The first part deals with the decision process to continue modifying an existing website vs. rebuilding it from the ground up.  The second part deals with a new technology stack we're using Twilio (Voice/SMS communications in the Cloud) combined with SalesForce.

In my line of work, it seems like web application revisions are easiest if I'm inheriting a well-documented, understandable app wherein I can easily determine which classes produce what functionality.  When one cannot ascertain how the inner workings of a web application is developed, it is almost impossible to make any changes to the site.  I am a firm believer of providing customers with documentation of how I designed their application.  They may choose to wallpaper their bathroom with it :) or they can file it and pass along to the next developer they hire (if it's not me).  Either way, the customer knows how their...

I've been using .Net Reflector casually for a few years and just recently have been engaged on a project that requires decompilation of client's DLLs secondary to absence of original source code.  Reflector along with the Decompiler add in has been my friend in this engagement.  It defines all the properties and methods in a given class and permits copy functionality so that one can take the decompiled code and add it into their current Solution/Project files.  So far, I've found Reflector to be helpful in about 90% of the classes I've decompiled.  The remaining 10% of the classes have to be hand-coded or edited so that errors are resolved.  This is a tedious process as it requires review of the class within the DLL, review of the decompiled code, and further review after the code is copied from Reflector into your new class file.  Some nuances between .Net 3.5 and .Net 4.0 come into play here as well.  However, when the source code is not available and the site needs to be modified/updated, Reflector is your best friend!

...

I'm excited to announce a new service offering that adds to the web development lifecycle.  Since starting WebDBApps 4 years ago, I've focused solely on web and database programming services and have outsourced or partnered with designers who have provided mock ups, graphic design elements like logos, or Flash animation.  I've recently acquired the Adobe Creative Suite and am now ready to provide graphic design services to my clients.  This addition to my repertoire will ensure that current and future clients have a "one stop shop" for their website needs whether it be graphic design, database development or web application programming.  I look forward to serving you in this capacity and invite you to contact me here should you have any current or future needs for Flash projects, graphic design elements etc.  Future clients can look forward to full-fledged mockups as part of their engagement as well!

I also want to wish everyone a very Happy Thanksgiving!  There are so many things for which we should be...

One of our current projects requires clean up of an ASP.NET application that has changed hands from one developer to another, has deviated from original scope and needs some tender love and care.  Brownfield application (re)development is challenging and time consuming.  Some things to consider when working on a Brownfield project are:

Never take any of the application code for granted.  The general rule of thumb is that if you'd didn't write the code, don't trust it!  Thus, an extensive review of the entire codebase is needed to understand what was attempted by previous developers, compared to the scope and goals set forth by the customer. Plan to spend a lot of time on Brownfield projects.  Since you're not starting from scratch, there's a lot of undoing/rewriting involved to produce a clean codebase.  Demonstrate small but measured successes to your customer.  Many customers are not technicians like ourselves.  These folks can't relate to the time we spend on rewriting classes, functions...

Silverlight 4, in my opinion, has matured to the point that it is ready for serious commercial-grade web applications.  The ability to create visually appealing user experiences coupled with all the goodness of .NET 4.0 is merged together now with the business world in Silverlight 4.  Development of my first Silverlight business application has been, at times, frustrating and, at other times, rewarding.  Coming from an ASP.NET background, I tend to look for things like master pages to streamline layout, and I still catch myself adding HTML tags to XAML and getting the red squiggly warnings. 

Here are a few things I've discovered thus far in my development process:

MainPage.xaml , for those of us coming from ASP.NET, equals master page!  That's right, this is the place to create your master layout.  In doing so, you can ensure that all the pages in your Silverlight application have the same look and feel. Use the Silverlight 4 Toolkit Especially Themes.  I chose BureauBlue for my first application as I'm prototyping an ASP.NET site that has the same branding colors as BureauBlue.  To ensure your style is applied to all pages, include it in the UserControl tag on MainPage.xaml.  Thereafter, all controls added to the page will acquire the Theme you've defined....

A question came across StackOverflow yesterday asking whether it was better to perform sorting or filtering within a stored procedure or in the business logic layer of an application.  This highly depends on the application and your needs.  The general approach I use, and is based on advice given by those with a few more gray hairs than I have, indicates that filtering and sorting should be placed within the stored procedure logic. 

The reason for placing this functionality within the stored procedure is due to the fact that SQL Server's database engine can better handle the load of performing these tasks than a web server (which is possibly hosting multiple sites with numerous users).  Obviously, this practice doesn't fit for all cases such as those in which you need to allow the end user to do their own sorts or perform their own filtering.  Providing end users with this functionality...