The last couple of weeks I've been working on migrating an ASP.NET application from using a Visual FoxPro database to using SQL Server 2005. My application has it's logic in library DLL and with some layering uses Typed DataSets to connect to the database.
Typical code within the data access layer looks like this:
internal ViewDataSet.RequestViewDataTable GetViewByPrimaryUser( string user ){ using ( ViewDataSetTableAdapters.RequestViewTableAdapter _adapter = new ViewDataSetTableAdapters.RequestViewTableAdapter() ) { ViewDataSet.RequestViewDataTable table; table = _adapter.GetByPrimaryUser( user.Trim() ); return table; }}
The method 'GetByPrimaryUser' is defined on the TableAdapter and using the GUI designer in Visual Studio I manage my typed datasets. All SQL is stored within the Typed DataSets. There is very limited use of stored procedures.Migrating the .NET code from using a Visual FoxPro database to using SQL Server 2005 has involved the following:
After following these steps some of the datatables would generate unexplicable validation errors. Not wanting to waste too much time I just re-created those typed tables and re-added the queries on those tables.
Since the advent of cheap web hosting, we have had more development in the field of SEM. Thanks to features like internet phone, managing internet network marketing is a lot more feasible now. Marketing strategies like cpc, ppi and pay per click can be managed with much more comfort now. Usually regular advertising agencies miss out on this since they concentrate more on building links through email marketing.