version 1.0.2005.1 final (self-servicing) VS2005 asp.net 2.0

Hiya, I'm having this intermittent hassle where client code doesn't find new fields that I have added to the typedList.

I obviously build, then reload the c# generated project.

The major thing I notice is that I can use a typedList in my client code that is NO LONGER in the llblGenPro designer project.

Why would this be? Surely if the typedList in question isn't present in the designer before I generate the project, then it shouldn't be in the "typedListCalsses" of the generated code??

I can confirm that I'm referring to the correct project, because when I rebuild it, visual studio notes the change and asks if I want to reload..I of course say yes.

Any ideas what's happening?

I'm losing a lot of time :-0

thanks,

yogi

What if you try to generate the code into a new empty folder?

hiya Walaa.

Yes, that removed the phantom typedlists.I've no idea why?

Do you recommend that I simply delete all the generated code in the original folder that llblGenpro generates the C# code into, so that I initially have an empty directory?

many thanks,

yogi

Normally I don't do that.

Are you suing a Source control or something? I think some files were locked for write.

You can also set any or both of the following 2 Project Properties (Use them with care, and read the description first):

CleanUpVsNetProjects When set to true, the VS.NET project file task performer will first remove all file references for files from an existing VS.NET project file, before adding the files generated. For VS.NET 2005 projects, it will remove all files generated by LLBLGen Pro, as these are marked with a Generator tag. Default is false. Note:
Use with care as an old VS.NET 2003 project may contain references to files which aren't marked with LLBLGen Pro specific XML elements/attributes, so all file references are removed, which thus also means that references to files you've added yourself to the project are removed as well, which forces you to re-add the references to those files to the VS.NET project manually. Projects created for VS.NET 2005 and with LLBLGen Pro v2.0 or higher do have the files marked as LLBLGen Pro generated and it's safe to use this setting with these projects.

FailCodeGenerationOnWriteError When set to true (default is false), the code generator engines of LLBLGen Pro will throw a GeneratorAbortException to terminate the code generation cycle if a write error occurs. A write error is generated when the target file exists and is readonly and failwhenexistent is false for the executing task.