Many of you may know about the context menu item Set Next Statement (Ctrl+Shift+F10) that moves the yellow arrow (the instruction pointer) to the target line of code. You may also know that you grab and drag the yellow arrow up and down in the gutter to move it. What you probably didn’t know is that as of Visual Studio 2017 version 15,3 Preview there is an even easier way to target a line and Set Next Statement.
1. Hover over the line of code where you want to move the yellow arrow.
2. Hold the CTRL key and notice the Run to Click (Run execution to here) glyph changes into the Set Next Statement glyph.
3. Click on that glyph and the yellow arrow will move to that line.
4. This line will be the next statement to execute when taking a step or pressing Continue (F5).
I know it’s against all logic and mathematical probability, but I find it hard to trust the uniqueness of GUID’s!
When dealing with a Cloud Architecture the ability to scale out becomes available by adding computational resources to process job queues. The application’s work load is divided across a number of servers who each process a job or set of jobs retrieved from a queue.
What you lose in the power earned from Classic Architecture you gain in power though parallelism and cost saving through flexibility in Cloud Architecture. In Cloud Architecture, when more resources are needed more servers are added and when demand has been met and those resources are no longer needed they are removed.
This type of resource management is powerfully meaningful from a cost perspective when the process of scaling out and back is automated.
Classic Applications are usually comprised of three core components. The Web Application, a Document Storage System, and a Database System. In the Classic Application Architecture model these components are distributed across one or more servers.
When resources become maxed out on these servers new hardware must be added to meet the demand. This is called Scaling up because you scale up your hardware’s specification to meet the demands of your application’s requirements and will probably lead to big servers, slow servers, or high maintenance costs, so it’s not very flexible or efficient from a resource management perspective.
But this is fine actually because this resource management model is perfectly well suited to clients who can accurately predict their usage of an application and have adequate resources to hand.
SQL Server reporting services (SSRS) is a suite of tools made available by Microsoft as an alternative to Crystal Reports and as an optional component of SQL server. Reports are created using a Visual Studio component or other Client Report Definition (RDLC) designer such as Report Builder. Reports are published to a central store to be viewed, manipulated and exported to a variety of formats. SSRS needs to be enabled and configured before reports can be published to its report hosting web application.
The following resources should give a good overview and starting point for anyone planning on building RDLC Reports
SQL Server Reporting Services Overview (4:57)
SQL 2012 Report Builder -> for designing and publishing reports -> uses the familiar MS Office interface.
SQL 2012 Report Builder Tutorial -> (11:59)
There is also an addin available for Excel called “Power Query” that allows for the easy aggregation of basic data from SQL, a user can then use the Excel components that they are already familiar with to create reports.
Power Query > Excel Addin for creating Excel reports
If you want to do some simple iteration for non essential tasks and you don’t care about the iteration index, you can do the following in c#
foreach (int i in new int)
When writing a limitation into an application, say for a maximum file size allowed for an upload, always set the actual limitation to a little above the reported one. People like to exceed their limitations. Why not let them?!