Dear all,
If i use the same Business Logic in a VB.NET and ASP.NET, the business logic
is the same to be used on VB.net windows application and Asp.net web
application.
Which method to implement the business is better ( Class Library or web
service)

I'm afraid if i change the business logic in the CLASS LIBRARY, i need to
redeploy the dll in the windows application

I'm afraid if i use the business logic in the WEB SERVICE, the performance
will be down graded, is it right, it need marshaling..

That's the trade off. Have you checked out "one click deployment"
in .NET? Are you sure you can't deploy the dlls without too much
hassle?

If you use web services, you will still need to deploy updates
to the desktop if the interfaces change (particularly if you
require a new parameter). Plus, your client app would
need to have internet access at all times.

--
Robbe Morris - 2004/2005 Microsoft MVP C#

Earn money answering .NET Framework
messageboard posts at EggHeadCafe.com.
http://www.eggheadcafe.com/forums/merit.asp



[quoted text, click to view]

I'd have to go with class library distributed to each client. Like Robbe
said you can go with 'one click deployment' or the Updater Application Block
by MS. I've modified it before to work as a screen saver and its pretty
solid for updating any of the assemblies.

As far as web services, dont believe the hype! SOA and all that "we must
distribute EVERYTING" chanting you hear comming from redmond is bull. If we
listened to all the evangelish comming from MS everything would be a web
service, and we'd use SOAP serilization, XML, DataSets, data binding,
reflection, and a web UI for every application.

Remember, the number one rule in distributed objects. Dont distribute them
if you dont NEED to. distributed objects are just one tool in your tool box.
MS would (for some reason i dont get) love for people to thing its the
silver bullet tool that works for every situation. Anyone remember MTS?
Anyone remember MS's recomendation for MTS? one class per dll, and all dlls
in MTS. then COM+ and Component Services came out. MS changed its tune to
group classes by functionality and ALL DLLS IN Compnent Services.
distributed objects is the end all silver bullet for EVERY situation!!! woo
hoo!!! :-) catch the sarcasim?

sorry about the soap box, but the 'best practices' that come from redmond
kill me sometimes. MS seems to try and promote building the slowest
applications ever. Heck, i worked there and the coding practices were crazy.

web services are great for cross platform communication, or internet
communication. but internally between servers of the same platform, its a
waste of CPU cycles. distribute your assemblies to the client or use
remoting or sockets.

that my 3425234.34 cents worth :-)



[quoted text, click to view]