Compartir a través de


using .net framework 2.0 from VS.Net 2003

Ah yes...everyone once in a while (usually after I start feeling like I know what I'm doing) a problem like this show's itself to put me in my place.  hehehe...

one would think that it would be a simple task to switch over from using .net framework 1.1 to 2.0, but it has proven to be a somewhat difficult task.  Been looking all morning for an answer to how to do this, and aparently I'm either the only person in the world trying it, or the only one who can't figure it out.  hehehe.

Specifically what I'm trying today is to get my teams project to build using the 2.0 framework...so I thought it would be a simple matter of replacing my references with the 2.0 versions, but I keep getting an error saying that it's not a valid .dll or COM object.  Hmmmmm...

Can anyone point me in the right direction for some answers...like I said, I've been searching all morning, but I'm not exactly sure on what to search on, so that could be the problem too...hehehe.  Anyway, any help would be greatly appricated.  :)

Comments

  • Anonymous
    July 15, 2005
    The comment has been removed
  • Anonymous
    July 15, 2005
    The comment has been removed
  • Anonymous
    July 15, 2005
    To get my applications to compile on multiple versions of the .NET Framework, I use NAnt. I write a build script with a "portability" target that compiles my solution for all .NET framework versions that I want to support. If your code uses a feature that is not supported by the target .NET framework, you will get errors that you will need to fix and hence you will eventually achieve portability.