Home/ Questions/Q 6255757
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T14:25:34+00:00

I have a very unusual problem. I have an ASP.NET application that uses LINQ-to-SQL

  • 0

I have a very unusual problem. I have an ASP.NET application that uses LINQ-to-SQL a lot, and works fine on most servers. However the application exists on another server on the same network, and after a recent update, whenever I open a new DataContext like this:

LINQDataContext dc = new LINQDataContext();

The dc object is null, so I get object reference errors trying to use it. I cannot replicate this on my development machine, or on the other server which the application exists on, so I’m baffled about why this could be. Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Since you are using default constructor of your DataContext, then connection string is read from web.config. So we could make a suggestion that application on that server has different config without proper connection string. But there is one more thing that we’ve faced once in our project. In a new version of ASP location of connection string storage in config file has changed. I don’t have code at my fingertips, but you could test my suggestion by using constructor that takes connection string as a parameter. Read connection string from config manually or just hardcode it for testing purpose.

    • 0