Bug 10305 - Clean up the default Target Framework level in MSBuild and AddIns
Summary: Clean up the default Target Framework level in MSBuild and AddIns
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: Tools and Addins ()
Version: 4.5.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: dean.ellis
URL:
Depends on:
Blocks:
 
Reported: 2013-02-14 14:16 UTC by dean.ellis
Modified: 2017-06-28 21:30 UTC (History)
3 users (show)

Tags:
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:
Status:
RESOLVED NORESPONSE

Description dean.ellis 2013-02-14 14:16:42 UTC
why investigating https://bugzilla.xamarin.com/show_bug.cgi?id=9469 we found that we are not being consistent when defining the default Target Framework within the Visual Studio Addin and within MSbuild. 

In the Visual Studio Addin it is defaulted to 2.2 when it really should be v2.2 and with in the MSBuild taargets it is defaulting to v1.0 which is incorrect. We need to go through a clean this up.
Comment 1 Mikayla Hutchinson [MSFT] 2013-02-14 15:46:43 UTC
Why do you think the MSBuild targets' defaults are incorrect?
Comment 4 Atsushi Eno 2013-05-22 14:37:18 UTC
Is this still a valid bug? If not please close it.