Home/ Questions/Q 4072170
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T16:51:04+00:00

VS2008 / TFS Build 3.5 / Ent Lib 4.1 I have a rather large

  • 0

VS2008 / TFS Build 3.5 / Ent Lib 4.1

I have a rather large solution that contains several apps. They are all currently using Enterprise Library (v.4.1) for their data access layer.

I added and locally tested a new data access layer that uses LINQ to SQL- it was fast and easy to add and the test went fine. But…

When I checked in the project, it would not complete the build – I get a “Partially Succeeded”. There are some warnings, but those exact same warnings were there prior to the build failing.

I took the data access class back out (along with the code that calls it) and rebuilt and it builds fine.

I then added an empty new class and put a single variable in it and referenced it from the code. That built. I then created a new LINQ to SQL class in that new project and did not even reference it. When I checked that in, the build failed again with the “Partially Succeeded” message. No extra errors or warnings.

I love LINQ to SQL, I have used it in a few projects outside of this system, but I now have many hours into attempting to get this to build with no success.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    OK, we found it. The issue is on stack overflow elsewhere at
    Visual Studio Setup and Deployment build fails with no errors

    The issue is a bug in MS setup and deploy that breaks when it hits a line in the project that uses Linq. You have to comment out a line in the project to get it to work. Amazing, ridiculous, and no surprise.

    Thanks for the input, it was that input that helped us get to the eventual answer (already on StackOverflow, but didn’t have Linq in the title).

    • 0