My First Post      My Facebook Profile      My MeOnShow Profile      W3LC Facebook Page      Learners Consortium Group      Job Portal      Shopping

Thursday, July 12, 2018

ThisChapter.Close() in long debates is good. Personal relations are important to keep that political discourse

And, we all know that well - Politicians are for none. Doesn't matter you support or oppose. If it's your turn you will get the bruise.

Anyways, I propose an algorithm to end the long debates. When you see that no fruitful is happening, you can end the thread. But please do remember to end any traces of hate that popped up in between. See below:

catch( exception hate)

Enjoy the life.

Yahoo Messenger Going down on 17th July 2018. An emotional letter by a fan remembering the golden era that now comes to an end.

Dear Yahoo,

Yahoo messenger was one of the first as well as the finest chat application. Chatting, to the most of our generation, started from Yahoo messenger in the public domain. Private chats as well as the chat rooms, were all a world of fantasy that soon became the world we lived in.

It's a sad news that Yahoo Messenger will no longer be supported after July 17, 2018. However, I do believe changes do happen. And, are essential to keep the river flowing. But trust me, the heart is heavy as if someone very own is going far far away.

The messenger has been a part of my childhood and of millions like me. It has supported me from contacting guys for studies as well as chatting late hours with my girlfriend. And, who could ever forget that chats with unknowns beginning with the all new discovered slangs like "a/s/l please" and frequently supplemented with the cool additions to our vocabulary like "brb", "lol" and "imo" etc. It has also been the only support in my long distance relationship with my ex.

I pretty much remember everything. Those were the days before Orkut, MySpace, Facebook, Watsapp, Hike or anything. The free chatrooms with multiple people checking in and leaving was an experience  out of the box. We have developed sincere and full-fledged virtual relationships with someone we never met. Sometimes, we waited for hours at odd hours for people to check-in the chat room. And, sometimes we just waited for hours before sending that first 'hi' to our crushes. Looks like some most cherished memories circle around Yahoo Messenger!

I’ve loved using the tool and want to thank you Yahoo for bringing such a product for us. I know that you will continue to focus on building and introducing new, exciting communication tools that impact and delight your users. 

Thanks for being a part of my life for so many years.

Thanks and regards,
Anwar Jamal Faiz

** To my blog readers: Before July 17, you can continue to use the service, but after that date, you will no longer have access to Yahoo Messenger. You can learn how to save your chats by visiting this FAQ page of Yahoo.

Wednesday, July 11, 2018

Cannot Start Microsoft Outlook. Invalid XML, the View Cannot be Loaded

One way your Outlook blocks you from accessing emails is when it Cannot Start Microsoft Outlook. Invalid XML, the View Cannot be Loaded" Error Message. The cause is also simple and more is its fix.

Follow the following steps below to clear and regenerate your Navigation Pane if you receive an error message that says "Cannot start Microsoft Outlook. Cannot open the Outlook window. Invalid XML, the view cannot be loaded."


When opening Microsoft Outlook Windows client, you receive the following error:

"Cannot start Microsoft Outlook. Cannot open the Outlook window. Invalid XML, the view cannot be loaded."

Opening Outlook in SAFE mode does not help, nor can this problem fixed by running repair or even by re-installing Outlook.

To fix this error, run the Outlook.exe  /ResetNavPane command:

Where to run:
Hold the Windows key and the R key at the same time.
The Run command window will open. Copy Outlook.exe  /ResetNavPane into the text field.
Click OK to run the command.

What happens:
Running this command clears and regenerates the Navigation Pane for the current profile, removing all shortcuts and favorite folders from the Navigation Pane.

Its time for a cheers ;)

Friday, June 29, 2018

Null conditional operator : Question mark (?) before Variable

One of the reader recently asked about the new kind of operator that we use in C# 6.0. He noticed that in the VS - 2015, there is a use of new operator as following. And, he wanted about what it is:
Eg: public class A {
   string method1 { get; set; }
var a = new A();
var foo = "anwar";
if(a?.method1 != foo) {

So, let me explain this brief concept!

It's the null conditional operator. It basically means to evaluate the first operand. If that is null, stop, with a result of null. If not, evaluate the second operand as a member of the first operand.

In the above example, the point is that if a is null, then a?.method1() will evaluate to null rather than throwing an exception.  It will then compare that null reference with foo, using string class overload, and find that they are not equal and execution will go into the body of the if statement.

In addition, it can be very useful when flattening a hierarchy and/or mapping objects. iEg, Instead of:

if (Model.Model2 == null
  || Model.Model2.Model3 == null
  || Model.Model2.Model3.Model4 == null
  || Model.Model2.Model3.Model4.Name == null)
  mapped.Name = "default"
  mapped.Name = Model.Model2.Model3.Model4.Name;
It can be written like (same logic as above)

mapped.Name = Model.Model2?.Model3?.Model4?.Name ?? "default";

So, with this I end. Go, grab a cuppa coffee. I will still do Cheers :)

Thursday, May 24, 2018

How to Load Test APIs: Methods and most effective way to test web or downstream services

There are three typical approaches to load testing an API. These, as well as various hybrids, each have drawbacks and advantages.

#1 Faking it – API Mocking

The least useful for load testing is API Mocking These are basically temporary placeholders used during development of an API. Developers use these for early unit testing. But they also provide these “dummy” versions to other teams that need to call the unfinished API from within their own code.
Mocks return hard-coded responses, the formats of which often change during development. Also, the effort to create the mocks is wasted after their initial use.
Remember that, mocks aren’t yet hooked up to actual data sources, their performance isn’t at all representative of the real world. In summary, mocks may be useful for unit testing, but they aren’t representative of the real world.

#2 Cloning it – A Full Test Environment

This approach stands up a full-blown test environment using a snapshot of production data. disadvantages-of-cloned-environmentsOften you’ll have a copy of all the applications running, too, because your code relies on other APIs, not just database queries.
The good in this approach is that it’s very representative of the live system’s performance. If your load test brings the system to its knees, no problem! It hurts no one.
However, they raise privacy concerns, require constant data reloading, and can be very expensive if calling third party APIs.

#3 Hitting production – Load Testing Live APIs

Sadly, the method so many companies use is to test on production itself. Why? Well, it’s live, so it’s the most representative of all methods. It’s also “easy” –  no separate test environment to stand up and maintain. 
Disadvantage is that all data created are actual and stateful. And you still have to worry about the cost of pay-per-use APIs.
It’s important to schedule your load test “off hours.” And, any break would cause your production to become down.

#4 API Virtualization – The Risk-free Approach

You want to perform an exhaustive load test of your API – and keep your existing customers and your job. That rules out hitting the production system. And, you also need more than a test version of your API in a cloned environment. You need to test the real API in an environment where you can control the load condition for aspect of the test.
That’s where API Virtualization comes in. A virtual API provides a sandbox environment where you can simulate environmental loads on network bandwidth, server and database connections, simultaneous users and more.
With API virtualization, minimal resources are required for standing up and testing the API. You test the API itself, not the end-to-end application with all its required backend systems.  This eliminates the need for a clone of the production environment. 
You can test your API in isolation, gauging the reaction against real data,  under a variety of load conditions. 
API Virtualization allows you to load test your API in isolation from the rest of the system. With complete control of the test conditions, you can simulate network load, maximum connection limits, latencies and other conditions that happen in the real world.