When I move my app to the production server, how will my apps resolve the previous server name?



Download: The Developer's Guide to IoT
The IoT world may be exciting, but there are serious technical challenges that need to be addressed, especially by developers. In this handbook, learn how to meet the security, analytics, and testing requirements for IoT applications.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.
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
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.
Meet all of our Microsoft .Net Development experts
Start the conversation
0 comments