Modeling .Net Remoting or DCOM

The new Application and System designers are amazing, but I'm having a difficult time figuring out how to model my application space.  Specifically, my "middle tier" is not an ASP.Net Web Service, it is either a .Net Remoting service or a COM+ application accessed via DCOM.  How do I model these  

Surely I don't have to use the "GenericApplication" object, do I  

I suppose I could use the WindowsApplication of type Service for the .Net Remoting scenario, but there doesn't seem to be anything that will generate a .Net Class Library (for the COM+ scenario).

Or am I missing something


Answer this question

Modeling .Net Remoting or DCOM

  • Chewmp

    Hi David,
    I don't have the answer for you, but I wanted to let you know that I forwarded your post to one of the program managers for Team Architect he will be posting a response to you soon. If you don't see something by today, you will have a response by Monday.
    Thanks,

    Elona Tuomi
    Team Architect User Education

  • Philred

    Thanks for letting me know.

    I've done a bit more digging, and I think the answer is to use the SDM SDK to write my own "application type" boxes for use in the Application Designer.

    But I'll be looking forward to hearing what the engineer has to say.

    David

  • vampire85

    David, thank you for the excellent question, it is timely and valid.

    < xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /> 

    Our Distributed System Designers (and in your case Application Designer) will not support .NET Remoting as a communication  protocol out of the box in VS 2005 Team Edition for Software Architects. As for the COM model, we are working on it, and most likely will deliver it through the SDM Portal ( http://lab.msdn.microsoft.com/teamsystem/workshop/sdm ) as soon as it is ready. At this time, it will not be shipped with VS 2005 as well.  Later, however, we will support Indigo with its type-sharing-based close-coupled equivalent/alternative for .NET Remoting.

     

    As you have already figured out, using the extensibility features of the SDM SDK you will be able to model Remoting support (create new Remoting provider and consumer endpoint types and define which application  types support these) but this will not impact code generation or synchronization so extending the models to do this will be for documentation purposes only. As an option, you can provide similar to Implement functionality either through custom templates in Visual Studio, or through an add-in mechanisms.

     

     In later releases we will also extend the extensibility model to allow plug-in providers that would support deeper integration with code/config but I doubt that we will then retrofit .NET Remoting support with Indigo support being the likely priority by that time.

     

    To make it short, you are able to design your own models with SDM SDK. The limitation is that there is no code synchronization/generation there by default, but you can overcome it with VS extensibility functionality. Links to SDM SDK (shipped as a part of VS 2005 SDK) and support files (samples, tools, docs) are available at the SDM Portal 's download section. When released, all these files will be a part of VS 2005 SDK.

    Please, feel free to contact me with your questions regarding our Distributed Systems Designers, SDM and extensibility.

    Best Regards,



  • Modeling .Net Remoting or DCOM