C#

Kevin Marois wrote:

Anything wrong with the concept of returning responses?

Kevin Marois wrote:

a WPF app

Kevin Marois wrote:

If you put a TRY/CATCH in the DAL, log the error, then what..??? Throw again and
catch it again in a UI side TRY/CATCH?

Kevin Marois wrote:

What about situations where it's NOT an exception, but the UI needs to know
something, like a duplicate record problem

Kevin Marois wrote:

So far this works well, but I'd like to get your opinion. Do you have a better
way?

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]

void SomeFunction();

Response<SomeEntity> SomeFunction();

Kevin Marois wrote:

1) Try/Catch blocks All Over.

Kevin Marois wrote:

You always want try/catch's wrapping your DAL data methods

Kevin Marois wrote:

I do not agree that a duplicate record is an exception. First, it really is an
issue of the business rules.

Kevin Marois wrote:

Second, the user types in "Blah" and saves, and then "Blah" again and saves, and
the app should log & throw?? Really? The app should notify the user, but no
other action is necessary.

[Serializable]
public class ComputerSaysNoException : Exception
{
  public ComputerSaysNoException() { }
  public ComputerSaysNoException( string message ) : base( message ) { }
  public ComputerSaysNoException( string message, Exception inner ) : base( message, inner ) { }
  protected ComputerSaysNoException(
    System.Runtime.Serialization.SerializationInfo info,
    System.Runtime.Serialization.StreamingContext context ) : base( info, context ) { }
}

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]

Eddy Vluggen wrote:

You do not have to; it's not the BR-rules that define how the data is saved most efficiently. There technically cannot be "duplicate" records in a relational database

Kevin Marois wrote:

You're confusing a Business Rule Violation with an Exception.

Kevin Marois wrote:

What is an exception? It's simply a fancy word for Error. A BR violation isn't
an error. It's a condition that can't be allowed to continue on to the DAL.

Kevin Marois wrote:

And to say "There technically cannot be "duplicate" records in a relational
database" isn't always true. Again, this is something determined by the app
requirements.

Kevin Marois wrote:

My point in all this is that I think I've come up with a standardized way of
returning to the call ANYTHING that happens

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]

public void GetTypeAndSetToOne(ref object Value)
{
    Value = new Frood("Towel");
}
...
int MyInt = 0;
GetTypeAndSetToOne(ref MyInt);
// What does MyInt contain now?

string MyString = "";
int MyInt = 0;

object temp = MyString;
GetTypeAndSetToOne(ref temp);
MyString = (string)temp;

temp = MyInt;
GetTypeAndSetToOne(ref temp);
MyInt = (int)temp;

class A {}
class B : A {}
class C : A {}
...
B b = new B();
Change(ref b);
// At this point, b contains an instance of C!
...
void Change(ref A a)
   {
   a = new C();
   }

public void Test()
    {
    string MyString = "";
    int MyInt = 0;
    object oS = MyString;
    GetTypeAndSetToOne(ref oS);
    MyString = (string) oS;
    object oI = MyInt;
    GetTypeAndSetToOne(ref oI);
    MyInt = (int) oI;
    }

using System;

namespace ConsoleApplication5
{
    class Program
    {
        static void GetTypeAndSetToOne<T>(ref T Value)
        {
            if (Value is int)
            {
                Value = (T)(object)1;
                Console.WriteLine("int");
            }
            else if (Value is string)
            {
                Value = (T)(object)"1";
                Console.WriteLine("string");
            }
        }

        static void Main(string[] args)
        {
            string myString = "";
            int myInt = 0;
            GetTypeAndSetToOne(ref myString);
            GetTypeAndSetToOne(ref myInt);
            Console.WriteLine("MyString, type = {0}, value = {1}", myString.GetType(), myString);
            Console.WriteLine("MyInt, type = {0}, value = {1}", myInt.GetType(), myInt);
            Console.ReadLine();
        }
    }
}

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]

using (SqlConnection cnn = new SqlConnection(strConnect))
    {
    cnn.Open();
    using (SqlCommand cmd = new SqlCommand("SELECT * FROM LISTSTAFF()", cnn))
        {
        using (SqlDataAdapter da = new SqlDataAdapter(cmd))
            {
            DataTable dt = new DataTable();
            da.Fill(dt);
            gridview.DataSource = dt;
            }
        }
    }

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE PROCEDURE LISTSTAFF 
AS
BEGIN
	SET NOCOUNT ON;
	SELECT * FROM tblStaff
END
GO

Member 2458467 wrote:

procedure does not return a value