Lance's Whiteboard

FW: Batch Updates and Deletes with LINQ to SQL

2008-06-23T23:07:09Z

I'm currently on a project creating a proprietary data-migration tool using C# & Linq. I'm still new to Linq, but quickly discovered the challenges of doing mass-updates and deletes with Linq.

Specifically, by default Linq to Sql generates a sql statement for each row you are updating. There is no built-in way to do large batch-updates or deletes without dropping to custom SQL. After a quick search, I found this great article and sample code by Terry Aney on Batch Updates and Deletes with LINQ to SQL.

It offers solutions to many of the basic problems with some elegant extension methods so you can do things like:

   1:  be_Posts.UpdateBatch( first10, new { Author = "Chris Cavanagh" } );

2:

   3:  and

4:

   5:  var posts = from p in be_Posts select p;

6:

   7:  be_Posts.UpdateBatch( posts, p => new be_Posts { DateModified = p.DateCreated,

   8:                                                   Author = "Chris Cavanagh" } );

Cool stuff!

Minimum & Maximum Dates in code

2008-06-19T16:35:56Z

When updating Sql columns that need a minimum or maximum date, consider using the defaults from the System.Data.SqlType namespace:

   1:  DateTime minDate = SqlDateTime.MinValue.Value

2:

   3:  // and

4:

   5:  DateTime maxDate = SqlDateTime.MaxValue.Value

This can be a lot safer than putting hard-coded "magic date" constants in your code.

What we dont know "will" hurt us...

2008-06-05T17:17:53Z

I like this article by Nathan Henkel, its essentially about assessing risk and scope of projects and strikes me as a simple truth about the uncertainties you encounter in every project:

Information about any project can be divided into four categories:

1. Things we know (and know we know)
2. Things we know we don't know
3. Things we think we know, but don't (i.e. things we're wrong about)
4. Things we don't know we don't know

Obviously, if you were to try to actually figure out where everything falls, you would put everything into 1 or 2. Everything that should be in 3, you would put in 1 (you're not going to have known mistakes in your information), and everything that should be in 4 would simply be missing.

However, without dealing with specific items, I do think that it's possible to guess at how much "stuff" goes in each category. You can take into account your history ("I tend to often be mistaken about X"), or a general feeling of ignorance ("I've never used framework Y before") to guess how much goes in each category.

http://simplyagile.blogspot.com/2007/10/classifying-information-or-what-we-know.html

Sometimes, I think we get so wrapped up with what we “know” about a project that we fail to quantify what we don’t know, or the degree of certainty to which we actually know what we think we know. As with solving any problem, the first step is to find a way to quantify and measure uncertainty and risk in order to minimize it.

If you track this measurement over time, it should also help your estimation and planning on future projects.

Good stuff!

Argotic Syndication Framework 2008 released

2008-03-27T16:59:12Z

I got an email yesterday that a major update to the Argotic Syndication Framework was released. I have used the older versions of this framework several times for projects that need basic RSS & Atom parsing/generating so I'm looking forward to digging-in to the new release.

If you are not familiar with it, here is a quick blurb:

The Argotic Syndication Framework is a Microsoft .NET class library framework that enables developers to easily consume and/or generate syndicated content from within their own applications. The framework makes the reading and writing syndicated content in common formats such as RSS, Atom, OPML, APML, BlogML, and RSD very easy while still remaining extensible enough to support common/custom extensions to the syndication publishing formats. The framework includes out-of-the-box implementations of 19 of the most commonly used syndication extensions, network clients for sending and receiving peer-to-peer notification protocol messages; as well as HTTP handlers and controls that provide rich syndication functionality to ASP.NET developers.

To learn more about the capabilities of this powerful and extensible .NET web content syndication framework and download the latest release, visit the project web site at http://www.codeplex.com/argotic.

Also, here are some of the new features in this release:

a) Targeting of both the .NET 2.0 and .NET 3.5 platforms

b) Implementation of the APML 0.6 specification
c) Implementation of the BlogML 2.0 specification
d) Native support of the Microsoft FeedSync 1.0 syndication extension
e) Simplified programming API and better online/offline examples

Brian has done an amazing job on this project from the start. I had intended (and still hope) to jump in and contribute some of my own work, so its great to see how far it has evolved from its first releases.

If you work with RSS, ATOM, or any other syndication format/protocol, you should definitely take a look at this framework for your next project.

I love ClearContext!!

2007-12-18T19:40:04Z

