Bug 3842 - Unsupported target framework is set for new project
Summary: Unsupported target framework is set for new project
Status: RESOLVED DUPLICATE of bug 6660
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: Trunk
Hardware: PC Linux
: Low normal
Target Milestone: ---
Assignee: Lluis Sanchez
Depends on:
Reported: 2012-03-10 12:13 UTC by Mansheng
Modified: 2012-11-16 16:59 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Mansheng 2012-03-10 12:13:52 UTC
Current Behavior:
When a new VB.net project is added, its target framework is set to .Net4.0 and there are no errors or warnings. However, when the solution is reopened, the project cannot be loaded and I couldn't find any way to change its target framework when its state is "load failed".

Expected Behavior:
When the default target framework is not supported by the language, MD should choose an alternative one.
Comment 1 Mansheng 2012-03-10 12:17:26 UTC
See https://github.com/mono/monodevelop/pull/166 for a possible fix
Comment 2 Jeffrey Stedfast 2012-11-16 16:59:37 UTC

*** This bug has been marked as a duplicate of bug 6660 ***