7+ Year Exp in IT Industry, Working as Technical Lead at HytechPro| Consultant | Leadership, Corporate Trainer | Motivational, Technical Speaker | Career Coach | Author | MVP | Founder Of RVS group | Trained more than 4000+ IT professionals | Azure | DevOps | Agile | ASP.NET | C# | MVC | WEB API | ANGULAR | TYPESCRIPT | MEAN | SQL | SSRS | WEB SERVICE | WCF...
Sunday, 3 November 2019

How To Create Angular App With .NET Core In Visual Studio

In this article, I am going to share knowledge "How to create an angular app inside .net core". Most of the developers are thinking about angular if it can be merged with visual studio .net core so that's fantastic. So don't worry guys I am here and going to explain about this0. If you are not aware of Angular and .net core separately please go through the below-given link these links are very helpful to create an angular app with .net core step by step.
I am going to explain in some of the steps to create an Angular app using .net core using visual studio:
Before start, you should make sure you have already installed Visual Studio 2017.

Open Visual Studio and create a project after clicking on File> New> Project, See the below image for more help. 

Choose template ASP.NET Core Web Application and click on OK after that one other popup will be displayed there, so now time to select the SPA category. We can choose any template e.g React, Angular, WebAPI, any template according to your requirement, Now we should select Angular because we are going to create SPA with .netCore with Angular. see image for more help

Select Angular and click on OK, Now SPA template is generating by Visual Studio for Angular with .netCore. it will take 1 minute approximate to create a complete application structure with all configuration on your system. see image for more help. 

Now open solution explorer and we can see SPA application structure is ready. Application structure completely follow the latest version of the framework .net Core. Open the given link if not aware of .net Core click here https://docs.microsoft.com/en-us/visualstudio/ide/quickstart-aspnet-core?view=vs-2019.
So let me explain about  ASP.NET Core - Project Structure one by one:

AngularSPAwithCore: Solution Name and project Name (in this project both names are the same but you can choose different).
Connected Services: We can use to connect any cloud services e.g Azure.
Dependency: It contains all the installed serverside NuGet packages as well as clientside frameworks such as jQuery, Angular etc. Client-side dependencies are managed using NPM in Visual Studio. 
Properties: Properties set the configuration launchSettings.json file which includes Visual Studio profiles of debug settings. 
wwwroot: Basically, This is root folder of the application and treated as webroot () folder, Inside wwwroot should be separate folders for the different types of static files such as JS, CSS, Image, bootstrap etc. 
ClientApp: Complete Angular application with all configuration. see below image to understand in easy way.

Above image, Now we see inside ClientApp Angular configuration available e.g. Component, Package.json, Index.html. etc. If you are already not aware about angular application structure so click on this link Clickhere.

Controller: In this folder, we can create our business logic e.g API
Pages:  Application related .cshtml pages e.g error.cshtml.
.gitignore: This file is part of the git code versioning tool to configure the setting of git logic as well as to ignore folder and file from the application.
appsetings.json:   As we know don't have anything called Web.config in Asp.net Core application which we use to write our connection strings or application-specific settings. Here we have a file called appsettings.json to store such type of information.
Program.cs: As we know Asp.net Core application starts from the program.cs file and execute always void main() function. 
Startup.cs: As we know about Asp.net Core Application there is no Global.asax file so instead of that use Startup.cs which is executed the first time when the application starts.

Now we can change the configuration in any file according to our project requirement. So let's move to our application which is already configured by default.
Application is ready to run but before that, we should make sure all client-side and server-side packages available inside the dependency node_module folder. If the yellow icon indicator displaying on the dependency folder it means we need to rebuild the application to restore the packages.

Let's press f5 or run the application after compile and build application will open in browser with default https://localhost:44391/See the below image.

In this application already default SPA application template is created. Now we can change layout, component, service etc. 
I hope this article is helpful to learn about ASP.NET Core SPA Application with Angular. 

      Happy Coding!! Keep learning!!

Bikesh Srivastava Angular, Interview Question
Saturday, 7 September 2019

Microsoft Azure DevOps Syllabus for deep learning

Getting started with Azure DevOps.
  1. Overview of Azure DevOps
  2. What DevOps Service and DevOps Server.
  3. Create Azure DevOps Account
  4. Roles And Responsibilities in Azure DevOps
  5. Create Project and User mapping to Azure DevOps
  6. Azure DevOps access to Different roles
  7. Project management using Azure DevOps
  8. Test case Management through Azure DevOps
  9. Methodologies In Azure DevOps (SCRUM,AGILE,CMMI)
  10. Deployment Group Creation
  11. Configure the Azure DevOps  service in the virtual machines
  12. Agent management in the Azure DevOps.
  13. Capacity Planning using Azure DevOps.
  14. Kanban Board Management
  15. Scrum Management

Azure DevOps Keywords
  1. Organization
  2. Projects
  3. Azure Board
  4. Dashboard
  5. Wiki
  6. Repos
  7. Pipelines
  8. Test Plans
  9. Artifacts

