Targetting 1.1 with VS2005

[Udi]

Hi,
I'd like to use VS2005 but to target my application to run on 1.1.
I tried changing the csproj file to include the line -
<Import Project="$(ProgramFiles)\Everett\Everett.targets" />
(I have the everett.targets file on that location) but it doesn't work.
When I execute my app, it asks for .NET 2.0.

How do I make it run with framework 1.1?
Thanks,
Udi

[Marwan Tarek]

Hello Udi,

try to use MSBee
http://www.gotdotnet.com/codegallery...a-9b8d00970371
MSBee uses MSBuild which is builtin VS 2005 to traget .net frame 1.1

Marwan Tarek
http://www.sharepointblogs.com/marwantarek/

Hi,
I'd like to use VS2005 but to target my application to run on 1.1.
I tried changing the csproj file to include the line -
<Import Project="$(ProgramFiles)\Everett\Everett.targets" />
(I have the everett.targets file on that location) but it doesn't
work.
When I execute my app, it asks for .NET 2.0.

How do I make it run with framework 1.1?
Thanks,
Udi

[Udi]

Hi Marwan,
Thanks for your help, it works with a simple application, however, when
I'm trying it on the real application it fails to build it,
saying "Metadata file 'C:\...Debug\Interop.CWUIControlsLib.dll' could
not be opened -- 'Version 2.0 is not a compatible version.'
(this is a third party dll.)

Any ideas what's going on?
(of course with VS2003 everything worked fine)
Yhanks,
Udi.

[Udi]

BTW, Everything worked fine even with 2005 targeting to 2.0 and not to
1.1
Thanks!

[Marwan Tarek]

Hello Udi,

is your third party dll built with .net framework 1.1 or 2.0

Marwan Tarek
http://www.sharepointblogs.com/marwantarek/

Hi Marwan,
Thanks for your help, it works with a simple application, however,
when
I'm trying it on the real application it fails to build it,
saying "Metadata file 'C:\...Debug\Interop.CWUIControlsLib.dll' could
not be opened -- 'Version 2.0 is not a compatible version.'
(this is a third party dll.)
Any ideas what's going on?
(of course with VS2003 everything worked fine)
Yhanks,
Udi.

[Udi]

Thanks again Marwan,
1.1.

As I said, I'm currently using it on 1.1. Still, when I've ported my
project to 2.0 while targeting it to 2.0 (it's a testing environment)
it works fine as well.
The problem occurs when targeting it to 1.1 with VS2005.

[Udi]

Marwan, Thanks again.
it was built with 1.1.
I'm currently using it with 2003. But as I said, when building the same
dll with 2005 and targeting to 2.0 it works fine as well.
The problem happens only when building my proj with 2005 while
targeting to 1.1.
Udi.