After several months of using the Free version of the ClearContext addon for Microsoft Outlook, I just cant imagine what I would do without it. It has reduced my email time, kept me more organized, and uncluttered my Inbox better & faster than any ad-hoc system I have devised in the past.

As a developer, I hate it when I have to "code in Outlook". If it were up to me, I would ban all email during a project and deal with all communication via instant messenging, Scrum meetings, and whiteboards, but the truth is that email is a neccessary evil especially as a Tech Lead who needs to interface with the Project Manager, Customer, and IT personnel.

Enter ClearContext Information Management System...

First, I set it up to flag emails from my bosses in Red, so I dont miss them. Plus, for good measure, I have an Outlook rule that sets a FollowUp flag to make sure I dont overlook them. Also, ClearContext automagically ranks emails based upon my prior history with this person, so I know what to do when I get some nice blue and green colored mail too.

If I receive an email relating to my current project, I simply hit ALT-P to popup the CC dialog and flag it with the topic "projects/MyProject" then either leave it in the inbox for further review, or hit ALT-M to file the message for future reference. Accordingly, if I receive some corporate or administrative relating email, then I assign it's topic appropriately and file the message to send it to its respective holding area.

The act of assigning a Topic (ALT-P), automatically creates subfolders within my Inbox (e.g. inbox/projects/MyProject) matching the topic name (Note the trick of adding a "/" to the topic name to create a nested subfolder at the same time). The act of filing a message (ALT-M), moves it to the subfolder identified by the topic name. This is great because the messages are nolonger visible in the Inbox listing, but are still within the Inbox via the subfolder.

At that point, my AutoArchive settings will take care of moving it off on a monthly basis in case I need it later.

At some point, I want to look at the full product, which has features for deferring emails, converting them to tasks & appointments, assigning them to other people, etc. See their Features Overview section for more on these areas.

If these features are nearly as useful as the ones I use now, then I could *gasp* become even more productive! woot!

Degrees of optimism in projects

2007-12-01T01:22:13Z

Whenever I lead a project, I always try to plan in such a way that sets me and my team up for success. I do this in many ways, starting with a good methodology, doing thorough analysis, and providing a level of risk/certainty along with any estimates I provide.

Part of this strategy involves ensuring that client expectations match developer and project expectations. I tend to use the tried and true approach; "Plan for the worst, hope for the best".

Some people see me as a pessimist, but I beg to differ - I consider myself a cynical, yet optimistic, realist. By that, I mean that although I do plan everything based upon the worst case scenario, in my heart I truly believe we are going to achieve the best case scenario every time. It often surprises me when people take my approach to be negative while at the same time, I often see their approach naive & overly optimistic.

The truth is that there seems to be a gradient scale of attitudes and philosophies employed from project to project depending upon the people leading and participating in the project.

Over the years, I started a private game in my head of creating nicknames for the different patterns of behavior. Here are a few names of I have toyed with in the past:

"Expect the worst, then add 20%" - The Pessimist

"Expect the worst, hope for the best" - Reformed Pessimist

"Expect the best" - Mr. Optimist

"Expect the best, but prepare for the worst" - Fallen Optimist

"Plan for the worst, hope for the best, but expect something in between" - Uncle Realist

"Just do it!" - El Toro

"It is what it is." - Aunt Apathy

"I don't want to hear about risks, just tell me when it's done." - The Ostrich

"Oh, you arent done yet?" - Captain Oblivious

"How much longer?" - The Waiter

Which one are you? Is there one philosophy or attitude you believe works better than others?

Manual CRUD operations with the Telerik RadGrid control

2007-10-17T15:33:00Z

I have been working on a project lately that was already using the Telerik ASP.NET Rad Controls suite. One of the new features was a fully editable web-grid, so I chose to use the existing ajax-enabled RadGrid control to speed my development. I chose to use a 3rd party control, mostly due to time constraints since the project required a grid with inline-editing, full CRUD operations, plus custom column templates, all with heavy Ajax support to avoid postbacks and excessive page size.

I soon discovered, the Telerik controls are nice tool for simple uses where you can use asp.net DataSource controls and automatic databinding, but not so much if you need to get "fancy" with your implementation. In my case I needed to do 2 things that cross over into the grey area where these controls excel.

First, I'm using an early 2.0 version of NetTiers for the DAL (with Service Layer implementation) with custom mods to the entities as the datasource, and second, I'm doing some aggregate custom ItemTemplates that require custom data-binding.

