Structuring WebApp with heavy Powershell script usage
Hello r/dotnet,
I've been a lurker on this subreddit for a better part of a year now, and I am in need of some advice.
I'm developing a web application (using Angular 7 client-side & .NET Core web API server-side) that is an all-encompassing IT-infrastructure monitoring tool. The requirements still aren't fully fleshed out yet, but the idea is that the app will provide a dashboard that allows for displaying of each environment's servers, each IIS servers' applications, specific details about the servers/apps, etc.
Thus far, I've been using a lot of Powershell scripts to query IIS for information, invoked through my .NET core code. My question is, how should I structure/architect my application? Is this even a good idea? I'm relatively new to Powershell and have never invoked Posh through .NET c# code.
There's also a namespace called Web.Administration that allows for the management of IIS objects, but it's not as friendly as powershell is. Do you recommend I keep invoking powershell scripts, and if so, how should I structure my code to do this? Or, should I force myself to do everything through the Web.Admin APIs?
Thanks for any advice, it's greatly appreciated.
0 comments:
Post a Comment