Is it bad practice to end method names using the old asynchronous pattern with "Async"?
.net, asynchronous, c#
Solution
As new frameworks/patterns/techniques are discovered/created/implemented, new rules or advises appear.
The naming conventions are just a way to create a standard in order to make code more unified between developers; that doesn't mean you can't use the one you like the most or is more useful to you (unless you are ina company that enforces conventions).
From my POV, I wouldn't adopt the new convention in what is now your legacy code.
Also, I always prefer to use a naming convention similar to the framework I'm using so that it will be easier to any other developer working with me.
Check this (kind of old but still pretty good): http://msdn.microsoft.com/en-us/library/xzf533w0(v=vs.71).aspx
Problem
In the recent async/await pattern, the recommendation is to end method names with "Async", such as "GetAsync()". Now let's say I'm using the old asynchronous pattern, i.e. the one with the Begin/End method pair and `IAsyncResult`. And I have a method that wraps a call to that method, such as: ``` public void SendAsync(byte[] data) { this.stream.BeginWrite(...); } ``` Also assume that the `EndWrite` method passed to `BeginWrite` is the same for all data, i.e. it would be a method in the same class. In this case, is it wrong to name this method `SendAsync()` since it might be confused with the new async pattern?