You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've created an empty solution, then, I used the "Add new project to solution" option, but doesn't edit the sln file. I mean, this option doesn't add the project and projectconfiguration sections. I found this question but can't find a way to re-template the .sln file once it have been created.
The text was updated successfully, but these errors were encountered:
You're right, the sln file is an VS's concern. But thinking about how to solve it I had an idea, using a file watcher on the editors that modify the sln (and also the fsproj) content when new file/folder is added. At least on Electron based editors there is a pathwatcher. So, in Atom and VSCode (using ionide), we can stop editing that files manually on xplat development. And also use FAKE Build without run into issues like this (when compile files separately). The only issue would be the order, that Move upMove down on VS Solution Explorer 😕
I've created an empty solution, then, I used the "Add new project to solution" option, but doesn't edit the sln file. I mean, this option doesn't add the project and projectconfiguration sections. I found this question but can't find a way to re-template the .sln file once it have been created.
The text was updated successfully, but these errors were encountered: