Romting vs Web Service in vs2005

dotnet framework

    Next

  • 1. Response Point
    I am trying to make an outbound call and the system keeps coming back and saying that this is not a valid extension. This seemed to be working the other day and now it has just stoped working
  • 2. Finding my VPNs
    I am writing a connection program for which I need to iterate my VPN connections. When I use the static method System.Net.NetworkInformation.NetworkInterface.GetAllNetworkInterfaces() I can't find them unless they are already connected. But I am looking for the ones that aren't connected yet, so I can start them using RASdial. Anyone has any clue where to find them? Theyare listed in the Network Connections window so they must be findable. tnx, Ton.
  • 3. Client crashes when calling method in server
    Hi, Still working away on my remoting based client/server setup - new problem I have is as follows: My windows service (the "server" as far as remoting is concerned) has a method that is called by a timer at certain intervals. This raises events that the "client" (a Winforms app) receives and acts on. This works absolutely fine. However, I want users to be able to manually kick off said method whenever they want in addition to the timed ones, and this is where the problem lies. I put a button on my forms app that calls the same method in the server, but at the point within the method that the event is fired back to the client, the client freezes. I assume this is because the method it called on the server hasn't yet completed, so the two bits of communication are somehow getting crossed and cocking things up... any pointers?

Romting vs Web Service in vs2005

Postby RkxEYXZlTQ » Fri, 27 Oct 2006 21:46:02 GMT

I'd like to get some ideas of the best way to accomplish the following in 
vs2005:
   Win1 - a windows application
   Web1 through WebX- many website applications

I'd like to talk from Web1-WebX to Win1 and also back through, at this 
thinking, a web service.  I need Win1 to communicate to only a specific Web 
application at a time.  I don't need the websites to talk to each other, 
though.

For example: 
   Web1 messages to Win1 "Name: Joe"
   Web2 messages to Win1 "Name: Mary"
   Web3 messages to Win1 "Name: Bigfoot"
   Win1 responds to each of these websites individually, not like a 
broadcast message.

I think .Net Remoting might be a better way to go than a WebService, but I'm 
not sure.  I really don't know that much about Remoting, so if someone is 
suggesting that, can they also point me to a good tutorial or book?

Thanks,
Dave



Re: Romting vs Web Service in vs2005

Postby Spam Catcher » Sat, 28 Oct 2006 03:19:52 GMT

=?Utf-8?B?RkxEYXZlTQ==?= < XXXX@XXXXX.COM > wrote in




What sort of messages are you passing back and forth? Will it be 
primarily primative data types? If they are - web services will suffice. 
If you need to pass complex data types (typed objects, .NET data types, 
etc) I would use remoting.

Remoting should provide better performance than web services if you're 
transferring large amounts of data.

Bi-directional communications should be easier with remoting as well.




Re: Romting vs Web Service in vs2005

Postby RkxEYXZlTQ » Sat, 28 Oct 2006 03:35:02 GMT

SC, Thanks for the quick reply.

I think at this point I'll pretty much be sending a simple string.  The 
thing is, with a web service, I don't know, if say 5 web users have 
instantiated the web service, how can my windows app call the web service and 
tell it to send info to just one of the websites?  Doesn't each website 
instantiate the web service, and then how will the web service instantiated 
through the windows application even know where to route the reply messages?  
Or am I over-complicating things?






Re: Romting vs Web Service in vs2005

Postby Spam Catcher » Sat, 28 Oct 2006 03:45:35 GMT

=?Utf-8?B?RkxEYXZlTQ==?= < XXXX@XXXXX.COM > wrote in




With web services, each web service is a different class - you need to pre-
generate the web service proxy beforehand. Thus, with web services, you 
need to know the servers up front.

I believe there are way to dynamically generate the web service proxy on 
the fly, but I have never done it before.

If you need to dynamically call/register servers ... it is very easy to do 
in remoting.


Routing reply messages is the challenging part with web services - web 
services doesn't support bi-directional messaging... so you'll need 2 web 
services on each box - a sender and receiver.

If bi-directional communications is a requirement, go with remoting or a 
custom solution like sockets + XML?

Re: Romting vs Web Service in vs2005

Postby RkxEYXZlTQ » Sat, 28 Oct 2006 04:55:02 GMT

SC: Thanks again.  I guess it's Remoting for me.  Any outstanding, can't miss 
articles or tutorials you know of?

Thanks,
Dave






Re: Romting vs Web Service in vs2005

Postby Spam Catcher » Sat, 28 Oct 2006 10:16:41 GMT

=?Utf-8?B?RkxEYXZlTQ==?= < XXXX@XXXXX.COM > wrote in




How to do stateless bi-directional remoting in IIS:

 http://www.**--****.com/ 

How to do bi-directional remoting (non-stateless):

 http://www.**--****.com/ 

I hope that helps : )

Similar Threads:

1.Web service convert to VS2005 web service

I've upgraded a webservice project from VS2003 to VS2005.  In my VS2003 
solution I created a handy msi install for the webservice that always worked 
fine.

In my VS2005 solution I also created this msi install for my VS2005 
Webservice app.  The web service works fine in the IDE in debug run mode and 
compiles just fine into a MSI install but after the install I try to hit the 
main asmx page and get the following error:

Server Error in '/tezDataAccess' Application.
--------------------------------------------------------------------------------

Parser Error
Description: An error occurred during the parsing of a resource required to 
service this request. Please review the following specific parse error 
details and modify your source file appropriately.

Parser Error Message: Could not load type 'tezDataAccess.Global'.
Source Error:
Line 1:  <%@ Application Codebehind="Global.asax.vb" 
Inherits="tezDataAccess.Global" %>
Source File: /tezDataAccess/global.asax    Line: 1
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET 
Version:2.0.50727.832

If I remember when I converted to VS2005 it did not create a Global.asax 
file which I use extensively.  I added one to the project and like I said 
all works fine in the IDE and even hitting the service on my box just from 
IE.

Obviously something is not right with the install - also I'm installing this 
on a Windows 2003 Server whereas my box is running XP Pro if that'd make any 
difference.....

Anyone else run into this?

TIA

Harry 


2.Remoting vs Web Service in vs2005

OK, sorry about the typo in the subject and another tidbit:
The websites are not restricted to the same machine the Win1 is on (I 
thought this was obvious, but I just want to be clear).

"FLDaveM" wrote:

> I'd like to get some ideas of the best way to accomplish the following in 
> vs2005:
>    Win1 - a windows application
>    Web1 through WebX- many website applications
> 
> I'd like to talk from Web1-WebX to Win1 and also back through, at this 
> thinking, a web service.  I need Win1 to communicate to only a specific Web 
> application at a time.  I don't need the websites to talk to each other, 
> though.
> 
> For example: 
>    Web1 messages to Win1 "Name: Joe"
>    Web2 messages to Win1 "Name: Mary"
>    Web3 messages to Win1 "Name: Bigfoot"
>    Win1 responds to each of these websites individually, not like a 
> broadcast message.
> 
> I think .Net Remoting might be a better way to go than a WebService, but I'm 
> not sure.  I really don't know that much about Remoting, so if someone is 
> suggesting that, can they also point me to a good tutorial or book?
> 
> Thanks,
> Dave
> 
> 

3.COM+ Web Services vs. .NET Web Services



Return to dotnet framework

 

Who is online

Users browsing this forum: No registered users and 50 guest