Hi, Bryan (Costanich) recently pointed out a problem with .dbml files and Visual Studio. When adding a .dbml file to a Visual Studio project, VS generates a .cs file from the DBML, but uses SqlMetal, even if the .dbml file comes from DbMetal.
At first sight, I thought it was possible to make SqlMetal generate a valid .cs, but we came to a big limitation: - EntitySet and EntityRef are going to be DbLinq's classes, not System's. So we need to use DbMetal to generate second part too, which is dbml -> cs. What are the options? I think to register DbMetal as a VS custom tool, so the only required change would be to change the custom tool name in .dbml properties. Anything else? Pascal. jabber/gtalk: [EMAIL PROTECTED] msn: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
