“Dot Net Remoting frequently Asked Questions in various Dot Net Remoting job Interviews by interviewer. Get preparation of Dot Net Remoting job interview”
.Net remoting is replacement of DCOM.
Step 1:Build a proxcy which is looks like a real obj.
Step 2:By useing proxcy U can make method calls on remoting
objs.
Step 3:These method calls know as "Messages", messages can
be serialized by Formater.
Step 4:It send to client channel.
Step 5:Client channel communicate with sever channel. And
Deserialized the Messages.
Step 6:Sever send the exact remot obj.
Remoting Performance and Auto Web Proxy .
The .Net Framework 2.0 has significant changes to its
support for proxies including support for connection-
specific proxy settings, automatic proxy configuration and
the ability to automatically refreshing proxy settings
whenever the active connection changes. These features can
be very useful in .Net Remoting but the auto web proxy
feature can also affect performance. If you do not need
these settings in your client it might be useful to disable
them.
There are a number of ways to disable this:
1. In Internet Explorer Open Internet Options,
(either through control panel or the Internet Explorer™
tools menu), switch to the connections tab, and select LAN
settings. Clear all checkboxes under automatic
configuration. This will disable automatic proxy settings
for the current user (note that this will not work for
ASP.NET sites making outgoing web service calls because
they run under a different user).
2. Imperatively disable it by setting
System.Net.WebRequest.DefaultWebProxy = null;
3. In your config file bypass the proxy for your web-
server. You can also disable the default proxy altogether.
.NET remoting is specifically used when you are using only
Microsoft platform. Remoting cannot be used between .net
client and non .NET clients.
Web services though can be used for communication on
MIcrosoft technologies, but their main feature is Platform
Interoperability.
So if you are using client and server supporting .NET
framwork, iwould recommend to use .NET remoting because
you can customise it to great detail and also its faster.
If you are developing for cross platform technologies, you
cannot use .NET remoting. So the only option you have is ot
use web services
Binary over TCP is the most effiecient, SOAP over HTTP is
the most interoperable.
Yes we can call a native function exported from a Dll in
the following way,
I used C#.Net for Coding.
Add a Namespace that "System.Runtime.InteropServices"
Then use the following code,
Syntax:
[DllImport("dllname")]
here place the function in "dllname" Dll.
The runtime checks to see that only one version of an
assembly is on the machine at any one time.
.NET allows assemblies to specify the name AND the version
of any assemblies they need to run.
The compiler offers compile time checking for backward
compatibility.
rendc.org
Whether it is technological solutions or user-oriented innovations, We have put together for you the best sources of HR Interview Questions and Answers, Tech Ideas, and Programming Tutorials."
Get all the latest information on rendc.org
© 2022 | All rights reserved.
RENDC
welcome to www.rendc.org
