Return base. ExecuteFunction("MyCustomerAdd", nameParameter, surNameParameter); ALTER procedure dbo. Proc_MyCustomerAdd Can you try to use: return base.
ExecuteFunction("proc_MyCustomerAdd", nameParameter, surNameParameter) Does that make any difference? Marc.
Return base. ExecuteFunction("MyCustomerAdd", nameParameter, surNameParameter); ALTER procedure dbo. Proc_MyCustomerAdd Can you try to use: return base.
ExecuteFunction("proc_MyCustomerAdd", nameParameter, surNameParameter); Does that make any difference? Marc.
I find solution. Thanks alot. – Penguen Jun 14 '09 at 19:48 You can change sp name in C# " proc_MyCustomerAdd--->MyCustomerAdd" – Penguen Jun 14 '09 at 19:51 Yes, you can change the name of the procedure in C# - but the stored proc is still called "proc_MyCustomerAdd", and when calling base.
ExecuteFunction, I understand you have to give it the name of the stored procedure - no matter what your C# function is called.... – marc_s Jun 14 '09 at 20:27.
Try { entityContext. MyCustomerAdd(textName.Text.Trim(), textSurName.Text.Trim()) } catch (Exception ex) { ; } Added Process runs correctly. On the other hand ; after added process, give Above error.
But My solution run correct!
– Luke101 Nov 18 '09 at 7:02 Never have an empty catch block. You will never know what's happening with your code. – David Kemp Jul 22 at 15:42.
Data reader with the same name. Added is ok.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.