locked
DSN or not DSN RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    User-835668542 posted

     Hello,

    I am new to the deployment of my database-driven ASP.NET application to the Godaddy.com web server; therefore, I need some help in understanding the purpose of connecting to the database with DSN and without DSN. It looks like under Visual Studio Web Developer, we do not need to connect to the db with the DSN concept. But why do we need to go through the the connection to the db step with or without DSN on the web server.

     Thanks in advance for your tips

    Jacthemanus
     

    Saturday, October 20, 2007 10:07 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    User-821857111 posted

    DSN's are an old technology.  They use ODBC which has been deprecated.  Consequently they create additional unnecessary overhead.  The main reason that people use DSNs is because a lot of MSDN examples are so old, they use it - although that's not true of any ADO.NET examples where the new SqlClient provider is used (or Jet OleDb provider for Access).  I think they used to be used to obscure usernames and passwords in the olden days, but since you can encrypt connection strings in ASP.NET, that reason no longer has legs.

    Really, there is absolutely no reason to use DSNs.


     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Saturday, October 20, 2007 2:20 PM