Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 16594 on
Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
Reported on behalf of a few customers. If ClickOnce Publishing compatibility is not planned (or is far off), then hopefully the error message for this situation can be improved. The current error message about TargetFrameworkVersion is confusing since the TargetFrameworkVersion visible in the .csproj is correct.
## Steps to reproduce
1. Create a new Empty iOS project in Visual Studio 2013 (and fill in the Application name, identifier, and version number in the project properties).
2. Go to the "Publish" project properties page, and click on the "Publish Wizard" button to set up the app for ClickOnce Publishing.
3. Click Finish.
> Invalid value for 'TargetFrameworkVersion'
... appears in the Error List, and
> error MSB3174: Invalid value for 'TargetFrameworkVersion'
... appears in the Build output window.
Cleaning and rebuilding leads to the same error again.
Remove these lines (added by the ClickOnce setup process) from the .csproj:
## Example report from the forums
I am able to reproduce the issue described in comment 1 myself with a an iOS Unified template app. Simply using the Build->Publish AppName menu adds or changes the XML element for GenerateManifests to:
I attempted to reproduce this issue based on the bug description with the latest Visual Studio 2017 Preview version 15.3, and I was unable to hit the problem.
If this issue is still occurring for you, please reopen this report and attach a reproduction.
I am still able to reproduce an error related to the `GenerateManifests` element after running through the ClickOnce publication wizard .