What it is A web application developed based on the responsive web design concept will adopt the layout of the application based on the screen size and orientation. As the user switches from their laptop to iPad, the website should automatically switch to accommodate for resolution, image size and scripting abilities. In other words, the website should have the technology to automatically respond to the user’s preferences. This would eliminate the need for a different design and development phase for each new gadget on the market. When designing a web in responsive manner same HTML content will be maintained, but it will be viewed in different layouts when user switches among different browser sizes. In that way website can server the users by changing the layout of the content so user can view it in more user friendly manner, without too many scrolling. How the layout changes will be discussed under topic Design patterns Pros Increasing your reach to tablet and ...
WCF 4.5 supports contract first development. Means it allows to create all the data contract classes can be auto generated using the WSDL. one of the advantage in using the is if we start developing the service from the data contracts & then generating the WSDL we might end up in creating from data contracts with .net specific data types. But when using contract first development as WSDL is xml based only xml based data types are allowed to create so no .net specific contract will be created. This feature can be very useful when WSDL file is produced through design phase either by a solution architect or through mutual parties that agree on a contract prior to development and build phases. When this is the case, either the contract can be created for a future service implementation or contracts can be created so that developers can begin coding for the client side of an interface prior to the endpoint being available. The contract-first tool is integrated into Visual Studio 2...
Fan In Fan out is one of the main usages of Azure Durable Functions Fan-out/fan-in refers to the pattern of executing multiple functions in parallel, and then waiting for all to finish. Often some aggregation work is done on results returned from the functions. Let’s see how to achieve this pattern using Azure Durable Functions. If this is the first time you creating a durable function please follow my post Here , it will have the steps on how to create a durable function and activity functions. Problem to solve: You have to generate a invoice for a customer, which should include around 20 orders. So First you need to calculate the order amounts for each order then generate the complete invoice. let’s see how to solve this using Azure durable functions Fan In Fan Out Patten Step 1: Add two Activity Functions for orderCalculation & InvoiceGenerations public class OrderCalculationActivity { [FunctionName("OrderCalculationActivity")] ...
Comments
Post a Comment