Repository Management/Branch Management
  1. Create the New repository
  2. Create the Master branch
  3. Create the Own Branches based on the developer requirement
  4. Branch merging
  5. Import Repository from Outside of the vsts to vsts
  6. Creating Pull requests And Accepting Pull Requests

CI/CD Process Using Vsts and Azure
  1. Task Creation Based on the Application Repository
  2. Create the CI Process
  3. Build Setup
  4. Environments Setup
  5. Authenticate Build to Azure Web service
  6. Failover Mechanism
  7. Load balancing
  8. Cluster Creation for Load Balancing
  9. Continues Integration Setup
  10. Test Cases Build
  11. Build alerts Configuration
  12. IAAS Deployments
  13. PAAS Deployments
  14. Micro Services Deployment using Azure
  15. Alerts Configuration Using Azure
  16. Arm Build and Release templates Creation
  17. Build And deployments through powershell
  18. Big bucket Jenkins internal configuration using Vsts for ci cd
  19. Build And Deployments Authentication and authorization

Working with Azure App service
  1. Overview of App Service
  2. Deployment in App Service
  3. Deploy and maintaining web apps
  4. Configuring web apps
  5. Monitoring web apps and WebJobs
  6. Traffic Manager

Working with Azure SQL Database
  1. Overview of SQL Database on Azure
  2. How to Deploy Azure SQL Database
  3. Implementing and managing Azure SQL Database
  4. Managing Azure SQL Database security
  5. Monitoring SQL Database in Azure
  6. Managing Azure SQL DB recovery
  7. Import and Export Data

Working with Active Directory
  1. Overview of Active Directory
  2. Why need AD for Azure
  3. Active Directory Configuration in Azure
  4. Domain Controller in Azure
  5. AD Federated Services in Azure
  6. Custom domain
  7. Monitoring Azure Active Directory

Microsoft Azure Syllabus for deep learning

Introduction to cloud computing and Microsoft Azure
Types of cloud computing
  1. What is What is Cloud Computing
  2. SaaS: Software as a service
  3. PaaS: Platform as a service
  4. IaaS: Infrastructure as a service
  5. Advantages and Disadvantages of Cloud Computing
Azure services
  1. Compute services
  2. Data services
  3. Application services
  4. Network services
Azure key concepts
  1. Datacenters and regions
  2. Azure portal
  3. Resources
  4. Resource groups
  5. Resource Manager templates
  1. Azure PowerShell
  2. Azure command-line interface
  3. REST APIs
Getting started with Azure subscriptions & pricing Calculation
  1. Select and enable an Azure subscription
  2. Grant administrative access to an Azure subscription
  3. View billing information in the Azure portal
  4. Get billing information from billing APIs
  5. Forecast cost with the pricing calculator
  6. Set up billing alerts
Azure Resource Manager
  1. Tips for creating resource groups
  2. Building Resource Manager templates
  3. Security of Azure resources (RBAC)
Azure App Services - Web Apps
  1. Introduction
  2. App Types
  3. Deploying Web App directly from Visual Studio.
  4. Scaling a Web Apps
  5. Application Settings Configuration

Azure SQL Database 
  1. Introduction/Overview.
  2. Creating and Using SQL Server and SQL Database.
  3. Azure SQL Database Tools.
  4. Using Azure SQL Database with EF Code First.
  5. Migrating on premise database to SQL Azure.
  6. Elastic Storage.
  7. Manage Business Continuity
  8. Azure SQL Database vs SQL Server in IaaA VM

Azure Virtual Machines
  1. Use cases
  2. Deployment of virtual machines
  3. Portal
  4. PowerShell
  5. Command-line interface
  6. Access and security for virtual machines
Azure Storage
  1. Use cases
  2. Blob storage
  3. File storage
  4. Table storage
  5. Queue storage
  6. Deploying a storage account
  7. Portal
  8. PowerShell
  9. Command-line interface
  10. Access and security for Azure Storage
  11. Virtual machine disks
  12. Storage tools
  13. Storage API
  14. Storage access keys
  15. Shared access signatures
  16. C# / MS.NET Azure Storage SDK
Azure Virtual Network
  1. Use cases
  2. Cloud-only virtual networks
  3. Cross-premises virtual networks
  4. Deploying a virtual network
  5. Portal
  6. PowerShell
  7. Command-line interface
  8. Access and security for virtual networks
Azure Web Jobs
  1. Logic App
  2. Web Jobs
  3. Microsoft Flow
  4. Functions
Azure Service Bus 
  1. Service Bus Basics
  2. Relayed Messaging
  3. Service Bus Queues
  4. Topics and Subscriptions

Azure Active Directory 
  1. Azure AD Introduction
  2. Relationship between AD DS and Azure AD
  3. Managing Active Directories
  4. Adding a custom domain name to Azure AD
  5. Managing Users, Groups and Devices
  6. Adding Co-Administrators for a Subscription
  7. Configuring Role Based Access Control
  8. Integrating On-Premise AD Identities with Azure AD
  9. Integrating Gallery Applications with Azure AD
  10. Integrating On-Premise Applications with Azure AD
  11. Implementing Azure AD B2B Collaboration

