Why can the project whose target FW is 2 use 3.0/3.5 assemblies in VS2008? RRS feed

  • Question

  • Hi, thanks for reading my post.

    I updated a dll in a VS2008 project whose target FW is .NET FW 2.0.

    The updated dll depends on WindowsBase.dll and System.Core.dll.

    Then, the updated project can run correctly. I can find WindowsBase.dll and System.Core.dll in Modules window of VS2008.

    Is this a correct behavior of VS2008? How can I forbidden VS2008 to use 3.0/3.5 assemblies when target FW is 2.0?

    Friday, May 6, 2011 2:24 AM

All replies


    Hi Noel,


    Firstly, you can see this link which describes "What's New in .NET Framework".


    Actually, FW 3.0 adds new features of WCF&WPF&WF&WCS, FW3.5 adds LinQ. But both FW 2.0 and FW 3.0 use the CLR 2.0. That is why project can load updated assembly which targets FW 3.0 successfully. If you don't use new features of FW 3.5, you can change updated assembly to target FW 2.0 so that you won't get the warning.


    Have  a nice day!

    Paul Zhou [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Proposed as answer by Paul Zhou Tuesday, May 24, 2011 6:13 AM
    Wednesday, May 11, 2011 7:49 AM