.NET framework apps in Terminal Server

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

ranga - 04 Jan 2005 16:05 GMT

hello

>> are there any issues with running .NET framework apps written in vb.net/c# in a terminal server environment?. If so, any pointers would help

thanks
ranga

Reply to this Message

Jonathan - 04 Jan 2005 16:35 GMT

Hi, what kind of issues did you encounter ?

> hello
>
[quoted text clipped - 4 lines]
> thanks
> ranga

Reply to this Message

ranga - 04 Jan 2005 16:51 GMT

Jonathan

>> I have not tired it yet -- i was trying to find out from this group if

there
are any known issues.

>> I have had no problem running vb6 apps in a Terminal Server. While I do not

expect any isuses with .NET framework apps in Terminal Servers, I am trying
to find out if there are any - just in case !. I do not see any references to
this subject in the web.

thanks
ranga

> Hi, what kind of issues did you encounter ?
> > hello
[quoted text clipped - 5 lines]
> > thanks
> > ranga

Reply to this Message

Shariq - 04 Jan 2005 17:03 GMT

I have been running VB.Net applications successfully on multiple Terminal
Servers for years and haven't encountered any problems so far.

> hello
>
> >> are there any issues with running .NET framework apps written in vb.net/c# in a terminal server environment?. If so, any pointers would help
>
> thanks
> ranga

Reply to this Message

ranga - 04 Jan 2005 20:57 GMT

thanks shariq - a quick question on this subject

>> after i configure a 2003 server as a terminal server, should i install the .NET framework from Add/Remove programs to make it available to multi-users?

> I have been running VB.Net applications successfully on multiple Terminal
> Servers for years and haven't encountered any problems so far.
[quoted text clipped - 5 lines]
> > thanks
> > ranga

Reply to this Message

Cletus Van Damme - 05 Jan 2005 04:50 GMT

No, you should not need to re-install the framework. If it's already there,
it should be available to all users.

Cletus

> thanks shariq - a quick question on this subject
>
[quoted text clipped - 13 lines]
>> > thanks
>> > ranga

Reply to this Message

ranga - 05 Jan 2005 15:44 GMT

Cletus

>> When you install windows 2003 server from scratch, I am not sure if you

get .NET Framework 1.1. Then when you configure it as a Terminal Server,
still you don't get the framework. It is only when you configure it as an
application server that IIS and ASP.NET are installed and you get the
framework now.

>> but then, it is not best practice to have IIS on a terminal server. The

best practice to build a TS is to install windows 2003/2000 first and
then install TS and then install the framework from the redistributable
package.

My original question was - do i need to install this framework from add/remove
programs so that it is available to all users .. i guess it is a moot
question bcos once
you have a TS, when you install any app in it, TS will warn you to install
it in
add/remove programs. But I asked the moot question anway since crazy
installation
issues happen in the MS world and wanted to see if anyone has experienced
anything quirky

>> another issue will arise when .NET framework 2.0 is released. Then, in this case, if the TS has framework 1.1, then framework 2.0 has to be installed, from

the redistributable package, manually thru the add/remove program

thanks
ranga

> No, you should not need to re-install the framework. If it's already there,
> it should be available to all users.
[quoted text clipped - 18 lines]
> >> > thanks
> >> > ranga

Reply to this Message

.NET framework apps in Terminal Server

Free Magazines