Home → Support →

Build contains projects using unsupported .NET frameworks

• Edit

Austin Fatheree

Apr 19, 2013 @ 10:23 PM

Have you all seen this before?

4/19/13 5:19 PM Received notification, queuing build
4/19/13 5:19 PM Downloading source
4/19/13 5:19 PM Downloaded source in 3.35 seconds
4/19/13 5:19 PM Starting build
4/19/13 5:20 PM 15 warnings
4/19/13 5:20 PM Build completed in 4.11 seconds Show Log
4/19/13 5:20 PM Build contains projects using unsupported .NET frameworks

https://appharbor-logs.s3.amazonaws.com/95/ec5694-ff86-4640-98f6-a1...

1. Support Staff 1 Posted by rune on Apr 19, 2013 @ 11:08 PM

   

   Hi Austin,

   Yes that can happen if we don't recognize the framework version. We read the framework version from the targetFramework attribute in the configuration/system.web/compilation element (if it is a web application) - can you let me know the value you have there?

   Best,
   Rune

   • Edit

2. 2 Posted by Austin Fatheree on Apr 20, 2013 @ 02:53 AM

   

   <compilation debug="true" targetFramework="4.0.3" />

   • Edit

3. Support Staff 3 Posted by rune on Apr 20, 2013 @ 05:56 PM

   

   Ok, makes sense then - we look for either 4.0 or 4.5 and not 4.0.3. I'm fairly certain that specifying one of those two instead should work just fine.

   This is a fairly uncommon issue, but we may want to add 4.0.3 as a recognized framework version. Did you do anything in particular to get that framework version in your web.config, or did you change it manually for a particular reason?

   Best,
   Rune

   • Edit

4. 4 Posted by Austin Fatheree on Apr 23, 2013 @ 01:30 PM

   

   Reverting back to 4.0 worked...I'm not sure why it was 4.0.3...I guess that
   is the latest version that I have installed.

   • Edit

5. Support Staff 5 Posted by rune on Apr 23, 2013 @ 09:27 PM

   

   Alright great. I'm still trying to figure out why the framework version would be different though - if you didn't change anything it stands to reason that this is inserted automatically in certain cases, but we've haven't figured out what causes this framework version to be inserted. We'd like to confirm the behavior and cause of it before introducing "support" for something that may not work.

   It all resolves to the same framework version anyways as long as the major version number if 4 or higher, and we have contemplated just resolving based on the "minor version number" and see if that is less than or equal to 5. We haven't heard about any framework incompatibilities from customers who changed so that's likely the way we'll go. Thanks for your feedback.

   Best,
   Rune

   • Edit

6. rune closed this discussion on Apr 23, 2013 @ 09:27 PM.