View Single Post
  #6 (permalink)  
Old August 3rd, 2011, 01:19 PM
Imar's Avatar
Imar Imar is offline
Wrox Author
Points: 72,055, Level: 100
Points: 72,055, Level: 100 Points: 72,055, Level: 100 Points: 72,055, Level: 100
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Jun 2003
Location: Utrecht, Netherlands.
Posts: 17,086
Thanks: 80
Thanked 1,587 Times in 1,563 Posts

IMO, that's a pretty difficult and time-consuming way to create and debug web applications. Understanding how your code runs and where it breaks is invaluable in tracking issues like this. If I were you, I'd:

1. Create a backup of the remote database
2. Restore it against your local SQL Server Express version
3. Modify the connection strings to work with the local database
4. Develop and test locally, while keeping track of changes you make to the database.
5. When you're ready to deploy, update the database and then send over the ASP.NET and other files to the live site.

Just my 2 cents.

With regards to your "latest thought": that would work, but it won't change anything. I don't think the counter variable is null as you haven't declared it as a nullable type, leading to another error than the one you're getting now.....

Imar Spaanjaars
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!
Reply With Quote
The Following User Says Thank You to Imar For This Useful Post:
esherr01 (August 3rd, 2011)