how to force a .net application to use .net 2.0 ?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Daniel - 21 Sep 2007 21:53 GMT

how to force a .net application to use .net 2.0 ?
this windows service is about 4 years old and im pretty sure is using .net
1.x runtime. Is there soem setting in the installer that says to use .net
2.0 instead of .net 1.0? this windows service is developed in visual studio
2002

Reply to this Message

Mel - 21 Sep 2007 22:12 GMT

Recompile the program using VS2005

> how to force a .net application to use .net 2.0 ?
> this windows service is about 4 years old and im pretty sure is using
> .net 1.x runtime. Is there soem setting in the installer that says to use
> .net 2.0 instead of .net 1.0? this windows service is developed in visual
> studio 2002

Reply to this Message

Som Nath Shukla - 22 Sep 2007 08:16 GMT

Dont worry it will work with .net 2.0.
if a system have .net 1.0/1.0/2.0 framework installed .then it will always
run with latest version .if u force to run it with .net 2.0 then syatem that
does not have .net 2.0 installed wil not able to run this application.
even if u want to force it to run only .net 2.0. .
go web.config and
and change the setting in
<?xml version = "1.0"?>
<configuration>
<startup>
<supportedRuntime version="v2.0.50727/>
</startup>
</configuration>

> Recompile the program using VS2005
>
[quoted text clipped - 3 lines]
> > .net 2.0 instead of .net 1.0? this windows service is developed in visual
> > studio 2002

Reply to this Message

Doug Semler - 24 Sep 2007 13:55 GMT

On Sep 22, 3:16 am, Som Nath Shukla
<SomNathShu...@discussions.microsoft.com> wrote:

> Dont worry it will work with .net 2.0.
> if a system have .net 1.0/1.0/2.0 framework installed .then it will always
[quoted text clipped - 9 lines]
> </startup>
> </configuration>

Caution: Saying it will RUN under CLR 2 is NOT the same as saying it
will WORK under CLR 2!

I believe that there are sufficiently subtle differences, especially
in the platform invoke layer and cross thread control access that may
cause unexpected problems if the code is not regression tested
completely. And it's not web.config, it's exename.exe.config for a
windows service...

Reply to this Message

Nicholas Paldino [.NET/C# MVP] - 21 Sep 2007 22:16 GMT

Daniel,

What is the impetus for changing the runtime? If it works, why change
it?

Signature

- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com

Reply to this Message

Daniel - 21 Sep 2007 23:55 GMT

anything before .net 2.0 does not support extended memory servers and 64 gig
server etc. even if you have the new windows serve with 64 gigs ram, .net
1.x apps have an upper bound of 2 gigs, and an even smaller upper bound of
memory per object. with memory fragmentation, can see out of memory even
earlier. its a waste of money to get a new windows server with 64 gigs ram
and use .net 1.x

> Daniel,
>
[quoted text clipped - 6 lines]
>> .net 2.0 instead of .net 1.0? this windows service is developed in visual
>> studio 2002

Reply to this Message

Daniel - 21 Sep 2007 23:58 GMT

so regretfully many of us will have to upgrade to 2.0 when we hit memory
issues with 1.x :) :) :)

> Daniel,
>
[quoted text clipped - 6 lines]
>> .net 2.0 instead of .net 1.0? this windows service is developed in visual
>> studio 2002

Reply to this Message

Family Tree Mike - 22 Sep 2007 01:54 GMT

You may find this thread http://www.thescripts.com/forum/thread381325.html
helps.

You seriously have a service which needs objects larger than 2 GB?

I think Mel is right, recommending rebuilding with the latest VS 2005.

> so regretfully many of us will have to upgrade to 2.0 when we hit memory
> issues with 1.x :) :) :)
[quoted text clipped - 9 lines]
> >> .net 2.0 instead of .net 1.0? this windows service is developed in visual
> >> studio 2002

Reply to this Message

Willy Denoyette [MVP] - 22 Sep 2007 14:47 GMT

> You may find this thread http://www.thescripts.com/forum/thread381325.html
> helps.
>
> You seriously have a service which needs objects larger than 2 GB?

No, he doesn't, because no single version of the CLR allows you to create
such large objects anyway.

Willy.

Reply to this Message

Family Tree Mike - 22 Sep 2007 23:30 GMT

I wasn't sure if 3.5 had changed any limits on a 64bit OS. I thought the
poster had implied he needed this.

> > You may find this thread http://www.thescripts.com/forum/thread381325.html
> > helps.
[quoted text clipped - 5 lines]
>
> Willy.

Reply to this Message

Arne Vajhøj - 24 Sep 2007 01:26 GMT

>> You seriously have a service which needs objects larger than 2 GB?
>
> No, he doesn't, because no single version of the CLR allows you to
> create such large objects anyway.

Strictly speaking the fact that it is not possible does not
imply that there is no need.

Arne

Reply to this Message

how to force a .net application to use .net 2.0 ?

Free Magazines