Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In one of my current projects we keep running into this very wierd problem with Linq-to-Sql:
If we update some properties of some objects (that are mapped to the db) and then SubmitChanges as usual, we are not able to see these changes until we rebuild the entire solution in visual studio.
How come?
I assume your LINQ objects are in a different project? And that you are referencing that project in the code that ends up calling SubmitChanges? It is entirely possible that the code is using the previously built version of the project dependency, and therefore the version without your changes. If you right-click on your executing project in the solution explorer and select “Project Dependencies”, make sure that the dependent LINQ project you have is checked off on that list. Similarly, on the second tab of the dependencies window is Build Order. Your LINQ project should be built before the project that depends on using it.
EDIT: I’ve seen this problem in the past before where the reference LINQ project was reference by DLL instead of “by project”. You might delete the reference and then re-add it, making sure you do so via the “projects” tab.