Hello tcw,
Yep.
read there http://dotnetdebug.blogspot.com/2006/01/running-net-20-and-11-side-by-side.html
---
WBR, Michael Nemtsev [C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/
"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
t> Is it safe to use a third party's C# library which was built with
t> .NET 1.1 in my .NET 2.0 projecct? Thank you in advance.
t>
t> -tcw
t>
Cowboy (Gregory A. Beamer) - 30 Mar 2007 15:14 GMT
You realize this link does not really apply, right? :-)

Signature
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
*********************************************
Think outside the box!
*********************************************
> Hello tcw,
>
[quoted text clipped - 13 lines]
> t> t> -tcw
> t>
.NET 2.0 is backwards compatible with 1.1, so you should be able to stick
any 1.1 assembly into your project and run it without problems. I say
"should" as there is always a potential that somethign will not work. If you
have the option of a 2.0 assembly, I would choose that first. If not, be a
bit paranoid and test, test, test. This is good advice, no matter what you
are building.

Signature
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
*********************************************
Think outside the box!
*********************************************
> Is it safe to use a third party's C# library which was built with .NET 1.1
> in my .NET 2.0 projecct? Thank you in advance.
>
> -tcw
tcw - 30 Mar 2007 18:56 GMT
Thanks a lot, gentlemen.
-tcw
> .NET 2.0 is backwards compatible with 1.1, so you should be able to stick
> any 1.1 assembly into your project and run it without problems. I say
[quoted text clipped - 6 lines]
>>
>> -tcw