Software Web Development Structure

BASICS:- 1

Front End : User Interface

Middle Ware : Business Requirement Functionality

Back End : Storage Area

Example:

Front End Technologies : Html, CSS, JavaScript, Bootstrap, Angular, React ....

Middle Ware Technologies : C#, Java, Webapi, Azure Functions....

Back End Technologies : SQL, Azure Database, Oracle....

Comments

Power Portals Deployment Using Git Repos from VS Code

Open Visual Code - Open New Workspace In Vs Code - Extension - Search for - Power Platform VS Code Extension -> Install Open Terminal - check for command pac (It gives the version of power cli) check for Authorization pac auth list ( if list is there delete the list for fresh start) pac auth delete --index 1 ( if no list is found create auth ) pac auth create --url https://org.crm.dynamics.com/ ( it will ask for user name and password ) After successful of creation - check for the auth pac auth list To download portals check for paportal Microsoft Power Platform CLI command for portals is “paportal”. on the terminal - enter pac pac ( if paportal is there check for the portal list ) pac paportal list ( It will give the website ids of paportals of the organisation ) Connected to...Portal Environment Index WebSiteId ...

Environment Specific Deployment Profiles For Power Portals CLI Upload

Upload portal customisation using Environment specific portals deployment profile. Example: Deployment profiles for Development, UAT, PROD The deployment Profile allows you to define a set of variables for the environment in YAML format. If you're creating PROD profile, you can create file under deployment-profiles with the name "PROD.deployment.yml" (that is, <profileTag>.deployment.yml). And you can run command with tag (<profileTag>) to use this profile: example: pac paportal upload --path "X:\portals\starter-portal" --deploymentProfile PROD In this file, you can have the table (entity) name with table ID, list of attributes, and the values that you want to override while uploading the portal configuration using the deploymentProfile parameter adx_contentsnippet: - adx_contentsnippetid: xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx adx_name: abc\prod adx_value: https://abc.com/xyz/prod - adx_...

Power Apps Application Life Cycle Process For Release Management

SYNOPSIS The goal of this blogger is to aid in the ALM process for model-driven-apps. DESCRIPTION Most of the projects are adopting to ALM process where it can follow the agile methodologies and release the project in sprint models. so that release can be smooth and it can be easily tracked. To achieve this sprint model development. Developers need to create sprint wise solutions in the D365 CRM to move them to the higher environments based on sprint cycle. They need to check in their code into the git repository using git commands to track the changes. All the changes in the repository need to be linked with azure build and release pipelines to release those changes to higher environment. PREREQUISITES 1. Need to have Azure Devops, Power apps and D365 CRM subscription with global admin role for setup. On Local Machine : Need to Install Vs code, Git, Power Apps CLI, Azure CLI 2. Git should be installed 3. Powerapps CLI should be installed - ...

Mahesh Kondawar

Search This Blog