Re[1]: Which form should I choose to build client application?

dotnet framework

    Sponsored Links

    Next

  • 1. I need to connect to a server using the share name
    I have a remote server that I need to connect to and this is the parameter that will be passed to my program in C#... "\\server_name\share$" I tried sockets. The foll is the code that I give in... remoteHost = "xxx.xx.com"; //actual name is entered in here remotePort = 0; //since I do not have a port number IPHostEntry hostEntry = Dns.Resolve(remoteHost); foreach(IPAddress address in hostEntry.AddressList) { IPEndPoint ipep = new IPEndPoint(address, remotePort); clientSocket = new Socket(ipep.AddressFamily, SocketType.Stream, ProtocolType.Tcp); Console.WriteLine("Address {0}", Convert.ToString(address)); try { clientSocket.Connect(ipep); } catch(SocketException se) { Console.WriteLine("Code: {0}, Msg: {1}",se.NativeErrorCode,se.Message ); } } Result-- It is able to resolve the netbios name to an ip address but since I do not have the remote port number, the error code is "10061" and the error message is - "No connection could be made because the target machine actively refused it." Is there a way to get around giving the port number and simply connect using the share name? Thanks in advance Jan

Re[1]: Which form should I choose to build client application?

Postby zhenghuan » Fri, 02 Jul 2004 11:56:35 GMT

   Hello Sunny
   Thank your help.I want to develop a p2p application,which could change the different channel auto depending on the location of the user.When the user is inside the firewall then use the Tcp-channel,otherwise use Http-channel.Accroding what you said,I can do it with winForm application. I hope I don't misunderstand your suggestion.

   Wed, 30 Jun 2004 09:31:15 -0500  Sunny



   
             zhenghuan
              XXXX@XXXXX.COM 


Similar Threads:

1.ASP.NET vs Windows Forms for building client application

I kind of understand the ASP.NET architecture in terms of building web pages 
with embedded server controls, where the .aspx is run on the client and the 
.aspx.cs runs on the server.

But what if I want to build an ASP.NET based application that is to be run 
entirely on a client (all files hosted on the client and run on the same 
client)? What would that client need to run it?

I want to write an application that can be run standalone on a PC (not 
hosted on a web server and accessed from a PC), which uses web technology 
like javascript and Ajax, while also being able to code the primary logic in 
C#. I have the choice of a windows forms rich client application which uses 
a WebBrowser control, or a native ASP.NET application. But I'm not sure the 
latter is even feasible for being deployed and run standalone on a PC - 
would it need IIS and .NET framework installed, and even more? 


2.Which form should I choose to build client application?


     

  I read the book named <<Microsoft.NET Remoting>>,in which it mentioned we can use http channel in WAN,and Tcp Channel in LAN,and we can custom proxy to achieve it auto. But I wonder which form of client application should I use,web based or winForm based? Because if I use web based application as asp.net, then I could use http channel.While I use the winForm application,I can use Tcp channel. which form of client application could make me do it auto? Can some friend help me? 

   
             zhenghuan
              XXXX@XXXXX.COM 

3..NET Windows Forms Application VS MS Access client Application

SQL Server will be used as the back-end database to a non trivial client 
application.

In question is the choice of client application:

I need to be able to speak intelligently about when one client (MS Access vs 
.NET Windows Forms) would be preferred over the other. While I have some 
good arguments on both sides, I would appreciate your points of view on the 
topic.

For the sake of this discussion, please assume a *non trivial* client 
application with, say 120 forms, secure data processing, hundreds of 
reports, and a clear need for a rich UI experience (MDI, a variety of rich 
UI controls, non trivial printing requirements, etc).

I would appreciate help in compiling arguments both for and against each 
technology (MS Access and .NET Windows Forms) as a client application.

So far I have this (in no particular order):