Bikesh Srivastava Azure, DevOps, Syllabus, Training & Seminar
Wednesday, 5 June 2019

Agile Vs. DevOps: What’s the difference?

What is DevOps?

DevOps is a software development method which focuses on communication, integration, and collaboration among IT professionals to enables rapid deployment of products.
DevOps is a culture that promotes collaboration between Development and Operations Team. This allows deploying code to production faster and in an automated way. It helps to increases an organization's speed to deliver application and services. It can be defined as an alignment of development and IT operation.

What is Agile?

Agile Methodology involves continuous iteration of development and testing in the SDLC process. This software development method emphasizes on iterative, incremental, and evolutionary development.
Agile development process breaks the product into smaller pieces and integrates them for final testing. It can be implemented in many ways, including scrum, kanban, scrum, XP, etc.

Agile Vs. DevOps

Stakeholders and communication chain in a typical IT process.
Agile addresses gaps in Customer and Developer communications
DevOps addresses gaps in Developer and IT Operations communications

Difference Between Agile and DevOps

What is it?
Agile refers to an iterative approach which focuses on collaboration, customer feedback, and small, rapid releases.
DevOps is considered a practice of bringing development and operations teams together.
Agile helps to manage complex projects.
DevOps central concept is to manage end-to-end engineering processes.
Agile process focusses on constant changes.
DevOps focuses on constant testing and delivery.
Agile method can be implemented within a range of tactical frameworks like a sprint, safe and scrum.
The primary goal of DevOps is to focus on collaboration, so it doesn't have any commonly accepted framework.
Team skill set
Agile development emphasizes training all team members to have a wide variety of similar and equal skills.
DevOps divides and spreads the skill set between the development and operation teams.
Team size
Small Team is at the core of Agile. As smaller is the team, the fewer people on it, the faster they can move.
Relatively larger team size as it involves all the stack holders.
Agile development is managed in units of "sprints." This time is much less than a month for each sprint.
DevOps strives for deadlines and benchmarks with major releases. The ideal goal is to deliver code to production DAILY or every few hours.
Feedback is given by the customer.
Feedback comes from the internal team.
Target Areas
Software Development
End-to-end business solution and fast delivery.
Shift-Left Principles
Leverage shift-left
Leverage both shifts left and right.
Agile emphasizes on software development methodology for developing software. When the software is developed and released, the agile team will not care what happens to it.
DevOps is all about taking software which is ready for release and deploying it in a reliable and secure manner.
Any team member should be able to do what's required for the progress of the project. Also, when each team member can perform every job, it increases understanding and bonding between them.
In DevOps, development teams and operational teams are separate. So, communication is quite complex.
Scrum is most common methods of implementing Agile software development. Daily scrum meeting is carried out.
DevOps communications involve specs and design documents. It's essential for the operational team to fully understand the software release and its hardware/network implications for adequately running the deployment process.
Agile method is to give priority to the working system over complete documentation. It is ideal when you're flexible and responsive. However, it can hurt when you're trying to turn things over to another team for deployment.
In the DevOps, process documentation is foremost because it will send the software to the operational team for deployment. Automation minimizes the impact of insufficient documentation. However, in the development of complex software, it's difficult to transfer all the knowledge required.
Agile doesn't emphasize on automation. Though it helps.
Automation is the primary goal of DevOps. It works on the principle to maximize efficiency when deploying software.
It addresses the gap between customer need and development & testing teams.
It addresses the gap between development + testing and Ops.
It focuses on functional and non-function readiness.
It focuses more on operational and business readiness.
Developing software is inherent to Agile.
Developing, testing and implementation all are equally important.
Speed vs. Risk
Teams using Agile support rapid change, and a robust application structure.
In the DevOps method, the teams must make sure that the changes which are made to the architecture never develop a risk to the entire project.
Agile produces better applications suites with the desired requirements. It can easily adapt according to the changes made on time, during the project life.
DevOps, along with automation and early bug removal, contributes to creating better quality. Developers need to follow Coding and Architectural best practices to maintain quality standards.
Tools used
JIRA, Bugzilla, Kanboard are some popular Agile tools.
Puppet, Chef, TeamCity OpenStack, AWS are popular DevOps tools.
The agile method needs teams to be more productive which is difficult to match every time.
DevOps process needs to development, testing and production environments to streamline work.
Agile offers shorter development cycle and improved defect detection.
DevOps supports Agile's release cycle.

  • DevOps is a software development method which focuses on communication, integration, and collaboration among IT professionals.
  • Agile software development method emphasis on iterative, incremental, and evolutionary development.
  • Agile refers to an iterative approach which focuses on collaboration, customer feedback, and small, rapid releases.
  • DevOps consider as a practice of bringing development and operations teams together.
  • Agile method is to give priority to the working system over complete documentation. It is ideal when you're flexible and responsive.
  • In the DevOps, process documentation is foremost because it will send the software to the operational team for deployment.
Bikesh Srivastava DevOps

Life Is Complicated, But Now programmer Can Keep It Simple.