General Question About Development / Deployment Options

The company I work for is planning a platform change from IBM midrange
platform to Microsoft platform.

We have spent a couple of months looking at many of the available Microsoft
technologies and we are stuck on the decision of whether to develop web or
windows apps.  It seems with web apps you have a lot of security issues and
dealing with session variables and such.  On the other hand windows apps
would be potentially demanding in deployment.  In that the number of machine
s
you might deploy to.

Also, we have been looking at how to deploy .dll files.  We looked at simply
placing them on a shared location on the network.  We also have been looking
at com plus.

I just hoped to get some feed back as to what avenue(s) other people have
gone down.


--
Don

On Mon, 27 Dec 2004 10:57:01 -0800, Don
<Don@discussions.microsoft.com> wrote:

>The company I work for is planning a platform change from IBM midrange
>platform to Microsoft platform.
>
>We have spent a couple of months looking at many of the available Microsoft
>technologies and we are stuck on the decision of whether to develop web or
>windows apps.  It seems with web apps you have a lot of security issues and
>dealing with session variables and such.  On the other hand windows apps
>would be potentially demanding in deployment.  In that the number of machin
es
>you might deploy to.
>
>Also, we have been looking at how to deploy .dll files.  We looked at simpl
y
>placing them on a shared location on the network.  We also have been lookin
g
>at com plus.
>
>I just hoped to get some feed back as to what avenue(s) other people have
>gone down.


if all your users use internet explorer, you can run a .net windows
exe from w/i it (i.e., you can have it both ways).

fwiw, my company also runs its client/server app (1 exe, 12 dlls) from
a network share. deployment is as simple as copying the files from the
test machine to the network share drive - very easy.

Thanks Todd.

In a scenario where you have very limited number of exe and dlls the network
share seems like a really good idea.

This is our scenario:
We will be building a large system.  A warehouse management system with many
forms and many dlls.  An example problem: you have a dll (name = dllA) that
is referenced from 50 other dlls.  A bug is found in dllA and a logic change
is required.  It now has to be recompiled.  Due to this file being
referenced, which creates a copy of the file, you now have to go to all 50 o
f
the other dlls and recompile them and potentially any apps that reference an
y
of the 50 recompiled dlls.



"ToddT" wrote:

> On Mon, 27 Dec 2004 10:57:01 -0800, Don
> <Don@discussions.microsoft.com> wrote:
> 
>
>
> if all your users use internet explorer, you can run a .net windows
> exe from w/i it (i.e., you can have it both ways).
>
> fwiw, my company also runs its client/server app (1 exe, 12 dlls) from
> a network share. deployment is as simple as copying the files from the
> test machine to the network share drive - very easy.
>
>