Visual Basic .NET Compiler

[William Foster]

Good evening all,

I am running Microsoft Visual Studio 2005, when I compile my programs
with this software it has been compiled by the .Net Framework version 2.
Unfortunately I need my program to run on .Net Framework version 1; does
anyone know if there is an option to make a complied program backwards
compatiable.

Any assistance you may be able to provide would be greatly appreciated.

Yours sincerely,

William Foster

 

[Guest]

i know it is possible the other way around

and for sure i would be surprised if it is even possible what you want

i guess the only 2 things you can do is

1. upgrade your users to framework 2.0 ( write an installer for that )
2. switch back to VS.Net 2003 ( where you have the possibility to support
1.0 and 1.1 versions of the framework )

hth

Michel Posseth [MCP]

 

[Jared Parsons [MSFT]]

Hello William,

Good evening all,

I am running Microsoft Visual Studio 2005, when I compile my programs
with this software it has been compiled by the .Net Framework version
2. Unfortunately I need my program to run on .Net Framework version 1;
does anyone know if there is an option to make a complied program
backwards compatiable.

AFAIK, it's not possible to do this. The best solution I've found is to
develop with VS 2005 but actually build and deploy via VS2003. That allows
you take advantage of the new IDE features (but not the language ones unfortunately.).

 

[Ahmed]

I don't think this is a good idea. In VS 2005 there are some controls
not available in VS 2003. There also few methods become obsolete and
been replaced by new methods which are not available in vs 2003.

Just my 2 c's

Hello William,

Good evening all,

I am running Microsoft Visual Studio 2005, when I compile my programs
with this software it has been compiled by the .Net Framework version
2. Unfortunately I need my program to run on .Net Framework version 1;
does anyone know if there is an option to make a complied program
backwards compatiable.

AFAIK, it's not possible to do this. The best solution I've found is to
develop with VS 2005 but actually build and deploy via VS2003. That allows
you take advantage of the new IDE features (but not the language ones unfortunately.).


--
Jared Parsons [MSFT]
(e-mail address removed)
All opinions are my own. All content is provided "AS IS" with no warranties,
and confers no rights.

 

[Jared Parsons [MSFT]]

Hello Ahmed,

I don't think this is a good idea. In VS 2005 there are some controls
not available in VS 2003. There also few methods become obsolete and
been replaced by new methods which are not available in vs 2003.

I agree it's not an optimal idea. It's too easy to start using constructs
or libraries just not available in vs2003. But at least when you recompile
in 2003 you'll catch these errors. I think it' more of a question of whether
or not you think the improved IDE is compelling enough in itself to use.

 

[William Foster]

Thanks all for your feedback, unfortunately I think I will have to go
with the compile in VS2003 option. The program I am doing is one of
those ones that assist a few people, but it is not improtant enough for
my IT Department to release the new .NET platform (Darn them and there
deployment rules and associated costs).

The only annoying thing now is that I have to find another workstation
and sit there for a couple of hours install all of those CD's.

Thanks once again !

Yours sincerely,

William Foster