Environment: Adapter, SQL2k, C#, Web App

I've created a biz layer to encapsulate the llbl functionality I want to expose to my presentation layer. The problem I'm running into is that I can't seem to debug any class in my biz layer that references the LLBL code. In my biz layer project, I have a few classes that only expose simple int/string type properties. I can step into this class. However, any class that references llbl code throws the error: "There is no source code available for the current location". I can't even view the disassembly. I saw that Frans mentions that references must be manually updated, so I've tried removing and adding the runtime libraries from the references of the 2 generated project as well as my business layer project to no effect.

Has anyone else seen this? I'm not a good enough coder to survive w/out my debugger.

Did you by any change create a release build of the generated code entities? You should be able to step into the generated code

Hey Frans. Thanks for the reply.
I've added the llbl projects to a solution that includes my bl and my nunit tests, and I'm using things in debug mode. I've double checked my config to make sure that I wasn't compiling for release anyway, and am not. I've got the pdb files and they have the same last modified date as the dlls.

I was wondering if the problem had something to do with the ORMSupport classes in the runtime folder being built as release entities. I'm not trying to step into that code, but I am returning types from that library.

Yes, the runtimes are build as release builds. If you want to have debug builds, please build the sourcecode of the runtimes manually, the sourcecode is found in the 'SourceCode' folder in the beta archive.

Hmm... Ok, that didn't do it. I built the ORM and SQL DQE libraries and still have the same problem. That's actually what I expected, since I've never had this problem before. Any other thoughts?

Thanks.

There are a lot of links about this in google,, one of them suggest you do the following:

1. Verify that you are in debug mode and not release mode.

2. Verify that the timestamp of the .pdb file is the same as the .dll or
   .exe that you're generating. If they are not, remove all of the binaries
   and recompile your entire solution.

3. If the additional assemblies you are trying to debug are not part of
   your solution (i.e. other projects), go under the properties for the
   solution and be sure to include the "Debug Source Files" and "Debug
   Symbol Files" locations of the additional assemblies you're trying to debug.

Hi Walaa, thanks for the reply. Unfortunately, I think I've done all of this. I am definitely in debug mode, (I can step through some code), the timestamp on the dll & pdb's are the same, and the project is part of my solution. The peculiar thing is that I can debug some of the code in my project, but not all of it. The code I can debug doesn't reference any llbl runtimes or the generated code. That may not be the problem, but it's the only distinguishing characteristic I've found so far.

Thanks for checking things out for me.

I've been writing some tests to see where the problem is, and my current guess is that it may be a partial classes issue. In any event, I know the problem isn't llbl, (though I didn't really think it was to begin withm, but the collective programming knowledge on this board seems to exceed any other I'm familiar with, so I figured this was a good place to check.) At any rate, I'll mark this as complete since it's not a beta issue, but if anyone has any other suggestions, I'd love to hear 'em.

Thanks all.

Thanks for the extra info, Jeff. I've no idea what could be the problem either...