Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forge integration #36

Closed
wants to merge 4 commits into from
Closed

Forge integration #36

wants to merge 4 commits into from

Conversation

donopj2
Copy link
Contributor

@donopj2 donopj2 commented Jan 6, 2018

A few basic utility functions that get us started with Forge integration. I'd appreciate a bit of advice about how we expect to package and reference Forge.exe in our build as I'm a bit unsure of best practices @tlycken @forki?

I've also switched us over to Expecto, which requires a simple run of the test project executable. This has broken dotnet test though, any thoughts on how to fix @tlycken?

Also just something I was thinking about while looking through the Forge docs. As far as I can tell it provides no ability to bulk reorder files in a project. Just move up and move down commands or remove and add, which require separate individual calls. Is there a concern that this will be slow for larger projects?

@donopj2
Copy link
Contributor Author

donopj2 commented Jan 7, 2018

I'm closing this PR because I don't think this approach is ideal any longer. After playing around with this a good bit more my feeling is it will be simpler and faster to take the original approach of parsing the project file xml and making the ordering adjustment ourselves. If someone feels differently please let me know.

@donopj2 donopj2 closed this Jan 7, 2018
@tomasaschan tomasaschan mentioned this pull request Jan 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant