Confused individual needs help n- tier app

[mesa t]

Hello,

 

I have a fundamental question that I seem to have difficulty grasping.

 

I want to build a n-tier vb.net app, (not a web app), in a network environment.

 

Could I build the server side code as a collection of assemblies in a server share that I can reference in the Client code under project references ?

 

and if so, could I simply instanciate the classes within those assemblies from the client code ?.

 

Would I need marshaling or proxies ?.

 

Thanks,

 

Tino M.

[Roey]

I use one Assembly for each level in an n-tier application:

 

- User Interface

- Business

- Data Access Layer

 

Each Assembly is comprised of multiple classes that represent objects, and the class is then intantiated by the layer above it.

 

 

Hope this helps a bit

[mesa t]

n-tier questions

 

Thanks for your reply Roey,

 

I think that your comments validate my idea that in a network environment, a client machine can instantiate and use the methods and properties of the classes inside the (server machine) Business logic assembly / ies.

 

What would you suggest I use if I now want to let remote

(out of network) users utilize the same server assemblies?.

 

sockets?

 

.net Remoting?

 

Thanks,

[Roey]

Sorry but haven't done that before, and wouldn't want to guess and lead you in the wrong direction.

[PlausiblyDamp]

You may want to investigate Webservices in that case as it will allow your system to be called via a network connection.

[mesa t]

n-Tier reply

 

Thanks everyone for your comments on my questions.

 

I am familliar with webservices, but I dont want IIS involved in this application (If I understand it correctly webservices live in an IIS VD).

 

I am looking into remoting, or COM+ .....

 

 

Thanks again!

 

Tino Mesa.

[PlausiblyDamp]

I'd go remoting in preference to COM+ unless you need features specific to COM+ as it is heavily based on Microsoft standards and RPCs (all data is a binary format as well).

 

With ermoting you can still use XML (SOAP) and http so to all intents and purposes it is a webservice but without needing IIS (more work than a webservice but maybe worth it.)

[mesa t]

n-Tier re:

 

I think that will be route.

 

 

 

Thanks a lot for your help!

 

TM