If I start off with dlls coded to run on the same machine as the ui layer, how easily can I port them to another server without changing any code in
the dlls or especially in the UI?
thanks
"[MSFT]" <lukezhan@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:JVyVF2zaFHA.2184@xxxxxxxxxxxxxxxxxxxxxxxx > Hello,
>
> I think you have several choices in .NET:
>
> 1. Web service
> 2. COM+
> 3. .NET remoting.
>
> All of above are proper for business layer. Web service can coomunicate on
> internet ot intranet, but not best on performance. Also .NET remoting with
> HTTP channel. For better performance, you may consider COM+. It also
> support other issues like transaction. Check EnterpriseService Namespace
> in
> NET framework for more information.
>
> Luke
>
How to use .net remoting with web service? ... I have a question about .Net Remoting, I hope there's someone who can help me. ... We are making an academic project that includes .Net Remoting. ... that our server makes all the things and every objects saved in server. ...Web service is only used for getting the events results. ... (microsoft.public.dotnet.framework.remoting)
Re: Enterprise deployment.. ... I need to design the app ground up to be scalable...using .NET Remoting... to expose/communicate to my buisness layer...... (microsoft.public.dotnet.languages.csharp)
Re: Using Sharepoint function remotly on .NET ... use the sharepoint object model and expose them using .net remoting or ...web service.... I'm just new to SharePoint Portal and have been testing some basic ... > different application not residing in the same server as the SP. ... (microsoft.public.sharepoint.portalserver.development)
Re: LSA vs LSP GUI on Vista/2008? ... Thank you so much for the new information about .NET Remoting, you have saved me a lot of time by explaining it and providing the link to the article. ... But I still find it limited to COM/DCOM servers that use scripting interfaces - with these you can use pure text source code files without needing to compile, but still get lightweight and high-performance clients because all the work is being done on the server. ... But this has become more difficult with Vista/2008 and x86/x64, for example the MSI can be exposed as a COM server, but the registry keys are now owned by "TrustedInstaller" and I don't like changing security settings, so there's a lot of good technology in Windows that can't be used to it's full extent. ... Although .NET components are almost on every Windows server,... (microsoft.public.platformsdk.security)
Re: COM+ vs .Net Remoting vs... ... AS> guidelines for these techonologies usage.... AS> there is have to be realizaed capability to use application server... AS> What are the advantages of COM+, of .NET Remoting in this case? ... It's more usable from unmanaged code than from managed, because managed COM+ is just new EnterpriseServices namespace that don't replace unmanaged COM+ and just give u new namespace. ... (microsoft.public.dotnet.distributed_apps)
