use/reuse of intranet business dlls by asp.net apps

[=?Utf-8?B?bnV1dHV1ZG5ldA==?=]

We want to use allready written C sharp programs for our asp.net
applications. The idea is that we write a program ONCE and use this same
EXACT logic for our internet apps. Everything will run on the same server but
we will have two types of clients 1. web based, 2. intranet based. Is this
possible? If so, what is it called in Microsoft speak? How to links would be
appreciated.
--
cheers,
nuutuudnet

[Alexey Smirnov]

On Sep 10, 2:20 pm, nuutuudnet <[e-mail]:

We want to use allready written C sharp programs for our asp.net
applications. The idea is that we write a program ONCE and use this same
EXACT logic for our internet apps. Everything will run on the same server but
we will have two types of clients 1. web based, 2. intranet based. Is this
possible? If so, what is it called in Microsoft speak? How to links would be
appreciated.

You can identify the type of user by IP address, for example, if an
address starting with 10.*, it's an internal network IP.

if (Request.ServerVariables ["REMOTE_ADDR"].indexOf("10.") == 0) {
.....

[Aidy]

Look into "remoting" or "web services" as two possible solutions. Maybe web
services would be the better solution. You expose your code via web methods
and both the website and applications use the web service.

"nuutuudnet" <fa*******@here.dewrote in message
news:76**********************************@microsof t.com...

We want to use allready written C sharp programs for our asp.net
applications. The idea is that we write a program ONCE and use this same
EXACT logic for our internet apps. Everything will run on the same server
but
we will have two types of clients 1. web based, 2. intranet based. Is this
possible? If so, what is it called in Microsoft speak? How to links would
be
appreciated.
--
cheers,
nuutuudnet

[=?Utf-8?B?bnV1dHV1ZG5ldA==?=]

I do not want to reprogram. I want to use existing C#
Objekts/methods/programs in my internet app.
--
cheers,
nuutuudnet
"Alexey Smirnov" wrote:

On Sep 10, 2:20 pm, nuutuudnet <[e-mail]:

We want to use allready written C sharp programs for our asp.net
applications. The idea is that we write a program ONCE and use this same
EXACT logic for our internet apps. Everything will run on the same server but
we will have two types of clients 1. web based, 2. intranet based. Is this
possible? If so, what is it called in Microsoft speak? How to links would be
appreciated.

You can identify the type of user by IP address, for example, if an
address starting with 10.*, it's an internal network IP.

if (Request.ServerVariables ["REMOTE_ADDR"].indexOf("10.") == 0) {
.....

[=?Utf-8?B?bnV1dHV1ZG5ldA==?=]

We have heard of these two things but they are not exactly what we want. We
understand remoting to be a sort of physical shoving back and forth of data
between two apps. And Web services do not also fit our scenario. We have
existing allready written C# logic. We want asp.net (OR our internet
programs) to simply be able to use this C# logic. We are simply trying to
avoid the work of building two apps, one for web and one for intranet.
--
cheers,
nuutuudnet
"Aidy" wrote:

Look into "remoting" or "web services" as two possible solutions. Maybe web
services would be the better solution. You expose your code via web methods
and both the website and applications use the web service.

"nuutuudnet" <fa*******@here.dewrote in message
news:76**********************************@microsof t.com...

We want to use allready written C sharp programs for our asp.net
applications. The idea is that we write a program ONCE and use this same
EXACT logic for our internet apps. Everything will run on the same server
but
we will have two types of clients 1. web based, 2. intranet based. Is this
possible? If so, what is it called in Microsoft speak? How to links would
be
appreciated.
--
cheers,
nuutuudnet

[Aidy]

Then just reference the dlls from your web project and you should be able to
use them as normal.

"nuutuudnet" <fa*******@here.dewrote in message
news:75**********************************@microsof t.com...

We have heard of these two things but they are not exactly what we want.
We
understand remoting to be a sort of physical shoving back and forth of
data
between two apps. And Web services do not also fit our scenario. We have
existing allready written C# logic. We want asp.net (OR our internet
programs) to simply be able to use this C# logic. We are simply trying to
avoid the work of building two apps, one for web and one for intranet.
--
cheers,
nuutuudnet
"Aidy" wrote:

>Look into "remoting" or "web services" as two possible solutions. Maybe
web
services would be the better solution. You expose your code via web
methods
and both the website and applications use the web service.

"nuutuudnet" <fa*******@here.dewrote in message
news:76**********************************@microso ft.com...

