-
Notifications
You must be signed in to change notification settings - Fork 168
Generator option for a solution with projects? #18
Comments
We'd love this for traditional .Net apps however its quite tricky as you |
Thanks. This I had starred already, and forgot about it (kinda in information overload a bit). try https://github.com/nosami/grunt-init-csharpsolution —
|
This project, the grunt-init-csharp solution one looks interesting, but I have a feeling (at least from my understanding now) that we'll need another solution, too, for the vnext stuff. One thing I noticed is, with Omnisharp, that the references used from the project.json file (while in folder mode) aren't loaded. I generated a new console solution, ran omnisharp in folder mode, and checked references loaded. I had some added references in the project.json file, and those weren't loaded for autocomplete capability. I'll look at the Omnisharp base code and see what's going on there. |
You should probably use the dth branch of omnisharp-server (which was a quick spike)..... omnisharp-roslyn https://github.com/OmniSharp/omnisharp-roslyn is coming with good support but it's still some way off. |
Thanks, I'll take a look at that. I'm really hoping that, after some ramp-up, that I can help with this project. I'm very excited to see the work done to make this work on linux/mac. I'll go ahead and 'close' this issue, and see start trying to work with the source code. Thanks again for your help. |
Hey all,
I'm still somewhat new to ASP.net but one pattern I've noticed from the book I've read, for a complete project is:
Solution-Folder/
Solution-Name.sln
Project.WebUI
Project.UnitTests
Project.Domain
An example of what I mean is:
https://sportsstorevs2011.codeplex.com/SourceControl/latest -- under the 'SportsStore' application.
I'm curious if anyone knows a way to generate this kind of structure with existing tools? I'm tempted to extend the generator-aspnet to allow this kind of structure, but I wanted to ask first if anyone knew a way to do this.
The text was updated successfully, but these errors were encountered: