Hi, the answer is simple: don't use Visual Metal, which is not maintained (and currently looking for volunteers :)). Use DbMetal instead (less fun, but more working).
Pascal. jabber/gtalk: [email protected] msn: [email protected] On Thu, Feb 5, 2009 at 15:33, JeroenV <[email protected]> wrote: > > I've done a checkout of the last version of dblinq from the SVN, and > build the solution. > After that, I've tried to generate the C# code for a MySQL database > using the VisualMetal tool, with a base-type of > DbLinq.MySql.MySqlDataContext > > The source code resulting from this generation contains several > errors: > - enumeration types are not defined correctly, e.g., I get > private enum READ, WRITE, READ_WRITE _AccessType; > which should be something like > public enum EAccessType {READ, WRITE, READ_WRITE}; private > EAccessType _AccessType; > > - The generated codes defines the use of the following namspaces: > using DbLinq.Linq; using DbLinq.Linq.Mapping; > these namespaces do not exist, but do exist as childs of the > DbLinq.Data namespace > > The above errors are easy to fix, but it's annoying that they are > generated like that. > More severe are the following errors: > "The type or namespace name 'AutoGenIdAttribute' could not be found > (are you missing a using directive or an assembly reference?)" > and the same for 'AutoGenId' > > So, finally we come to my questions: > - what assembly contains the above types/namespaces? > - what am I doing wrong in VisualMetal that I have to correct these > errors, or are they bugs in the program? > > Hopefully someone is willing and able to answer these questions! > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