We want to use allready written C sharp programs for our asp.net
applications. The idea is that we write a program ONCE and use this
same
EXACT logic for our internet apps. Everything will run on the same
server
but
we will have two types of clients 1. web based, 2. intranet based. Is
this
possible? If so, what is it called in Microsoft speak? How to links
would
be
appreciated.
--
cheers,
nuutuudnet

[Alexey Smirnov]

On Sep 10, 4:16 pm, nuutuudnet <[e-mail]:

We have heard of these two things but they are not exactly what we want. We
understand remoting to be a sort of physical shoving back and forth of data
between two apps. And Web services do not also fit our scenario. We have
existing allready written C# logic. We want asp.net (OR our internet
programs) to simply be able to use this C# logic. We are simply trying to
avoid the work of building two apps, one for web and one for intranet.
--
cheers,
nuutuudnet

You wrote:

Everything will run on the same server

Does it mean you will have the same application with two kind of
users, or you will have two applications: one for internet and one for
intranet? I don't see any point to build a web service here

[=?Utf-8?B?bnV1dHV1ZG5ldA==?=]

Exactly, I have web users and in house intranet users. But we want both users
to make database changes in exactly and precisely the same way as far as
types, as far as date conversions, whatever. We hope with dotnet to be able
to write one program here in house, compile it, put one on the internet and
one local (both actually physically in the same machine) we'll write a GUI in
c# for in-house and an asp.net (??) GUI for the web but the kernal business
logic is exactly and precisely the same c#. I am hoping that someone could
tell me that it is indeed as simple as Aidy says just refrencing the methods,
classes and variables.
--
cheers,
nuutuudnet
"Alexey Smirnov" wrote:

On Sep 10, 4:16 pm, nuutuudnet <[e-mail]:

We have heard of these two things but they are not exactly what we want. We
understand remoting to be a sort of physical shoving back and forth of data
between two apps. And Web services do not also fit our scenario. We have
existing allready written C# logic. We want asp.net (OR our internet
programs) to simply be able to use this C# logic. We are simply trying to
avoid the work of building two apps, one for web and one for intranet.
--
cheers,
nuutuudnet

You wrote:

Everything will run on the same server

Does it mean you will have the same application with two kind of
users, or you will have two applications: one for internet and one for
intranet? I don't see any point to build a web service here

[Alexey Smirnov]

On Sep 11, 9:26 am, nuutuudnet <[e-mail]:

Exactly, I have web users and in house intranet users. But we want both users
to make database changes in exactly and precisely the same way as far as
types, as far as date conversions, whatever. We hope with dotnet to be able
to write one program here in house, compile it, put one on the internet and
one local (both actually physically in the same machine) we'll write a GUI in
c# for in-house and an asp.net (??) GUI for the web but the kernal business
logic is exactly and precisely the same c#. I am hoping that someone could
tell me that it is indeed as simple as Aidy says just refrencing the methods,
classes and variables.
--
cheers,
nuutuudnet

"Alexey Smirnov" wrote:

On Sep 10, 4:16 pm, nuutuudnet <[e-mail]:

We have heard of these two things but they are not exactly what we want. We
understand remoting to be a sort of physical shoving back and forth of data
between two apps. And Web services do not also fit our scenario. We have
existing allready written C# logic. We want asp.net (OR our internet
programs) to simply be able to use this C# logic. We are simply trying to
avoid the work of building two apps, one for web and one for intranet.
--
cheers,
nuutuudnet

You wrote:

Everything will run on the same server

Does it mean you will have the same application with two kind of
users, or you will have two applications: one for internet and one for
intranet? I don't see any point to build a web service here- Hide quoted text -

- Show quoted text -

What I ment, is that you can setup one application on one server for
all users. You didn't say that it has to be different (intranet/
internet), so why don't you make your existing intranet ASP.NET
application available in the internet?

[Alexey Smirnov]

On Sep 11, 3:36 pm, nuutuudnet <[e-mail]:

That is a very deep philosophical question :-) One reason amoung many is that
the system started out with the office app and then they added an internet
portal later. They expanded little by little. They want to stay with the same
model. Do you agree Smirnov with Aidy that the programs can simply be
referenced from asp.net? I am about to go out and buy a book but the choices
are overwelming and I just do not know which would fit my situation. One
thing is clear we will not be doing Web Services. We will only resort to
remoting if we cannot use/reuse ( or in this case reference) the c# in our
asp.net programs.

Well, the point is that in any case you will have two applications.
And if idea was to reduce the cost of development then it doesn't
really help, I think. If I were you, I would either go for one web
client for everyone, or for a Smart Client (for Windows users,
deployed over the web).

http://en.wikipedia.org/wiki/ClickOnce
http://msdn.microsoft.com/msdnmag/is.../05/ClickOnce/