The ORM Foundation

OK, I just fixed the issue with the DatabaseImport project (the missing reference to Microsoft.VisualStudio.Shell.Interop.9.0). I'm not sure what the problem is with the ORMModel project. It builds correctly on my system... What version of Visual Studio 2008 (beta 2?) are you using? Which version of the Visual Studio 2008 SDK do you have ...

Which version of VS2008 are you trying to compile it against? It should compile correctly against VS2008 Beta 2 ss long as you follow the instructions at https://sourceforge.net/forum/message.php?msg_id=4590202

Hi Brian, The .NET Framework 3.5 will definitely be ready at the same time as (if not prior to) VS2008 being ready; it is a hard dependency of VS2008, without which VS2008 can't even run. Although the ''launch event'' for Visual Studio 2008 is February 27, 2008, the actual RTM and release will almost certainly be before the end of this year. ...

We are still working on our final plan for how to deal with some of the versioning and side-by-side issues posed by supporting multiple versions of Visual Studio. We are also waiting for the availability of the redistributable installer for Visual Studio Shell, so that we can determine what components will be included in it. Because of this, we ...

Yes. The only other dependencies that NORMA has are on DSL Tools and PLiX, both of which our setup package will install if necessary.

Hi Joe, Would it be possible for you to send me a copy of the ORM file you're experiencing this with? I can take a look at it and try to track down what the problem is. Kevin

The quotes are the mechanism used in the ISO SQL Standard to create a ''delimited identifier''. Microsoft SQL Server works correctly with this, and also supports an alternative (non-standard) notation using square brackets (e.g. [Order]). Delimited identifiers (as opposed to ''regular identifiers'', which are just identifiers without quotes or ...

Brian, You are correct in that the number of diagrams / pages that any element of the model appears on does not effect how that element is mapped. Objectified fact types may or may not have their own representation after they have been mapped. As with any other object type, it depends on the roles that they play. It is entirely possible for ...

Hmm, given that it isn't IsIndependent that is the problem, I'm not sure off hand what would be causing those elements to not appear in the relational view.

The relational view available in the current version is only an early proof-of-concept of what we are planning to support. It is not synchronized to the our DDL code generation; the tables, columns, and constraints it shows may or may not appear in the actual DDL. We should have a release available by the end of this week that will contain a ...