MSDN Magazine June 2004
View Complete Post
The problem: unit testing libraries, especially data access components, that have a complex set of dependencies. The solution: providing a dynamic mock implementation of your data access classes. Here the author explains just how to make testing easier and more reliable using NMock.
MSDN Magazine October 2004
In the June 2004 installment of the Bugslayer column, I introduced the amazing FxCop, which analyzes your . NET assemblies for errors and problems based on code that violates the . NET Design Guidelines.
MSDN Magazine September 2004
MSDN Magazine August 2001
Not sure which category to put this question in, so I will put it in here.
Just to give you an idea of the layout of my solution, I have the main project, along with 2 class libraries, BLL and DAL. (Business Logic Layer and Data Access Layer)
The BLL refers to the DAL and the main project refers to the BLL.
I had a test website and the code worked fine, but the same code will not work on the real project. The only difference is that in the test project, the code was on an aspx code behind, whereas in the real project, it is an ascx code behind (Web User Control )
The code is:
Dim connectionString As String = ConfigurationManager.ConnectionStrings("ASPNETDBConnectionString").ConnectionString
Dim recordEntry As New UserRecord(connectionString)
recordEntry.UserName = "TestName"
recordEntry.BMI = bMI
recordEntry.BMR = bMR
recordEntry.FTM = fTM
recordEntry.TDEE = tDEE
recordEntry.TodayDate = dateForToday
check this link
and how can i implement on aspx page to get value on textbox