3 ms·

I think a good strategy to insulate yourself from .NET is to slowly move your .NET code into RESTful services and isolate the dependencies there. The one big d

I think a good strategy to insulate yourself from .NET is to slowly move your .NET code into RESTful services and isolate the dependencies there. The one big downside is that most of the alternatives are designed to work better with Unix based systems. That's usually a much bigger pill to swallow for an all Windows .NET shop so YMMV with pushing that. I know a shop trying to do Node.JS on IIS so that may be an option worth looking into to see if it works. YMMV here too, because it's really bleeding edge right now.

chrislomax 15y ago
Well I was aware of the IIS node.js plug-in. I am really interested in node.js as well. It may be worth like you say putting it into a service that we could consume from many languages and taking it from there. Our main issue really is our admin as it relies quite heavy ContentPlaceholders as we populate them on runtime but I am more interested right now in trying new technologies