Yesterday, I was handed a new project at work. We have a client who has an existing website that was built elsewhere and a couple years ago at least. It's in C# and the data access tier was generated with LLBLGen Pro. They need some new things added to the site which means modifying the existing database. Now, I've never used this tool before and was wondering what would be a better idea: modifying the existing code manually? Or regenerating everything and trying to patch it into the existing site? I also don't know what version of LLBLGen it was generated with and was wondering how I can find that out. Keep in mind, I'm completely new to this product...

Is my post too vague? I just want to know how complex it will be to regenerate the code with new DB fields and then plug it back into the existing site.

I've never had a problem refreshing a llblgen project with changes to a database, regenerating the code and proceeding to make changes to my code base, testing the code and publishing a new version. Of course your experience may vary, depending on the complexity of the code base, the severity of the changes to the database schema, and your skill level.

I also don't know what version of LLBLGen it was generated with and was wondering how I can find that out

Open any of the generated code files, the version should be written on topof the file, in the header comment. You should find something like the following:

//////////////////////////////////////////////////////////////
// Code is generated using LLBLGen Pro version: 1.0.2004.2
// Code is generated on: 
// Code is generated using templates: C# template set for SqlServer (1.0.2004.2)
// Templates vendor: Solutions Design.
// Templates version: 1.0.2004.2.071205
//////////////////////////////////////////////////////////////

I always re-generate the code against database changes, and it's always a smooth experience.

yup, I think that's the point w/ llblgen. Update the db schema and then refresh catalog in LL.