C#

Quote:

Error 1 The name 'Color' does not exist in the current context

using System.Drawing;

Quote:

the original was this error No overload for 'splitter1_SplitterMoving' matches delegate 'System.Windows.Forms.SplitterCancelEventHandler'

// Let's say that you run a search to see if a particular product was on sale
public bool IsProductOnSale(guid productId, out Guid[] productResellerIds)
{
  // This function runs a query against the database to see if this particular product has references in the 'on sale' reference table.
  // If it has references, it returns true also sets the array of resellers that sell that product.
  // The data for which seller has the item on sale is returned in the product query.
}

clapclap wrote:

Instead of an out Boolean to indicate success/failure, throwing exceptions provides more flexibility and scalability

using System.DirectoryServices.AccountManagement;

public static class AuthorizationManager
{
 public static bool UserHasAccess(string userName, out UserPricipal user)
 {
  // function runs a check against Active Directory for membership of a user group
  // if the specified user is a member, pass back the user's info to use elsewhere (logging? other authorization functions?)
 }
}

Foothill wrote:

Let me see if I can give a better example. Let's go with an web environment that supports both internal and external user logon.

public static UserPrincipal GetPrincipal(string userName)
{
   if (UserIsAuthorized(userName))
   {
      return new UserPrincipal();
   }
   else
   {
      return null;
   }
}

Foothill wrote:

The deeper I delve into C# and .Net, the more contradictions I find.

Foothill wrote:

Ah, so even though I can find Microsoft code that does it, doesn't mean that it's encouraged or the best way to go about things

Foothill wrote:

One takeaway that I am getting is that you should always write your code so simple that it lends to documenting itself even when you are writing companion documentation

Sander Rossel wrote:

That's an awesome takeaway!

Foothill wrote:

byte[] rndAry = rand.GetBytes(n);

Foothill wrote:

With TryParse, it almost seems like it was designed to swallow certain exceptions and return false if they occur.

Sander Rossel wrote:

I really hope professional programmers grasp the concept