Using aliases for better code readability

Why not join our community?, there are 4 users online

home
c#
view story

DotNetKick.com is an open-source project. Please report any bugs and let us know your great suggestions. Currently running svn revision 620 (rss)

Kick Spy!, Kick Zeitgeist and Kick Widgets

19
kicks

kick it

Using aliases for better code readability

published 7 months, 21 days ago, submitted by

jeremyjarrell 7 months, 22 days ago

jeremyjarrell.com — Here's a quick way to reduce overall code bloat while making your code even more readable.

2 comments | category:

C# | Views: 5 | Get KickIt image code

tags: Tips, C# | tag it

Everyones tags:

Your tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

jeremyjarrell - Mintman -

gavinjoyce - mihai.guta - mklinker - alunharford -

jdelator - Reman -

crpietschmann -

gt1329a - jacook11 -

kayos -

zigamorph -

drmohundro -

GTech33 - s.farmar - blisteringlunatic -

mdopp - john2021

Comments:

Yeah, I've never been a big fan of aliases myself. When reading the code you have classnames in your code that don't actually exist. Maybe it's just me but I find that a bit confusing.

posted by aquinas 7 months, 21 days ago

@aquinas: I agree, which is why I prefer to alias the namespace rather than the class. In the linked example I'd make the declarations:

using FancyControls = FancyControlVendor.Organizer.BusinessObjects;
using Outlook = Microsoft.Outlook.Interop;

and the code:

FancyControls.Email organizerEmail = _mailBox.GetSelectedEmail();
Outlook.Email outlookEmail = new OutlookEmail();

The multipart class name is my clue to look for an alias up top.

posted by BigTuna 7 months, 21 days ago