-
Notifications
You must be signed in to change notification settings - Fork 5
Is this project dead? #1
Comments
You're more than welcome to take this and run with it - I've added you to the project, and we can move to a more appropriate organization if it takes off. I'm not aware of any other Razor implementations of an F# provider, and we don't really need more than one. Assuming you still want to work with the ASP.NET 4 stack, the boilerplate to integrate into the stack doesn't look like it has changed much: Razor vNext does look quite a bit different: |
I'd love to contribute to this project as well. |
Sold. If you haven't seen the (4.5-year-old!) introduction post: |
I wonder if it would make sense to have a single solution with projects for each MVC version, a la Glimpse? From a test maintainability standpoint, there's probably an opportunity to share test |
I think that's a very sensible solution layout, more so than individual project branches. So, to clarify, do you think there should be separate namespaces consumed for FSRazor based on supported MVC version? I noticed that's how Glimpse is organized. This can still be accomplished, too, when using Project Scaffold based solutions. I really like the idea of shared test code among the different MVC version branches. Code reuse is a thing, after all 😉 I don't see any test code in the current revision, however it appears there's some test code available in the Razor repository. Since the discussion is moving off the issue's main title, I've made a new issue #2 with better focus. |
I am asking, because I would like to build a web page with just F#. If it is dead, could you give me hints to build my own version?
The text was updated successfully, but these errors were encountered: