The ORM Foundation

I just installed the 04CTP release of Norma and I just noticed that I cannot used the Extension Manager anymore. Whenever I click on any checkbox it closes the popup instantly. Not sure if it matters but I'm running VS2k8 on Vista. I know it worked with the previous version I had installed.

Has anyone else experienced this?

Update:

I also noticed that when I tried to use the ORM Generator Selection to create a DDIL Sql Server script it cannot load the extensions it needs. It asks if I want to load them, I click yes, but when I goto the Extension Manager nothing is enabled and no script is created.

Hi Jason,

Saw you note and just now tried this on a setup here (VS2008, Vista Ult. 32bit, 04CTP).  I created a new sln/project, and ORM file.  Went straight to context menu and opened Extension Manger. Clicked Relational View, and saw just what you stated - a vanishing act!  Tried other EM slections - same thing.  Tried after entering some Fact Types to the model - same thing.

Another system here  (VS2005, WS2008 32 bit, 04CTP), has EM woring fine!  My understanding is that the engine of Vista is much like that of Windows Server 2008, so if that's the difference, it's subtle.  On the other hand, the VS2005 and VS2008 versions of CTP are (I believe), even closer.

Following a lead from Matt C., I made sure the GAC was clear of neumont artifacts, after removing old CTP, OPliX, DSL Tools; and before installing new components.  I did not install new DSL Tools on Vista/VS2008 system, as I understand that VS2008 includes these - there were DSL Tools on that system from an earlier CTP install (possible link?).

Both systems installed and run with full admin authority.

Don't see any options in VS ORM Designer that would affect the EM.

I only looked at the Relational View in VS2005 system because I was curious.  I haven't gotten to anything yet where it's needed.  As the View is for the whole model, it's too much info for all but simple models.  I think I'd opt to shove the generated DDL it into SQL Server and using its tools to manage the Relational (logical) View.  Not the same, but may tide you over, until there's a fix.

Glad you reported the bug.

BRN..

A couple of questions for both of you:

1. Could you send me the contents of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Neumont\ORM Architect\Extensions key?
2. Could you launch VS2008 as an administrator and see if the problem still reproduces?

Those would both help me to track down the right machine configuration to test on here.

-Matt

I ran as administrator and it still didnt work.

Is this what you were asking for?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Neumont\ORM Architect\Extensions\http://schemas.neumont.edu/ORM/2007-11/CustomProperties

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Neumont\ORM Architect\Extensions\http://schemas.neumont.edu/ORM/2007-11/RelationalView

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Neumont\ORM Architect\Extensions\http://schemas.neumont.edu/ORM/Bridge/2007-06/ORMAbstractionToConceptualDatabase

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Neumont\ORM Architect\Extensions\http://schemas.neumont.edu/ORM/Bridge/2007-06/ORMToORMAbstraction

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Neumont\ORM Architect\Extensions\http://schemas.neumont.edu/ORM/Preview/CustomProperties

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Neumont\ORM Architect\Extensions\http://schemas.neumont.edu/ORM/Relational/2007-06/ConceptualDatabase

Hi Matt,

Just forwarded an email to you with this info.

Basically, the key is:

Name = (Default)

Type = REG_SZ

Data = (Value not set)

The tests I did were all when logged in as machine/system admin.

The notes in the email may give other clues.

BRN,,

Hi Matt,

Just realized I spaced and key was not expanded.  I sent the branch to you as an email attachment "For Matt.reg"

Also, a reminder: I did not use setup.bat for the install - just in case it matters.

BRN..

JasonB:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Neumont\ORM Architect\Extensions\http://schemas.neumont.edu/ORM/Preview/CustomProperties

This one shouldn't be there, delete it and restart VS. This was an ealier name for the Custom Properties extension and was dealt with incorrectly a couple of drops ago. However, it should have been pulled if the NORMA uninstalls were allowed to complete.

-Matt

Thanks Matt! Deleting that fixed the problem! :)

Hi Matt,

Found and deleted the "Preview/CustomProperties" key on VS2008/Vista system - all's well with EM now.

BTW, I tried the test for >arity predicate error I passed along to you, after removing the key (onthe off chance - even though EM was working on VS2005 system, with the same problem), and that problem is still there.  Still, I can send you a (text), copy of the Neumont branch for both VS2005 and VS2008 systems.  Maybe you'll spot a clue for the cause of the this other problem.

BRN..

Sure. This should only happen with a bad uninstall, or if you've built from sourcecode previously on the machine. This particular entry was incorrectly added via setup in the past, so may be hanging around on some machines. The issue is two extension namespaces mapping to a single loaded extension DomainModel. It blows up badly when an attempt is made to create the reverse mapping, which is assumed to be 1-1. The reverse mapping delay loads, and is needed to determine which other extensions need to be checked in the dialog--hence the crash on click for models with dependent extensions.

I added a sanity check in changeset 1293 to the extension loader to verify that any class that serializes elements supports the extension it is registered with. This will catch this case by screening out the bogus entry, but is not 100% foolproof (extensions are required to serialize elements, although most extensions that change their namespace over time do so because of a file format upgrade).

-Matt