By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,986 Members | 1,944 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,986 IT Pros & Developers. It's quick & easy.

Further framework stupidity

P: n/a
Nak
Hi there,

Please consider this string of events, 'A' being a client and 'B' being
me,

A) Your application doesn't work....

B) Please insure the correct version of the framework is
installed, that being 1.0 needs service pack 3 and 1.1 needs service pack 1.

A) 1.1 has service pack 1 installed, 1.0 has service pack 2
installed, why doesn't it work?

B) The application will use 1.0 if it is installed, otherwise it
will use 1.1, therefore you need service pack 3 installed for 1.0.

Is it just me or does this seem to confuse users? My understanding is
that I can configure the applications config file to force it to use 1.1,
but does anyone have any examples of this being done during deployment
within a setup project?

I'm not asking about framework detection here, just the ability to give
the application an opportuinity of selecting the framework itself. Maybe if
this is done during the first lines of the application?

Anyway, suggestions would be cool and appeciated.

Nick.
Nov 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
You can specify the target framework in the application configuration file.

<?xml version ="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v1.1.4322" />
</startup>
</configuration>

For full details check out "Targeting a .NET Framework Version"
http://msdn.microsoft.com/library/de...orkversion.asp

--
Rob Windsor [MVP-VB]
G6 Consulting
Toronto, Canada
http://msmvps.com/windsor/


"Nak" <a@a.com> wrote in message
news:uy**************@TK2MSFTNGP09.phx.gbl...
Hi there,

Please consider this string of events, 'A' being a client and 'B' being
me,

A) Your application doesn't work....

B) Please insure the correct version of the framework is
installed, that being 1.0 needs service pack 3 and 1.1 needs service pack
1.

A) 1.1 has service pack 1 installed, 1.0 has service pack 2
installed, why doesn't it work?

B) The application will use 1.0 if it is installed, otherwise it
will use 1.1, therefore you need service pack 3 installed for 1.0.

Is it just me or does this seem to confuse users? My understanding is
that I can configure the applications config file to force it to use 1.1,
but does anyone have any examples of this being done during deployment
within a setup project?

I'm not asking about framework detection here, just the ability to give
the application an opportuinity of selecting the framework itself. Maybe
if this is done during the first lines of the application?

Anyway, suggestions would be cool and appeciated.

Nick.

Nov 21 '05 #2

P: n/a
Nak
Hi there,

Excellent, I suppose now what I have to do is generate this config file
when the app is first run to determin which framework to use. Thanks for
your help.

Nick.

"Rob Windsor [MVP]" <rw******@NO.MORE.SPAM.bigfoot.com> wrote in message
news:ep**************@TK2MSFTNGP12.phx.gbl...
You can specify the target framework in the application configuration
file.

<?xml version ="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v1.1.4322" />
</startup>
</configuration>

For full details check out "Targeting a .NET Framework Version"
http://msdn.microsoft.com/library/de...orkversion.asp

--
Rob Windsor [MVP-VB]
G6 Consulting
Toronto, Canada
http://msmvps.com/windsor/


"Nak" <a@a.com> wrote in message
news:uy**************@TK2MSFTNGP09.phx.gbl...
Hi there,

Please consider this string of events, 'A' being a client and 'B'
being me,

A) Your application doesn't work....

B) Please insure the correct version of the framework is
installed, that being 1.0 needs service pack 3 and 1.1 needs service pack
1.

A) 1.1 has service pack 1 installed, 1.0 has service pack 2
installed, why doesn't it work?

B) The application will use 1.0 if it is installed, otherwise
it will use 1.1, therefore you need service pack 3 installed for 1.0.

Is it just me or does this seem to confuse users? My understanding is
that I can configure the applications config file to force it to use 1.1,
but does anyone have any examples of this being done during deployment
within a setup project?

I'm not asking about framework detection here, just the ability to
give the application an opportuinity of selecting the framework itself.
Maybe if this is done during the first lines of the application?

Anyway, suggestions would be cool and appeciated.

Nick.


Nov 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.