none
Project file contains ToolsVersion="4.0", which is not supported by this version of MSBuild. Treating the project as if it had ToolsVersion="3.5".

    Question

  • I copied some projects from VS 2010 and later incorporated them in a 2008 project. Now I get this warning. I can get around this warning by editing the project file with notepad and replacing 4.0 with 3.5. Is there a way to replace the ToolsVersion from within VS?

    Kevin

    Saturday, August 28, 2010 10:41 PM

Answers

  • Hi Kevin,

    Do you have any concern of this method?

    Downgrade conversion is not supported in the VS IDE, as the old version may have no idea of the new things happened in the new version. But for some specific case, editing project file(s) manually is the way.

    Thanks.


    Figo Fei
    MSDN Subscriber Support in Forum
    If you have any feedback on our support, please contact msdnmg@microsoft.com 


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    • Marked as answer by KevinBurton Monday, August 30, 2010 2:44 PM
    Monday, August 30, 2010 5:39 AM

All replies

  • Hi Kevin,

    Do you have any concern of this method?

    Downgrade conversion is not supported in the VS IDE, as the old version may have no idea of the new things happened in the new version. But for some specific case, editing project file(s) manually is the way.

    Thanks.


    Figo Fei
    MSDN Subscriber Support in Forum
    If you have any feedback on our support, please contact msdnmg@microsoft.com 


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    • Marked as answer by KevinBurton Monday, August 30, 2010 2:44 PM
    Monday, August 30, 2010 5:39 AM
  • Thank you. I was afraind of that. But it isn't that big of a deal.

    I developed an application using the latest (VS 2010, .NET 4.0) but there are some users that like the app but don't have .NET 4.0 and because of policies can't install it. So the only way I could provide them with these applications was to "downgrade". And for the functions that I used there was little or no difference in using .NET 3.5 and .NET 4.0.

    Kevin

    Monday, August 30, 2010 2:44 PM
  • Hi Kevin,

    Please note that you can also build for .Net 3.5, .Net 3.0 and .Net 2.0 using Visual Studio 2010. So there really is no need to go back to VS 2008 for these customers.

     

    Regards,

    Michael


    ----- http://jepsonsblog.blogspot.com -----
    Thursday, December 30, 2010 8:56 AM
  • The problem was that I was using 2010 and I want other users who have not installed 2010 also to be able to use this project. They have not upgraded to 2010 yet.

    Kevin

     


    Kevin Burton
    Thursday, December 30, 2010 3:06 PM
  • Hello,

    I am also facing this issue. Every time I try to build my solution there comes an error in output window "Project file contains ToolsVersion="4.0", which is not supported by this version of MSBuild. Treating the project as if it had ToolsVersion="3.5"."

    Also I dont get ToolVersion as 4.0 in any of the project cs file. I have been trying to resolve it since long. Any help is very much appreciated.

    Thanks


    Every day its a new learning. Keep Learning!!
    If this post answers your question, please click Mark As Answer . If this post is helpful please click Mark as Helpful

    Tuesday, October 30, 2012 7:53 AM
  • Hi Tiya,

    This ToolsVersion is not in any of the .cs files, it's in the project files (.csproj). Edit the files themselves, easiest is using Notepad or Notepad++. You can also right click them and choose to edit them. Either way, you should edit the actual XML code that is in these .csproj files.


    ----- http://jepsonsblog.blogspot.com -----

    Tuesday, October 30, 2012 12:02 PM