tag:blogger.com,1999:blog-7949267671212594224.post6708305393130368294..comments2023-07-08T03:55:28.894-07:00Comments on DevScape: NAnt and .Net Framework 3.5JBhttp://www.blogger.com/profile/08085754663631271944noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-7949267671212594224.post-72530030750880811492010-09-30T14:42:54.093-07:002010-09-30T14:42:54.093-07:00I recently ran into the same problem. I sort of k...I recently ran into the same problem. I sort of knew what to do, but you just confirmed what I think should work. I upgraded to the latest Framework 4.0, nant 0.91, and ncontrib. It all worked without needing Visual Studio installed!!Unknownhttps://www.blogger.com/profile/13708170737323792982noreply@blogger.comtag:blogger.com,1999:blog-7949267671212594224.post-62321203562051885532010-03-05T01:21:06.986-08:002010-03-05T01:21:06.986-08:00Ran into this problem.
Thanks for posting!Ran into this problem.<br /><br />Thanks for posting!Anonymoushttps://www.blogger.com/profile/00266387893437069655noreply@blogger.comtag:blogger.com,1999:blog-7949267671212594224.post-37652074618820741712009-05-27T06:37:16.496-07:002009-05-27T06:37:16.496-07:00lelijke os!lelijke os!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7949267671212594224.post-83641623017541427832008-11-06T11:07:00.000-08:002008-11-06T11:07:00.000-08:00Thanks so much for this. Ran into this exact probl...Thanks so much for this. Ran into this exact problem when updating to 0.86-beta1 today.<BR/><BR/>Cheers!Drewhttps://www.blogger.com/profile/03973980589782136178noreply@blogger.comtag:blogger.com,1999:blog-7949267671212594224.post-78689141857672368972008-07-06T11:11:00.000-07:002008-07-06T11:11:00.000-07:00We haven't had any problems, except that we haven'...We haven't had any problems, except that we haven't been able to upgrade out server to CCNET 1.3. CCNET wouldn't start. That was months ago, and I haven't spent a lot of time updating the build scripts since they ain't broke, I'm not going to fix them<BR/><BR/>I did get SandCastle working with the builds in our current environment, and that was a royal pain too.<BR/><BR/>I never knew how many hours I spent implementing time saving tools until I had to track the time really accurately. I know these tools save time in the long run, but they sure have a big upfront cost. <BR/><BR/>I've considered converting to MS Team Builder, but I sure can't justify the effort and cost at this point.JBhttps://www.blogger.com/profile/08085754663631271944noreply@blogger.comtag:blogger.com,1999:blog-7949267671212594224.post-51483737612545491302008-07-02T13:19:00.000-07:002008-07-02T13:19:00.000-07:00bernie... after some testing, we are now using NAn...bernie... after some testing, we are now using NAnt .86 Beta and the NAnt contrib .85 together, as we had a need for some targets within the contrib .dlls. So far, all is working fine.<BR/><BR/>Hope that helps.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7949267671212594224.post-14016318384146244402008-07-01T06:41:00.000-07:002008-07-01T06:41:00.000-07:00Am having the same problem too..Solution file erro...Am having the same problem too..<BR/><BR/>Solution file error MSB5014: File format version is not recognized. MSBuild can only read solution files between versions 7.0 and 9.0, inclusive<BR/><BR/><BR/>Looks like only version 0.86 supports .net framework 3.5. However NAntcontrib is at version 0.85 and looking at the documentation there is no mention of .net framework 3.5. Does Nant 0.86 Beta and NAnt contrib 0.85 work ok togthterUnknownhttps://www.blogger.com/profile/15132634884133293955noreply@blogger.comtag:blogger.com,1999:blog-7949267671212594224.post-65276353868348377632008-06-26T10:03:00.000-07:002008-06-26T10:03:00.000-07:00I found your blog because I just had the same erro...I found your blog because I just had the same error as you, about net-3.5 not a valid framework identifier.<BR/> Question: have you had any issues with the beta .86 NAnt? We use .85 and I'm a little concerned about using a beta release.Anonymousnoreply@blogger.com