This lead to extreme complexity in the implementation because, A) this version of NetTiers' had problems with properly generating CRUD operations for its EntityDataSource controls (NetTiers entities mapped onto a custom ObjectDataSource style control) which prevented me from using the declarative model, and B) the RadGrid control simply sucks if you cannot use automatic databinding and if you require custom databinding logic.

It would be great if I could upgrade NetTiers and/or Teleriki RadControls to the latest versions, but it wasnt possible in this situation, nor is it likely that this would have solved my problems.

Anyhow, all this discussion is basically just to share you this one link to a user-contributed example I found incredibly useful after 3 days of searching their forums, demos, and 3rd party blogs. This example shows how to manually implement Insert/Update/Delete functionality within the RadGrid control by handling the events OnNeedDataSource, OnItemCommand, OnInsertCommand, OnUpdateCommand, and OnDeleteCommand:

http://www.telerik.com/community/code-library/subm...

The reason this link is important is because the Telerik website, with all of its dozens of examples, consistently shows very basic scenarios, even in samples labeled "advanced". Also, not all of the API features are fully or well documented to help you figure this out on your own.

Hopefully this simple link (which should be promoted to Telerik's demos/samples page) will help someone else as much as it did me.

VPC 2007 Dual Monitor support

2007-10-11T17:11:00Z

I have been trying to find a way to allow you to run Virtual PC 2007 with multiple monitors. Natively VPC 2007 doesnt support more than 1 monitor, however you can "trick" it by using various techniques that expand the desktop area into a larger virtual desktop.

I tried using the awesome MaxiVista tool which can extend your screen across separate PC's (think "push" remote desktop), but the new multi-monitor compatibility feature of VPC 2007 (which inexplicably does not add multi-monitor support) made this difficult since it ensures that your desktop recaptures your mouse when you move it outside of the VPC window thus preventing the extended screen from being accessible.

So, instead I tried the Remote Desktop approach mentioned in Steven Harman's blog post.

Here is a quick rundown on how it works:

Connect 2 monitors to your PC (more than 2 typically don't work with this approach). Make sure to extend your desktop onto the 2nd screen via Display Properties -> Settings. Then launch Remote Desktop (mstsc.exe) with the "/span" flag:

mstsc /span

Then just use Remote Desktop as usual by specifying your VPC's computer name in the connection dialog.

When I first tried this, it still didnt work exactly right. It kept giving me annoying scrollbars instead of going full screen, so I added this extra flag to force it into fullscreen:

mstsc /span /f

Also, since I didnt want VPC to have the extra overhead of maintaining 2 sessions (the console and my new RDP session), I threw in one more flag to make it simply take-over the initial console window:

mstsc /span /f /console

NOTE: The /span flag is only present on the very latest version of Remote Desktop Connection. Therefore, you must either be running Vista on both PC's, or install the update specified here:

http://support.microsoft.com/kb/925876

There are limitations on how your monitors must be configured in order for this flag to work.

Also, keep in mind that this technique only enlarges your desktop area sufficiently large enouch to span both monitors, but it DOES NOT behave exactly like the native dual-monitor support you may be accustomed to. For example, when you maximize a window, it maximizes across BOTH monitors instead of maximizing within the confines of a single monitor. For now, I'm just dealing with that by avoiding maximizing and just manually resizing windows to fit 1 screen.

Advanced Users:

One way to avoid having to arrange windows each time is to use a cryptic, yet incredible tool called Hawkeye ShellInit. ShellInit is a small application that helps you manipulate your desktop & application windows via script. Here is a small script that will move Visual Studio over the right-hand screen (assuming 1280x1024 resolution) and enlarge it to the correct size.

Position Window, *Microsoft Visual Studio, wndclass_desked_gsk, 1280, 0, 1288, 1002

If you decide to use this tool, make sure and read the readme.txt file for some good sample scripts and ideas.

Link Love: 09/21/2007

2007-09-21T20:47:54Z

I havent been blogging much over the past several months. The main reason is time, or the lack thereof. Since I dont have time to write a "proper" blog post, I'm just going to start sharing some link love...

Here are a few interesting links I have spent time perusing today:

Thirteen Simple Rules for Speeding Up Your Web Site - a great checklist to review before releasing any public website into the wild.
dhtmlxGrid - an open source (but commercial) editable DHTML grid with AJAX support.
Edit Individual GridView Cells - an article on how to make clickable ASP.NET gridview cells to allow for a rich editing experience.

Note to self: Blog about using Service Broker

2007-06-14T18:31:54Z

Just a note to myself to do a braindump on all this Service Broker shiznit I have been playing with lately.

Potential discussion topics:

MessageTypes, Contracts, Queues, and Services.
Internal Activation, Routing, & External Activation
Using the Sql Server ServiceBroker sample library.
Implementation using SqlClr vs. TSQL
Developing via messages instead of procedures...
Compare & contrast Service Broker vs. Workflow Foundation vs. BizTalk
The nifty Sql Service Broker Admin tool (3rd-party)
Practical examples:

Async "fire-and-forget" stored procedure invocation
Query Notification for cache invalidation
PubSub

The influence of style upon methodology...

2007-05-24T00:53:00Z

No matter how faithfully you try to follow your chosen project methodology (Scrum, Extreme Programming, Waterfall, CMMI, etc.) ultimately the strengths, weaknesses, successes, and failures you experience are determined by the habits, attitude, and style of the project manager and team members on the project.

How is communication conducted? Meetings, hallway, bullpen, email, IM?

How do you react to change? How well do you manage scope?

How much trust/distrust is there amongst team members?

How rigorously or adaptively do you apply your process to each project?

Do you micromanage or do you empower?

This is the crux of why so many people disagree with most definitions of exactly what Agile is. This is why some people fail with one methodology while others succeed, and some unique individuals actually find great success with seemingly outdated methodologies like Waterfall. Much like with any good pasta, its not the ingredients in the sauce, its the sauce-maker(s).

I guarantee you that even the most rigorous Agile shop will see great variance (good and bad) between projects merely due to the different personalities of the project managers who manage each project. This is the human factor of software development that can never completely be erased. Your best hope is to try to control, monitor, and compensate.

There are plenty of excellent books to help you define your rules-of-engagement, develop good habits, and provide checks-and-balances throughout your project. However, ultimately experience is our best teacher for what habits, styles, and attitudes result in the most successful projects. Of course, to complicate things further, these same success factors may change from project to project.

In my opinion, good project management is like any other art form - everyone has different tastes, everyone does it at least a little different, and deep down you just hope that you have the right combination of experience, talent, and style to be able to execute on your vision. I'm just curious about how many other styles of project management are out there, and which ones people find the most successful.

What daily personal work habits do you find the most crucial for project team members?

What project management styles have you seen that were the most successful? Least successful?

Does your organization try to limit the impact of personal style, or embrace it?

My fair and biased opinion on the recent upgrade...

2007-05-18T19:07:09Z

DISCLAIMER: The following post represents my personal opinions and thoughts, not that of my employer.

As a Telligent employee and weblogs.asp.net blogger, I hate the fact that the recent upgrade caused problems for the weblogs.asp.net community and that it has affected the perception of Telligent as its steward. I wasnt one of the developers who worked on the project, but I couldnt help but feel a twinge of pain each time I read a post (often rightfully) slamming the team and company who delivered this upgrade.

Long before I joined Telligent, I was one of the more vocal bloggers about the mishandling of the weblogs.asp.net site. The great irony is that most of my arguments at that time were about how rarely the site was updated to newer versions of .TEXT and CS. Since that time, its hard to argue that it hasnt gotten much better. Eventually I became satisfied and frequently impressed with the website changes as we finally were able to take advantage of Community Server's outstanding features.

This latest release really excited me because it was very timely (coming on the heals of CS 2007's release) and had the potential to allow me to finally have the level of control I wanted over my blog's presentation.

Even with the recent problems, especially the fact that I need to resubmit my javascript, I'm still excited about this release. In fact, I truly was never all that disturbed by the problems as they were occurring

Was I surprised? Yes.

Was it annoying? Sure.

Would I have preferred an email beforehand? Absolutely.

I thought about my lack of concern, and had to ask myself why I wasnt more put-off by the problems of this update.

Was it just because I am now an employee?

Was my blog nolonger as important to me as before?

The answer, is quite simple. After coming to work for Telligent, I have met (most of) the people who work on Community Server and the Weblogs.ASP.net websites. Every one of them are top developers who are professional and thoughtful of every change they make and how it will affect the community. They have the best intentions of delivering new innovations to the community as cleanly and effectively as possible.

In short, I trust that the people in this company will always try their best to do the right thing for our customers, users, and community. If you knew the people here, and saw their passion, attention to detail, and work ethic, I have no doubt you would feel the same.

Do we always succeed 100%? No.

Do we WANT to succeed 100%? Absolutely.

Will we continue to try and improve our processes to avoid such problems in the future? Undoubtedly.

As the philosophy goes; "if you arent making any mistakes, then you arent trying hard enough". I dont know how/why things went awry this time, nor am I in a position to investigate it since I'm just a developer here. I just trust the weblogs.asp.net team and my company to do the right thing. They always have in the past, so I see no reason to doubt it in this situation.

I just wanted to share this view with my fellow bloggers. You can obviously choose to say "Lance has sold-out and is trying to back-up his employer" but I the truth is that I really believe what I said above. Nobody asked me to write this. In fact, I'm sure there might be some here who would prefer that I didnt even post this...

In the long term, I belive this will be a better site and a better community after this upgrade is stabilized and people realize how major this upgrade was, and how much new flexibility and control you now have to personlize your blog and make it the true home you always wanted.

As my mom always said; "this too shall pass.."

A web site is not an RSS feed...nor the reverse.

2007-05-14T19:22:14Z

There was a time not so long ago when we built "home pages". Glorviously extravagant, naievely simple web sites that said who we were, and what we were about. On those home pages, we put news & announcements, and often, links to static pages of content. If we wanted to interact with visitors, we included guest books, maybe a simple message board, or just displayed our email address prominantly so others could drop us a note. All of this was created by hand with the expectation that changes would be few and far between.

Eventually this became such a common approach for building a web site, that we tried to standardize these things. At the same time, we discovered that a frequently updated web site received more visitors than one that was static or rarely updated. As a result, content-management features were added to speed updates, forums were improved to include user avatars, threading, and email subscriptions. Finally, the news & announcements became data-driven, annotated with metadata, and archived for historical review.

The current incarnation of this evoulution is what we call the Weblog. A weblog is still nothing more than an "about" page, news, articles, and forums, it just has evolved a few new facets and appendages to impower users to interact in new (and hopefully better) ways. Today, we can hardly imagine a web site without at least 1 RSS Feed. In fact, most web sites today (nearly) completely revolve around their News & Announcements and the related RSS feed. Yet, we must remind ourselves that the RSS feed is useless by itself. It is an evolution FROM a web site, not an evolution OF a web site. It is nothing more than an alternative delivery vehicle for information, not neccessarily a replacement for the weblog (read web site).

However, too many blogs today look like nothing more than an RSS Feed transformed via XSLT. In fact, I bet quite a few are exactly that. As a result, they look less like a home page, and more like a laundry-list. Yeah, most sites have a banner and some rudimentary navigation, but I'm talking about what happens below the first 6 inches of the site.

Which leads me back to the title of this article...

A Web Site is supposed to be the virtual equivilent of a store-front window or your home's front lawn. A weblog is supposed to be like the entryway, and an RSS feed is supposed to add value to an already valueable web site, much like putting a sign outside the store to advertise your current specials. An RSS Feed is not supposed to be your entire web site, nor is your web site supposed to be turned directly into an RSS feed. Sure there are some nifty Web 2.0 uses for RSS, but dont get so busy focusing on your RSS Feed that you forget about why its there in the first place - to drive visitors toward your web site.

RSS is a just tool, and like any other tool it can be abused, and over used.

Reporting Services administration changes in Katmai (v.Next)

2007-04-24T17:02:23Z

Brian Welcker posts some information on changes they are consindering to how you will administer Sql Server Reporting Services in the next version, codenamed Katmai.

Right now, administering Report Models exposed to Report Builder requires you to launch Sql Server Management Studio tool, while other features require you to launch the Report Manager website. Also, there are some features that you rarely use, yet are exposed from the Report Manager portal, such as Job Management and System Wide Role & Security configuration.

It appears that the end result of the proposed tool changes will be to correct these inconsistencies by consolidating server and system-wide configuration and administration tasks into Sql Server Management Studio, and moving some of the more user-facing admin features to the Report Manager.

Not a bad idea overall, now I just hope they fix support for FormsAuth throughout the entire solution (ReportBuilder, nudge nudge).

Reserve judgement lest thou be judged too...

2007-04-24T00:34:29Z

After submiting my last post (rant), I re-read it and had a thought occur. Maybe I too should show humility and take the optimistic view that the developers of these projects really did have good reasons for their reinventions and innovations.

Perhaps somewhere in this world is a developer looking at old code that I wrote, saying "WTF!?!?". I'm sure I too had a reason...