bigwave wrote:
I'm currently investigating LLBLGen Pro for use in a major new project at my company.
The two questions that I need to answer are:
1) Will it work with Visual Studio 2005 (Whidbey)? As this project is part of our participation in the Whidbey early adopters (Ascend) program.
The code should compile fine on .NET 2.0 beta's. Of course the code is for .NET 1.x, so fancy features of .NET 2.0 aren't implemented in the generated code. Also, vs.net project files are currently vs.net 2002/3 only. A vs.net 2005 project file creator is in the works.
2) Can the SD.LLBLGen.Pro.ORMSupportClasses and SD.LLBLGen.Pro.DQE.SqlServer assemblies source code be downloaded?
All customers have access to the runtime library sourcecode, drivers sourcecode, all task performers sourcecode and sourcecode of some sdk tools like a commandline generator frontend.
This is because we have been bitten badly in the past with third party components which have had bugs, no updates and no source code.
Bugs can't be avoided but our goal is to fix every bug reported a.s.a.p. and every fix to the runtime libraries for example is accompanied with new source archives.
Looking at the forums I have found
http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=1764
which I think says that the source can be either downloaded, or found in the install directory of LLBLGen, however the dowload seems to be for paid up customers only and the demo install doesn't seem to have any source code in the installation directory.
No the demo doesn't have the sourcecode
Also please check: http://www.llblgen.com/pages/customerbenefits.aspx
Am I correct in thinking that there are no dependencies on propriatary third party components in the generated code?
Correct, there are no dependencies to 3rd party components other than some .NET providers for some databases, IF you need them. So if you want to use MySql, you have to have Corelab's MySqlDirect.NET provider installed. However if you don't use MySql, but for example SqlServer, you don't have to have the Corelab provider installed, as the assembly is never used and therefore never loaded in that case.