3 ms·

.NET clone of node.js would be nice, because I like the idea of node.js but not enough to ditch all my .NET stuff (especially entity framework).

by skrowl 13y ago

chadzawistowski 13y ago
Edge.js might interest you. It's an interop library for .Net and node.js: http://tjanczuk.github.io/edge/#/ http://tjanczuk.github.io/edge/#/
tracker1 13y ago
I think that the LINQ integration with EF is nice.. but EF in and of itself isn't all that great imho... Most of what it does is generate types to correspond to your database tables. When you use a language with real variable types, it's less of an issue... If you really want it, you could shoehorn generators and other db platforms into the hyena[1] package. In general, I've found that using databases tend to be much more straight forward under node, and that using ORM tools are less necessary. [1] https://www.npmjs.org/package/hyena https://www.npmjs.org/package/hyena
- j_s 13y ago
  C# (.NET4+) has real variable types, and a library to use them for database access. Using Type dynamic - http://msdn.microsoft.com/en-us/library/dd264736.aspx http://msdn.microsoft.com/en-us/library/dd264736.aspx https://github.com/robconery/massive https://github.com/robconery/massive
  - tracker1 13y ago
    When you use dynamic, you lose the biggest advantage of C# in general, intellisense in VS. Don't get me wrong, it can be great to use dynamic at times... I just feel you're losing the advantage that VS/C# give you when you do, so you may as well be using something else. (I like node.js)
lucian1900 13y ago
There's nothing in node.js that you can't get with .NET/Mono except for JavaScript, and even if you must run JS for some reason there are some solutions (like IronJS).
nbevans 13y ago
Entity Framework is really not a good excuse. .NET has lots of great things going for it. Entity Framework is firmly on the "enterprise .NET" list of such items though. .NET has always been able to do what Node does anyway. It has had HttpListener since v1.0...
- mattmanser 13y ago
  Think you'll be getting a shock in a couple of years if you think the EF is enterprise. It's changed massively and coding without it is becoming a little like coding javqscript without jQuery. You can do it, but why bother writing all those crud operations yourself?? Even with complicated SQL you can hand roll it and then tell the EF which class you're.returning and it'll handle all the boring `rs.GetInt(rs.GetOrdinal("ID"))` crap.
PallarelCoedr 13y ago
OWIN will give some of what you are looking for.
martydill 13y ago
I started something along these lines a while ago. Haven't touched in quite some time though. https://github.com/martydill/node.fs https://github.com/martydill/node.fs

.NET clone of node.js would be nice, because I like the idea of node.js but not enough to ditch all my .NET stuff (especially entity framework).

by skrowl 13y ago

.NET clone of node.js would be nice, because I like the idea of node.js but not enough to ditch all my .NET stuff (especially entity framework).

chadzawistowski 13y ago

Edge.js might interest you. It's an interop library for .Net and node.js: http://tjanczuk.github.io/edge/#/ http://tjanczuk.github.io/edge/#/

tracker1 13y ago

I think that the LINQ integration with EF is nice.. but EF in and of itself isn't all that great imho... Most of what it does is generate types to correspond to your database tables. When you use a language with real variable types, it's less of an issue... If you really want it, you could shoehorn generators and other db platforms into the hyena[1] package. In general, I've found that using databases tend to be much more straight forward under node, and that using ORM tools are less necessary. [1] https://www.npmjs.org/package/hyena https://www.npmjs.org/package/hyena

j_s 13y ago
C# (.NET4+) has real variable types, and a library to use them for database access. Using Type dynamic - http://msdn.microsoft.com/en-us/library/dd264736.aspx http://msdn.microsoft.com/en-us/library/dd264736.aspx https://github.com/robconery/massive https://github.com/robconery/massive
- tracker1 13y ago
  When you use dynamic, you lose the biggest advantage of C# in general, intellisense in VS. Don't get me wrong, it can be great to use dynamic at times... I just feel you're losing the advantage that VS/C# give you when you do, so you may as well be using something else. (I like node.js)

lucian1900 13y ago

There's nothing in node.js that you can't get with .NET/Mono except for JavaScript, and even if you must run JS for some reason there are some solutions (like IronJS).

nbevans 13y ago

Entity Framework is really not a good excuse. .NET has lots of great things going for it. Entity Framework is firmly on the "enterprise .NET" list of such items though. .NET has always been able to do what Node does anyway. It has had HttpListener since v1.0...

mattmanser 13y ago
Think you'll be getting a shock in a couple of years if you think the EF is enterprise. It's changed massively and coding without it is becoming a little like coding javqscript without jQuery. You can do it, but why bother writing all those crud operations yourself?? Even with complicated SQL you can hand roll it and then tell the EF which class you're.returning and it'll handle all the boring `rs.GetInt(rs.GetOrdinal("ID"))` crap.

PallarelCoedr 13y ago

OWIN will give some of what you are looking for.

martydill 13y ago

I started something along these lines a while ago. Haven't touched in quite some time though. https://github.com/martydill/node.fs https://github.com/martydill/node.fs