[MonoDevelop] The 'build order' feature doesn't work with xbuild, msbuild or VS

[fsharp]

[MonoDevelop] The 'build order' feature doesn't work with xbuild, msbuild or VS

[funnelweb]

We should just delete the MonoDevelop-specific 'build order' as a feature - xbuild ignores it, as does Visual Studio and msbuild.

[funnelweb]

updated the title of the bug to reflect this

[7sharp9]

Then how do you change the build order? Modify the fsproj file?

On 19 Nov 2012, at 09:21, Ben Winkel [email protected] wrote:

updated the title of the bug to reflect this

—
Reply to this email directly or view it on GitHub.

[DanielFabian]

I do manually edit the .fsproj at the moment, yes. Apparently the gui feature has a tag "BuildOrder" (lines 13-23 in the change set above).

When I change the build order in the gui, then the change is not reflected in the project structure, but only in that special tag.

Therefore the file order for msbuild/xbuild does not change and also the "solution pane" is not updated, until I manually change the .fsproj.

EDIT: to not have problems with intellisense, I always do both: set the correct order in the .fsproj by hand (for the compiler and solution pane) and in the gui (for intellisense)

[7sharp9]

There must be an alternative, rather than removing it fix it or adapt it. Maybe cross post to the monodevelop forums for a solution?

On 19 Nov 2012, at 10:00, DanielFabian [email protected] wrote:

I do manually edit the .fsproj at the moment, yes. Apparently the gui feature has a tag "BuildOrder" (lines 13-23 in the change set above).

When I change the build order in the gui, then the change is not reflected in the project structure, but only in that special tag.

Therefore the file order for msbuild/xbuild does not change and also the "solution pane" is not updated, until I manually change the .fsproj.

—
Reply to this email directly or view it on GitHub.

[funnelweb]

yes, editing the .fsproj is required if using xbuild. (This is a bit easier in MonoDevelop than Visual Studio because it lets you open the .fsproj in the same editor session. You have to choose to open the .fsproj with the source code editor to do that)

Suppose we could implement the Alt-up and Alt-down of Visual Studio.

[DanielFabian]

What is awesome already is, that it automatically updates and that it shows fsyacc and fslex steps, even if it does not understand.

And the idea with alt-up and alt-down would be awesome

[funnelweb]

@7sharp9 right now the feature is broken - it gives project files that can't be used with xbuild, msbuild and VS.

A 'build order editor' is ok but it shouldn't persist the build order using the current BuildOrder node in the .fsproj file (because that node is ignored by xbuild, msbuild and VS - the only thing not to ignore it is MD when xbuild is disabled).

Maybe we could persist build order edits by rewriting the order of the entries in the .fsproj after editing.

[DanielFabian]

That would be a clean way as it would remove the redundany. And it would
also support fslex and fsyacc-like extensions, i think.

Mit freundlichen Grüssen
Daniel Fabian

[7sharp9]

@funnelweb A command that moved the current file up/down would cause MD/XS to reload the project wouldn't it? We would probably have to suppress the reloading, or at least the collapsing of the project tree.

[7sharp9]

Closing this, using new feature #135