-
Notifications
You must be signed in to change notification settings - Fork 168
Nancy generator is outdated #67
Comments
Pretty sure the dependencies are exactly the same so would be interested to On 18 February 2015 at 10:03, João Moreno [email protected] wrote:
|
It seems to only be in the diff aspnet-nancy/project.json nancy-nancy/project.json
3,5c3,5
< "Kestrel": "1.0.0-alpha4",
< "Microsoft.AspNet.Owin": "1.0.0-alpha4",
< "Nancy": "1.0.0"
---
> "Kestrel": "1.0.0-*",
> "Microsoft.AspNet.Owin": "1.0.0-alpha2",
> "Nancy": "0.23.2"
11,12c11,13
< "aspnet50": {},
< "aspnetcore50": {}
---
> "aspnet50": {
> "System.Runtime": ""
> } |
hmm, baffled, |
I take it back. Both templates have something broken. I cannot run the template generated by generator-nancy.
In summary: I cannot build the one generated by generator-aspnet and cannot run the one generated by generator-nancy. |
what version of kre do you have? On 18 February 2015 at 10:32, João Moreno [email protected] wrote:
|
|
same as me On 18 February 2015 at 10:38, João Moreno [email protected] wrote:
|
You don't see any difference when generating from both templates? |
Ah I get a failure on kpm build with aspnet generator. Hmmm On 18 February 2015 at 11:04, João Moreno [email protected] wrote:
|
I think there may be an issue with the Nancy generator in aspnet. I was thinking to update all templates to work with |
x-ref: #60 |
#69 should now solve this. |
Nancy templates updated and publish in v 0.0.31, tested and built with beta3 |
👏 does work. It builds, thanks! |
Thanks everyone, closing now since its released |
Verified that I can run ( |
I used this generator to scaffold a Nancy application. I ended up with something that could be run (
k kestrel
) but not built (kpm restore; kpm build
). It couldn't find the Nancy namespace when building.I looked at @jchannon's generator-nancy and tried it out. It produced a seemingly healthier scaffold which I can both run and build successfully.
Why not incorporating generator-nancy into this project?
The text was updated successfully, but these errors were encountered: