Making an ASP.NET page talk to a running .NET program

[jmcgrew]

I'm not very familiar with ASP.NET, so any pointers would be
appreciated.

I'm developing a C# program which will basically run in the background
as a server. I want to have a web-based front end which people can use
to configure the server, edit their accounts, upload new data, etc.

One way to implement this would be for the server to accept
connections on a special port, and the ASP pages would connect to the
server and talk over the socket. But that adds complexity to the
server.

Is there a way to let the ASP pages work directly with the objects in
the server process instead?

 

[Coskun SUNALI [MVP]]

Hi,

Yes, .NET Remoting is used for such kind of business issues.

For information regarding .NET Remoting, please visit the following page:
http://msdn2.microsoft.com/en-us/library/kwdt6w2k(VS.80).aspx

--
All the best,
Coskun SUNALI
MVP ASP/ASP.NET
http://sunali.com
http://www.propeople.dk

 

[Eliyahu Goldin]

Consider using MSMQ with WCF. Just google for these 2 words.

--
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net

 

[sloan]

Check here:

http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!158.entry


I have a msmq example and nonmsmq wcf examples.

downloadable code....run a few .sql scripts and it'll work.


But WCF is probably the tree you want to bark up.

 

[jmcgrew]

Check here:

http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!158.entry

I have a msmq example and nonmsmq wcf examples.

downloadable code....run a few .sql scripts and it'll work.

But WCF is probably the tree you want to bark up.

This looks awfully complicated and "enterprisey" for what I'm trying
to do. Is there a reason to prefer MSMQ/WCF over .NET Remoting?

Jesse