What steps will reproduce the problem?
1. create a database in MSSql server using the attached .bak file
2. try to generate source code and mapping attributes or a mapping file for the
database using DbMetal.exe.
What is the expected output? What do you see instead?
expect a code file that can be referenced in my DotNet solution.
instead:
DbLinq Database mapping generator 2008 version 0.20
for Microsoft (R) .NET Framework version 3.5
Distributed under the MIT licence (http://linq.to/db/license)
>>> Reading schema from SqlServer database
DbMetal: System.InvalidOperationException: Operation is not valid due to the
current state of the object
at System.Linq.Enumerable.Single[Association] (IEnumerable`1 source, System.Func`2 predicate, Fallback fallback) [0x00038] in /home/james/Development/MonoSrc/mono-2.10.2/mcs/class/System.Core/System.Linq/Enumerable.cs:2330
at System.Linq.Enumerable.Single[Association] (IEnumerable`1 source, System.Func`2 predicate) [0x00007] in /home/james/Development/MonoSrc/mono-2.10.2/mcs/class/System.Core/System.Linq/Enumerable.cs:2353
at DbMetal.Generator.Implementation.Processor.ValidateAssociations (DbLinq.Schema.Dbml.Database database, DbLinq.Schema.Dbml.Table table) [0x00061] in /home/james/Development/MonoSrc/dblinq2007/dblinq2007-read-only/src/DbMetal/Generator/Implementation/Processor.cs:144
at DbMetal.Generator.Implementation.Processor.SchemaIsValid (DbLinq.Schema.Dbml.Database database) [0x0001a] in /home/james/Development/MonoSrc/dblinq2007/dblinq2007-read-only/src/DbMetal/Generator/Implementation/Processor.cs:133
at DbMetal.Generator.Implementation.Processor.ProcessSchema (DbMetal.Parameters parameters) [0x0000a] in /home/james/Development/MonoSrc/dblinq2007/dblinq2007-read-only/src/DbMetal/Generator/Implementation/Processor.cs:112
What version of the product are you using? On what operating system?
version 0.20 (checked out from svn this morning)
svn checkout http://dblinq2007.googlecode.com/svn/trunk/ dblinq2007-read-only
Please provide any additional information below.
Original issue reported on code.google.com by james.ki...@gmail.com on 17 Jun 2011 at 8:52
Original issue reported on code.google.com by
james.ki...@gmail.com
on 17 Jun 2011 at 8:52Attachments: