-
Notifications
You must be signed in to change notification settings - Fork 152
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
How to move existing solution to scaffold setup #160
Comments
Not sure there is a single correct way of doing that.. My procedure is quite simple:
Done, but this only covers my use, not sure it is generic enough to use as a recipe for others. |
That would be a way, only, I already have a solution on github with a src folder, i.e. the structure matches the scaffold setup. |
I've done the same procedure with existing projects with almost matching structure, and since git operates on file content, it usually creates nice diffs, even if your solution and folders are not the same. But again, my experience may not apply to others. |
I am still having trouble getting it working with a multi project solution. Seems that the current setup is geared toward a single project solution. I have modified the build script to suite my needs but the build target now fails. The current script I am using looks like:
However, this runs in a:
|
Any reason for not just building your .sln file rather than individual proj files? |
The reason is that the projects in the solution are services that work with each other, so, I would like to have more fine grained control. However, I can build the solution as a whole, however, I then still run into errors. When I build the solution manually (doing a rebuild), it works. Trying to build the solution by the build script runs into errors. Unfortunately, there is no real logging, and the command window overflows. At the moment I seem to have a problem with paket:
But the message is not very helpfull ;-( |
Did you convert from nuget to Paket dependency managmenet? |
Yep. |
This is what I get checking the offending paket command:
ca.Utilities.Tests\paket.references"" exited with code 1.Press any key to continue . . . c:\Users\hal\Dropbox\Development\GenPres> So, when paket runs the command from the build script, it fails, but when doing this manually it just runs fine. Could this be some sort of race condition, in which access is denied to the paket.references file? |
Now I'm blank. @forki any idea? |
Thanks to @forki, I was able to run the build with:
So, disabling the restore process during build seems to fix the issue. However, moving a multiproject sotion to the scaffold still has some challenges, I'll come back to that. |
("RestorePackages", "False") should be set automatically in FAKE 3.38 - can you please try to verify that? |
@Thorium: does `FAKE 3.38 work for your scenario? |
I actually still use plain MSBuild Xml and not Fake... So I did set it just RestorePackages false as a property and get (only) a minute away from build. |
Closing this discussion - the original scenario of "moving" is not really supported by the scaffold |
It would be nice to have a guide how to move an existing solution to the scaffold structure. At the moment I am trying to do this by trial and error.
The text was updated successfully, but these errors were encountered: