Re: Distributing application to customers?

From: Nick Malik (nickmalik_at_hotmail.nospam.com)
Date: 08/31/04


Date: Tue, 31 Aug 2004 06:15:28 GMT

I assume your application is a Windows Forms app.

If your "customers" are within your corporation, then this is sticky but
possible. If your customers expect to connect to you over the open
internet, I'd advise against connecting to SQL Server over the internet. It
is a little too easy to slam SQL Server with a DoS attack, and we all
remember the SQL virus about a year ago that slammed every SQL Server that
wasn't protected behind an iron-clad firewall. (SQL Slammer, I think it was
called).

No, I'd recommend against allowing your customers to connect across the
internet.

If your customers can connect to your corporate network, or a small secure
portion of it, using RAS, then you can have them dial in. They can either
run the app from their machine or use Terminal Services to run the app from
your machine. The latter is easier for you to deploy but requires users
that won't mind being trained on the intricacies of Terminal Services (e.g.
this usually works for the sales force, not the end customer).

At this point, I'd say your app isn't designed for the use that your
financial planner wants to use it for. I'd suggest adding some web services
on a server that can provide the data to a validated user and can check the
incoming data. Then jigger the app a little to call the data from the web
service instead of the database. This will allow your client-server app to
be run across the Internet, and you can put in a modicum of security by
using HTTPS for the transmission protocol.

That's probably the simplest without rewriting the app to a web app.

HTH,
--- Nick

"Job Lot" <JobLot@discussions.microsoft.com> wrote in message
news:4E49E344-CFAE-494C-ADFE-3758C4F78F2A@microsoft.com...
> I have created an application which creates a financial plan for our
> customers. Now my financial planner wants to distribute a copy of
application
> to our customer with their respective plans and limited functionality. How
> can I can I do this? I am using SQL Server at the back end with several
> stored procedures. I'll have to distribute a copy of .NET Framework and
MDAC
> as well. Moreover I'll have to distribute the application on a CD as it's
not
> possible to fit everything on floppies. Someone please put me in right
> direction to achieve these tasks, as I am doing it for first time.
>
> Thanks
>



Relevant Pages

  • TS and new SQL Server 2000 app
    ... I have no experience w/TS except for occasional connections at my main ... This lab uses XP boxes but connect to the Access app on Windows 2k via ... Terminal Services; they say the performance is much faster because ... When moved to SQL Server, they want the same type of set-up. ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Function name not found
    ... are casual canned-software-only customers? ... I have an app that has just ... certain Reference changes from version to version in MDBs, ... Looking at you Startup function, the first thing I see is a DFirst ...
    (microsoft.public.access.modulesdaovba)
  • Re: VS2003 and WM5.0 Devices
    ... The problem I have is that a customer who has a JasJar has reported that my installer will not install my app at all. ... I still have some customers who have the ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Securing a .NET webapp with ActiveDir and SQL-server?
    ... Or is this done in a separate app? ... I need some SSL in the mix also. ... Each Employee deals with Customers in one or more Regions. ...
    (microsoft.public.dotnet.security)
  • Re: 64-bit - the desaster continues ...
    ... >>> I can't check this myself, but I really wonder how many customers ... MS Excel Server is a new app from Microsoft to be released in 2006. ... Don´t you think it will matter to most Delphi customers by 2007? ...
    (borland.public.delphi.non-technical)

Loading