Tools Question

  • Thread starter Thread starter Brad Markisohn
  • Start date Start date
B

Brad Markisohn

I have a PC application (OS is Win XP Pro) that controls complex hardware
via the PCI bus. We've written the app using VB.Net; but, recently the
client has asked for remote access to data and remote control of the
hardware config. parameters via web pages. This will include
bi-directional transfers of large data files (mbytes- I looked around, but I
didn't see a native FTP capability in .Net.) The PC has an Ethernet port,
but it's not connected to a network, although it could be. The customer
wants all of the hosting capability to come form the PC managing the
hardware. I've glanced at ASP.Net, but I'm not sure if this is the correct
route. I would appreciate any suggestions or pointers to other resources
that my help me come up with a solution.

TIA

Brad
 
I have a PC application (OS is Win XP Pro) that controls complex
Click to expand...
hardware via the PCI bus. We've written the app using VB.Net; but,
recently
Click to expand...
the client has asked for remote access to data and remote control of thehardware config. parameters via web pages. This will include
bi-directional
Click to expand...
transfers of large data files (mbytes- I looked around,
but I didn't see a
Click to expand...
native FTP capability in .Net.) The PC has an
Ethernet port, but it's not
Click to expand...
connected to a network, although it could
be. The customer wants all of the
Click to expand...
hosting capability to come form the
PC managing the hardware. I've glanced
Click to expand...
at ASP.Net, but I'm not sure if this is the correct
route. I would
Click to expand...
appreciate any suggestions or pointers to other resources
that my help me
Click to expand...
come up with a solution.

Try IP*Works! .Net Edition. It includes fully
managed components, all written in C#. There are currently over 40 different
internet protocols there including FTP. ASP.Net demos (yes, FTP) are included
as well as Windows application demos in both C# and VB.Net. You can download
the trial at www.nsoftware.com/download/. If you have any questions feel free
to ask.

Regards,
Lance R.
/n software
http://www.nsoftware.com/

-
 
I have a PC application (OS is Win XP Pro) that controls complex hardware
via the PCI bus. We've written the app using VB.Net; but, recently the
client has asked for remote access to data and remote control of the
hardware config. parameters via web pages. This will include
bi-directional transfers of large data files (mbytes- I looked around, but I
didn't see a native FTP capability in .Net.) The PC has an Ethernet port,
but it's not connected to a network, although it could be. The customer
wants all of the hosting capability to come form the PC managing the
hardware. I've glanced at ASP.Net, but I'm not sure if this is the correct
route. I would appreciate any suggestions or pointers to other resources
that my help me come up with a solution.
Click to expand...

That's a very broad question... if they want to access your app via a web
page, your best bet would be ASP.NET. It has the ability to upload files,
however, when you say bi-directional, do you mean this in an automated
sense, or are you saying the user would upload a file, and then perhaps the
user would come back an hour later and want to down load something?

If you need to automate the file transfer, you could use the Indy Project.
It's got great support, and it's open source. It includes an FTP client. If
it doesn't need to be automated, you could just have a Web form with a file
uploader, and then a page where the user could view the links to available
files to download them.

Unless you know of some other way of communicating with the internet, I
would make use of that Ethernet card.

It's possible to just dink with ASP.NET and figure it out, but I highly
recommend taht you get a book or some sort of guide, it will make your life
sooooo much easier. I suggest "ASP.NET Unleashed", if you want a book that
covers _everything_ (1000+ pages). However, the coding style and conventions
leaves something to be desired.

Also, if you didn't design your original application in some sort of layered
or n-tier pattern, then you may find your self re-working some code.

HTH,
Jeremy
 
Hi,

The most recent (April) issue of Visual Studio Magazine has an article
titled, "Transfer Files with .NET." This covers both FTP and HTTP Post.

Naturally, you do need a connect to the Internet. You do not have to employ
ASP .NET, though. A Rich Client (Windows Forms) application will work.

There are .NET controls available on web, that do most of the grunt-work for
you. For example Zane Thomas has some at http://www.abderaware.com/.

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 3rd
Edition ISBN 1-890422-27-4 (391 pages) published February 2002.
 
Lance,

Thanks for the link.

Brad
hardware via the PCI bus. We've written the app using VB.Net; but,
the client has asked for remote access to data and remote control of the
hardware config. parameters via web pages. This will include
transfers of large data files (mbytes- I looked around,
native FTP capability in .Net.) The PC has an
connected to a network, although it could
hosting capability to come form the
at ASP.Net, but I'm not sure if this is the correct
appreciate any suggestions or pointers to other resources
come up with a solution.

Try IP*Works! .Net Edition. It includes fully
managed components, all written in C#. There are currently over 40 different
internet protocols there including FTP. ASP.Net demos (yes, FTP) are included
as well as Windows application demos in both C# and VB.Net. You can download
the trial at www.nsoftware.com/download/. If you have any questions feel free
to ask.

Regards,
Lance R.
/n software
http://www.nsoftware.com/

-
Click to expand...
 
Jeremy,

Thanks for the response and the book reference. Fortunately, I did develop
the original code using a layered model. The FTP interface doesn't need to
be automated, but I will tie it to a specific request by the user - like a
blind FTP request where you must know the name of the file in order to
retrieve it. The user will be in a "working" session via a web interface,
download a file, then make parameter changes on the web page that ripple
back to the device.

Brad
 
Back
Top