Assembly naming convention for CSLA.NET and CSLA.NET for Silverlight

Assembly naming convention for CSLA.NET and CSLA.NET for Silverlight

Old forum URL: forums.lhotka.net/forums/t/5769.aspx


darilek posted on Sunday, November 09, 2008

Hello, is it possible declare different assembly names for each part of CSLA framework? For example Csla.dll for original CSLA.NET framework and Csla.Light.dll for new CSLA.NET for Silverlight framework. Current situation with the same assembly naming for client and server side causes a little mess in referencing in VS2008 projects. These assemblies must be located in different folders and at first look on the assembly name, I don't know what assembly type it represents

Thanks

sergeyb replied on Sunday, November 09, 2008

Assembly name is playing an important role in communicating between Silverlight client and .NET server.  As you may have noticed by looking at the Rolodex project that it also has the same assembly name as well as root namespace for client and the server, just like CSLA itself.  What you are trying to accomplish is to have the same assembly qualified class names on both sides in order for client and the server to know how to exchange the information as well as be able to share classes between different projects.  It stems from the fact that in Silverlight environment client and the server are actually using different run times.

 

Sergey Barskiy

Principal Consultant

office: 678.405.0687 | mobile: 404.388.1899

cid:_2_0648EA840648E85C001BBCB886257279
Microsoft Worldwide Partner of the Year | Custom Development Solutions, Technical Innovation

 

From: darilek [mailto:cslanet@lhotka.net]
Sent: Sunday, November 09, 2008 8:09 AM
To: Sergey Barskiy
Subject: [CSLA .NET] Assembly naming convention for CSLA.NET and CSLA.NET for Silverlight

 

Hello, is it possible declare different assembly names for each part of CSLA framework? For example Csla.dll for original CSLA.NET framework and Csla.Light.dll for new CSLA.NET for Silverlight framework. Current situation with the same assembly naming for client and server side causes a little mess in referencing in VS2008 projects. These assemblies must be located in different folders and at first look on the assembly name, I don't know what assembly type it represents

Thanks


skagen00 replied on Monday, December 29, 2008

Wow, I'm glad I stumbled upon this post. I initally started a project myself and built it up and I could not figure out why none of my server code was getting hit.

So, I started from the Rolodex and added my items and I was getting my server code to run, so I started reorganizing and renaming things and then things started failing again. I had changed my assembly names for my client project and server project to be different and consistent with their project names -- boy was that a tough one to track down.

Changed both to the same assembly name in project properties and everything started working.

(Changed post title a bit to match what I would have searched for)

Chris

Copyright (c) Marimer LLC