The best way to deal with this issue is to use the SQL Server Client Network Utility and create a new alias for the database. This will point to different physical servers in your development and production machines, of course. Next, in your configuration files, as well as your code, in the connection string Data source attribute, use that alias. You can even point the alias to an specific SQL Server instance, if you have more than one in a single server.
Dig Deeper on .NET Workflow
Related Q&A from Daniel Cazzulino
Here Daniel Cazzulino explains how to load a DSL (domain specific language) domain model instance file programmatically. This requires the .NET type ...continue reading
Here we offer a glimpse at 12 of .NET development expert Danny Cazzulino's top ASP.NET questions and answers.continue reading
C# developers should NOT be modifying InitializeComponent method in the code-behind (or any of the variable definitions) by hand.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.