VB: How can a .NET 2.0 application be deployed to be able to run on lower .NET versions?

Question

0.00/5 (No votes)

See more:

VB: How can a .NET 2.0 application be deployed to be able to run on lower .NET versions? Please guide me .NET applications deployment techniques for less than .NET 2.0 comparability.

Posted 13-Mar-11 1:29am

Muhamamd Islam

Updated 13-Mar-11 1:31am

v2

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

#realJSOP · Answer 1 · 2011-03-13T01:31:00

Solution 1

If your app needs .Net 2.0, there's NO WAY it will run unless .Net 2.0 (or higher) is installed on the user's system.

Posted 13-Mar-11 1:31am

#realJSOP

Comments

Muhamamd Islam 13-Mar-11 8:31am

But I want to set my application for .NET 1.0. I am using Visual Studio 2005PE and I could not find options how to set mp application platform as .NET lower than 2.0.

#realJSOP 13-Mar-11 8:51am

VS2005 cannot create .Net 1.n apps. Period. You're going to have to downgrade your compiler if that's what you want. IMHO, that's a pointless exercise because a) .Net 2 is leaps and bounds better then 1.n, and b) it's ubiquitous. If you crate a setup project for your app, it will prompt the user to install .Net 2.0 automatically. No worries.

Muhamamd Islam 13-Mar-11 14:11pm

Dear John Simmons:
it's ok that .NET 2 is better, but here we have many slow (P-2, P-3) computers that is why I want to find some downward solution. If any please tell me.
sorry for late comments... I was out for some urgent work...

Sergey Alexandrovich Kryukov 13-Mar-11 16:10pm

Some downward solution? Please see my recommendation in my Answer.

John, 5 for yours.
--SA

Sergey Alexandrovich Kryukov · Answer 2 · 2011-03-13T10:09:00

In my opinion, running Framework v.2.0 does make sense, but not anything prior to that (really good) version.
If you have customers who only have .NET Framework versions prior to v.2.0 and not willing to install anything else, you should consider the following:

1) Deploy Framework v.2.0 (or later) as a part of installation;
2) Claim that Framework v.2.0 is a prerequisite for you product and give up the customers not willing to complain (which is perfectly legitimate option: after all, you don't support VAX VMS or MS-DOS. .NET is just on of the platforms, if you require it, do require).
3) Consider the product in native Windows code. Good alternative to .NET is Delphi for native Windows, major predecessor of .NET.

—SA

**Dalek Dave** · Answer 3 · 2011-03-13T10:55:00

Solution 3

As others have pointed out, it will not work.
You would need to force the upgrade to the higher version.

Posted 13-Mar-11 10:55am

Dalek Dave

Comments

Sergey Alexandrovich Kryukov 13-Mar-11 17:07pm

Thanks for supporting my view.
--SA