Hola, Alex.

>>Is it possible to use VS2005 to write Framework 1.1 components?
>>
>>I have a project that requires using framework 1.1 (it dependes on several components that I have to extend but I can't rebuild on 2.0 for licensing issues). Can I make my team work on VS 2005 but force C# and the libraries to be kept at 1.1 level?
>>
>>What I'd love is to be able to use the new IDE instead of having to stick with VS 2003.
>>
>>Any hint would be appreciated. If anyone our there actually DID this, then even better!
>
>
>It's not that easy but possible, though I'm not sure I'd recommend it.
>
>I did a project a couple of months ago (ASP.NET-C#) that had to go out in 1.1 (as VS 2005 was in Beta). I did not use new controls (like GridView). There were a few warning of 'deprecated' controls and methods that I ignored. Once most of the project was written, I switched to VS2003 for compilation and fixing the few incompatibilities. It was a small project so it was possible. I would not recommend it for anything big or complex as it is different. I'd just use VS 2003 for old projects and VS 2005 for anything new in my shop.

No problem here with the build process. I'll use MS Build to do it automatically and continually in a separate machine. What I really care about is being able to avoid using any framework 2.0 libraries or C# 2.0 features while writing the code. I guess this is the most complex issue.

Thanks a lot,