Hi,

This isn't specifically about LLBLGen but its related to its use. I have a seperate project for my DAL layer and its dll is being referenced by the main project. After the DAL project is changed and recompiled, the main app's local copy is not being refreshed.

I have to go and delete the old version from the bin folder so that it re-copies it. Only then does the main project use the correct version.

I have configured the project depedencies such that the main project is compiled last.

Any ideas?

Cheers, I.

This is a general dot Net referencing problem.

One possibility for this is that it failed to copy the dll in the bin directory, maybe it was used in the memory !!!

Best work for this is to have all your projects in one solution, so your main Application will reference the DAL project not the dll directly.

Another solution is to try "copy local = false"

Last solution is to delete it manually as you did

This isn't specifically about LLBLGen but its related to its use. I have a seperate project for my DAL layer and its dll is being referenced by the main project. After the DAL project is changed and recompiled, the main app's local copy is not being refreshed.

I believe I ran into the same problem. Couldn't figure out why the main app's local copy was not being refreshed. So I opted for this solution: Since the DAL is located in a completely seperate solution/project, you can run post build events. In my case, I run a post build event which runs a batch file which copies the DAL project dll's to the main app's bin directory. In short, everytime I build the DAL it automatically copies the DAL dll's to the bin directory. I haven't had any problems since.

Hmm, well I think I fixed it by updating the reference paths in 'Common Properties -> Reference Path' within the main project's properties.

I deleted a few items and changed the order.