Bug 1284 - Migration from .mdp to .csproj misses some important properties
Summary: Migration from .mdp to .csproj misses some important properties
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2011-10-05 18:51 UTC by Jeffrey Stedfast
Modified: 2011-10-12 14:47 UTC (History)
3 users (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 Jeffrey Stedfast 2011-10-05 18:51:19 UTC
It looks like the old .mdp project format stored information such as:

- CFBundleDisplayName
- CFBundleIdentifier
- CFBundleVersion
- NSMainNibFile
- Icons

These values are all available in the .mdp toplevel Project node:

<Project name="MyAppName" fileversion="2.0" DefaultNamespace="MyAppNamespace" language="C#" MainNibFile="MainWindow.xib" BundleIdentifier="com.mycompany.myappname" BundleVersion="1.0" BundleDisplayName="My App Name" BundleIcon="icon57.png" BundleIconHigh="icon114.png" BundleIconSpotlight="icon29.png" BundleIconSpotlightHigh="icon58.png" targetFramework="IPhone" ctype="IPhoneProject">
Comment 1 Mikayla Hutchinson [MSFT] 2011-10-05 19:00:35 UTC
Uh, the main point of the migrator was to move these values to the Info.plist.

You shouldn't even have a mdp, that format's been non-default for three years, and effectively deprecated since before MT was released. MT projects have been forcing migration to MSBuild format since the beginning of this year.

The only way you'd have a mdp is if someone manually changed the MD default project format for some unknown and likely misguided reason, and didn't edit the project with a MD any newer than Feb or so.
Comment 2 Jeffrey Stedfast 2011-10-05 19:07:54 UTC
We have a customer that has just updated to MonoDevelop 2.8 from from an older version where he was using the .mds/.mdp project format. We should try to make this migration as painless as possible, especially since we can get the information we need from the old format.
Comment 3 Alan McGovern 2011-10-05 19:18:24 UTC
Just to confirm, there are values in the mdp which are not ending up in vie info.plist? If so having the project file would be awesome.
Comment 4 Mikayla Hutchinson [MSFT] 2011-10-05 20:03:15 UTC
The MT Xcode 4 migration mechanism doesn't support the mdp format, as it's been deprecated for some years.

As a workaround, load the project in MD 2.6, open Project Options, click OK. You will be prompted to migrate the format to VS2010. After you do so, MD 2.8 will be able to import it correctly.
Comment 6 ric3kg 2011-10-06 12:27:12 UTC
I tried this workaround but did not get a prompt to migrate. Is there something else I nned to do?
Comment 7 Jeffrey Stedfast 2011-10-06 13:34:00 UTC
Once you export it in MonoDevelop 2.6, opening the resulting project in MonoDevelop 2.8 will offer to migrate the project.

At least that's what worked for me.
Comment 8 ric3kg 2011-10-06 13:37:28 UTC
How do I export the project?
Comment 9 Jeffrey Stedfast 2011-10-06 13:50:36 UTC
Unfortunately I no longer have MonoDevelop 2.6 installed for reference, but I believe that the Export command was under the Project menu.

Hope that helps
Comment 10 ric3kg 2011-10-06 13:54:20 UTC
Yes, I see it now. I have to highlight the Solution then there is an item in the Project menu to Export.

Comment 11 ric3kg 2011-10-06 14:18:40 UTC
I converted the old 2.6 version to VS2010. Opened new project in MD 2.8. Checked project settings, was prompted to convert - did so. Added a new file to the project, compiled, closed project. Open project, added files are missing...
Comment 12 ric3kg 2011-10-06 14:24:10 UTC
I'm wondering if the gist of the problem is that once converted a new project file is created. But the launch screen for MD does not know about that, so I keep opening the older project file?
Comment 13 Jeffrey Stedfast 2011-10-06 14:27:46 UTC
That sounds likely. You are probably continuing to open the .mds project instead of the .sln.

Try "open a new project" instead of using the recent project list.
Comment 14 Alan McGovern 2011-10-12 11:42:44 UTC
Has the project been successfully migrated through to MonoDevelop 2.8? If so, should i close this bug?
Comment 15 Jeffrey Stedfast 2011-10-12 14:47:03 UTC
Yes, it's been migrated.

I guess we can close this for now with the plan to re-open if more people start running into this.