Wiki Link: [discussion:1828]
Cannot create a Reference in ModelBus sample 

Jun 3 2009 at 9:42 PM
Hi,
I cannot create a State Reference in the sample. It builds without error and I launch in Exp hive, when I open the existing reference, there is a warning with the text "Warning: Not able to open the reference model 'Sample' when looking for element 'State1'. Browse to find the referenced file.".

When I select browse and choose a model file, nothing happens, all 3 input UI controls on the "Create Reference to Element' dialog are empty".

A few questions about the ModelBus. I have built in our own DSL solutions a similar cross model referencing infrastructure based on a path syntax and a moniker resolver. The approach I took was to enable model references to refer to a model which is an embedded resource in a referenced dll. Are there suitable extensibility points in the ModelBus architecture to provide my own model resolver to achieve similar functionality?

What about T4, will you allow model reference resolution at T4 time? How will this be supported? Or is the ModelBus completely dependent on Visual Studio being the operating environment?

Coordinator
Jun 8 2009 at 3:20 PM

PeteGoo wrote:
Hi,
I cannot create a State Reference in the sample. It builds without error and I launch in Exp hive, when I open the existing reference, there is a warning with the text "Warning: Not able to open the reference model 'Sample' when looking for element 'State1'. Browse to find the referenced file.".

When I select browse and choose a model file, nothing happens, all 3 input UI controls on the "Create Reference to Element' dialog are empty".


Hello Pete. Thanks for your feedback. You are right there was an error in the StateMachineOverModelBus sample (the Build events copied the folder to the %UserProfile%\Roaming\Microsoft\VisualStudio\10.0\Extensions, instead of copying just its content, which is what we need to do for Beta1). I just replaced the zip file, and updated the code (a few code improvements, and tabification of the files).



A few questions about the ModelBus. I have built in our own DSL solutions a similar cross model referencing infrastructure based on a path syntax and a moniker resolver. The approach I took was to enable model references to refer to a model which is an embedded resource in a referenced dll. Are there suitable extensibility points in the ModelBus architecture to provide my own model resolver to achieve similar functionality?

Yes, we believe that we have designed the ModelBusAdapter and ModelBusAdapterManager in a generic enough way so that you can do it. Contact me if you need.


What about T4, will you allow model reference resolution at T4 time? How will this be supported? Or is the ModelBus completely dependent on Visual Studio being the operating environment?

T4 over the modelbus is something that you'll discover (among other nice goodees) in Beta2.

Jun 8 2009 at 8:34 PM
I've tested the updated release and it seems good.

Awesome, I can't wait to try some of this stuff out. I'll try to send you a few details of what we are trying to achieve when I get time but it may be through the TAP program.

Thanks,
Pete

Dec 7 2009 at 3:36 PM
Hi, I am trying to do resolving of modelbus references during transfomration in T4. However, the modelbus service is not available during transformation due to IModelBus not being serializable, which is required during remoting. I am using Beta 2. Is there a solution/work around for this?

Kind regards,

Bas


Updating...
Page view tracker