C#, Asp.net, Java, PHP, Power BI, SharePoint Discussion Forums

In this article we are reading about  “ Page Directives in Asp.Net ” . The directives are instructions that specify optional settings in Asp.Net, but they are not rendered as part of the HTML page return to the client browser. These instructions include registering a custom control, page language etc. It describes how the .aspx pages (web forms) or .ascx pages (user controls) are processed by the .Net framework. Page directive The most commonly used directive is the @ Page directive and it can be used only in Web Forms. Page directive allows you to specify many configuration options for the page. By default, Visual Studio creates a page directive as shown below: 1 2 3 4 C # & lt ;% @ Page Language = "C#"  AutoEventWireup = "true"  CodeFile = "Default.aspx.cs"  Inherits = "_Default"   %& gt ; VB . NET & lt ;% @ Page Language = "VB"  AutoEventWireup = "false"  CodeFile = "Default.aspx.vb"  I...

An API Gateway can offer multiple features. Depending on the product it might offer richer or simpler features, however, the most important and foundational features for any API Gateway are the following design patterns. Reverse proxy or gateway routing.  The API Gateway offers a reverse proxy to re-direct or route requests (layer 7 routing, usually Http requests) to the endpoints of the internal microservices. The gateway provides a single endpoint or URL for the client apps and then internally maps the requests to a group of internal microservices. This routing feature helps to decouple the client apps from the microservices but it is also pretty convenient when modernizing a monolithic API by sitting the API Gateway in between the monolithic API and the client apps, then you can add new APIs as new microservices while still using the legacy monolithic API until it is split into many microservices in the future. Because of the API Gateway, the client apps won’t n...

In this article we are reading about  “What’s New in Dynamics 365 CRM V 9.0 ?” . Platform Separation : When Dynamics 365 launched, Microsoft signaled a move towards an app-centric platform to escape a bloated, monolithic model. This will be increasingly evident with the v9 release which sees Dynamics 365 break into modular apps that shift away from one platform with multiple modules hardwired in such as sales, marketing and service. By redefining the platform layer and breaking modules into role-based solutions for sales, finance & operations, customer service, talent, field service, to name just a few, it will remove the need to test all at once and upgrade everything in one big bang project. This will quicken release cycles and enable more rapid changes by allowing these to work independently of each other, but crucially these are connected with a common data service.  With apps frequently changing and able to upgrade independently of each other, several insiders...