Having said that, you shouldn't need to deploy Node in production, it is just for the tooling.
On Wed, Nov 29, 2017 at 9:38 AM, Craig van Nieuwkerk <crai...@gmail.com> wrote: > All the Angular (and almost every Js framework) tooling is built with > Node, so on you dev machines at least you are unlikely to be able to get > away from it. Going forward, unless you are planning on building something > bare bones with no framework I think there is not much chance of being able > to not have a dependency on Node. > > https://i.redd.it/tfugj4n3l6ez.png > > On Wed, Nov 29, 2017 at 9:21 AM, Greg Keogh <gfke...@gmail.com> wrote: > >> Folks, just a heads-up for the unprepared. >> >> Following a suggestion from Craig I used the command "dotnet new angular" >> to create a fresh Angular Visual Studio project. I've had no need to use >> .NET Core since it came out, so it's interesting to look at the help for >> the various options. The Angular project is generated with 45 files in 19 >> folders. After you open it in VS2017 it runs a quiet frenzy of downloads >> into the node_modules folder, this produces 13478 files in 1715 folders >> containing roughly 1.7 million lines of JavaScript. >> >> Now pardon me ... but is this crazy?! What I mean is, is this typical of >> an Angular project or is the default project incompletely or incorrectly >> configured? It's like creating a .NET traditional project and having the >> complete Framework source code included. I don't recall any concept of a >> "compiled library" for JavaScript, so I'm guessing such a thing hasn't been >> invented yet, is that right? >> >> I tried running the project but after giving me 150 package conflict >> warnings it stops and tells me "Node.js is required to build and run this >> project". Now I'm confused, as why on earth would that be needed? I was >> hoping to avoid Node.js completely as the backend of our proposed app is a >> working WebApi. >> >> I will be posting a formal request in here soon for anyone who can help >> us develop a browser-based product. >> >> *Greg K* >> >> On 17 November 2017 at 10:13, Craig van Nieuwkerk <crai...@gmail.com> >> wrote: >> >>> If you backend services are well established and you could easily put a >>> WebAPI over them, then it makes sense to do a SPA and mainly Javascript >>> front end. >>> >>> If it is an enterprisey type app then it is hard to go past Angular, >>> Pluralsight is your friend to learn. I would also talk to ssw.com.au, >>> they have some good courses that will get you running in the right >>> direction quickly. >>> >>> Craig >>> >>> On Fri, Nov 17, 2017 at 9:14 AM, Greg Keogh <gfke...@gmail.com> wrote: >>> >>>> Folks, we have a serious decision to make about the future directions >>>> of our 10 year old Silverlight product that is in wide use in some big >>>> companies. I told the boss I'd poll this forum for advice, so I'd really >>>> appreciate serious comments from people in-the-know. >>>> >>>> The large companies using the Silverlight product are now locking down >>>> security, so Internet Explorer is being banned and Edge adopted, which >>>> means Silverlight is out (some employees are already being forced to use >>>> the product from home). Our product is available as Xamarin authored tablet >>>> and phone apps for three platforms, but they won't even allow our apps on >>>> their company devices. >>>> >>>> So for the first time we are forced to produce a "browser based" >>>> version of our product, which apparently is acceptable to their security >>>> policies and audits. Here are some issues swirling in my head: >>>> >>>> - The backend services to drive the product are established. >>>> - The UIs of other product versions are explorer (master-detail) >>>> style, so it would be nice to maintain that feel in the browser. >>>> - We have to display data in Excel-like tables and a variety of >>>> charts (the richer and more interactive the better). >>>> - Should we use server-side ASP.NET Web Forms or MVC to drive it? >>>> - Should it be browser-side SPA? (you know I hate JS everything, so >>>> there is personal resistance there). >>>> - Could server-side and browser-side be combined to produce a >>>> better hybrid experience? Are there things to help you do that? >>>> - There are development platforms such as GTK and many others I >>>> guess that I'm not familiar with. Are they viable? >>>> - Other issues I'm forgetting? >>>> >>>> >>>> I'm personally familiar with ASP.NET Web Forms and MVC, but not with >>>> quality JS, layout or styling. Perhaps I could write a black-and-white >>>> skeleton of the working product and then give it to someone to style and >>>> script (I have done that once before). >>>> >>>> So in summary (I know this is a very broad question) ... if you were in >>>> my position, how would you proceed to produce a browser based version of a >>>> product? >>>> >>>> Cheers, >>>> *Greg K* >>>> >>>> >>> >> >