BENEFITS OF a .NET Windows Forms Application:
1. Client can be MDI (whereas Access only SDI)
2. Much richer UI with .NET (vs MS Access UI controls)
3. Easier deployment (with ClickOnce, XCopy, and similar .NET technologies 
or methods). The client already has the CLR installed as part of their 
standard desktop image - so I need to put nothing more than "XCopy" the 
application files onto the local machine.
4. .NET requires a smaller footprint on the client with respect to the use 
of 3rd party UI controls. MS Access is a COM-based technology and therefore 
requires that 3rd party controls be COM controls. These require installation 
to Windows\System32 and associated updates to the Registry (whereas .NET 3rd 
party controls require only XCopy deployment to the application folder)
5. 3rd party UI controls for .NET are more prevalent, capable, and rich than 
3rd party COM controls. Plus support for COM controls (i.e. number of 3rd 
party companies making and supporting them) is expected to only decrease, 
not increase, during the coming years - with the exact opposite trend 
expected for 3rd party .NET controls.
6. .NET Windows Forms applications can take full advantage of OOP constructs 
and patterns - thereby enabling the developers to create applications that 
are easier to maintain, more easily extensible, and better architected than 
the "equivalent" functionality provided in an MS Access application.
7. Visual Studio .NET significantly increases developer productivity (vs MS 
Access support for application development)
8. The .NET base classes significantly increase developer productivity by 
pre-packing substantial functionality that would have to be coded from 
scratch in MS Access.
9. Runtime performance of a .NET application would likely be faster than MS 
Access because MS Access (really Jet) necessarily entails a file server 
architecture, while ADO.NET necessarily entails a distributed (and 
disconnected) architecture.
10. ADO.NET takes care of connection pooling automatically and provides a 
huge amount of built-in functionality that substantially increases developer 
productivity and increases programmer control over database communications 
and updates (as compared to JET and DAO).

DOWNSIDE OF a .NET Windows Forms Application:
1. Increased expertise required for .NET development - vs. MS Access (at 
least that's the perception of the client)
2. Requires the target version of the CLR to be installed on the client 
machines (leading possibly to multiple versions of the .NET Framework 
installed simultaneously. Not that I have a problem with it, but their 
desktop support folks might).

BENEFITS OF a .MS Access Client Application:
1. Less expertise required on the part of the developers (at least that's 
the perception of the client).
2. Out of the box it includes many useful UI controls and a first-class 
report writer.

DOWNSIDE OF a .MS Access Client Application:
1. Insert right here THE EXACT OPPOSITE of all of the benefits of a .NET 
Windows Forms application, then:
2. The client machine must have the correct version of MS Access installed 
(i.e. they're stuck with a particular version, or all must upgrade 
simultaneously).
3. Passthrough queries would be required in order to get the query 
processing to happen on the server. Passthrough queries ential some 
additional complexity than non passthrough queries.
4. Without the use of passthrough queries, SQL Server's locking mechanisms 
can behave unexpectedly (e.g., locks can unexpectedly be placed on tables 
rather than pages or rows) - thereby resulting in slower performance.
5. Date processing logic is less secure because users can, relatively 
easily, view and modify the client-side code and/or queries.

Any additions to these lists are greatly appreciated!

Jordan 


4.Building a client-server application with .net 2.0 and above

What are the data access choices that I have in building a client-server 
application with .net 2.0?  If the application does not need to support 
running from browser, do I still need to understand xml web services or .net 
remoting?



5.Choosing security method for .net and java clients on different OSs

Hi guys!

I have to choose a security method for my web service. PLEASE HELP
ME... I have a problem... The definition is:

1. I have created web service with several methods e.g.
method 1: SignIn(login, passwd) (if needed)
method 2: id = PrepareSomething()
method 3: Something = GetPreparedSomething(id)
method 4: SignOut() (if needed)

2. Web Service is created using .NET 2.0 (VS 2005)/Windows 2003 server

3. There are about 5-10 clients using different platforms/OS (Windows/
Unix/Linux) and applications created in different languages
(mainly .NET 1.0/.NET 2.0, Java)

4. Web service is accessible in Internet.

5. Objects, that are returned by this web service, are rather small.

6. I have to secure this web service - only some users can access it.

What method of securing this web service should I choose? Do you have
any suggestions?

Thanks in advance for your help!
Pawel Krolak

6. Choosing the right Oracle Client

7. How to build a complete application by hosting windows forms in Internet Explorer

8. OT: Application to automate process of building forms from a SQL DB



Return to dotnet framework

 

Who is online

Users browsing this forum: No registered users and 73 guest