Robin19's Profile User Rating: *****

Reputation: 271 Architect
Group:
Expert
Active Posts:
550 (0.36 per day)
Joined:
07-July 10
Profile Views:
8,684
Last Active:
User is offline Yesterday, 12:12 PM
Currently:
Offline

Previous Fields

Country:
US
OS Preference:
Windows
Favorite Browser:
Chrome
Favorite Processor:
Who Cares
Favorite Gaming Platform:
Who Cares
Your Car:
Who Cares
Dream Kudos:
100
Expert In:
C#

Latest Visitors

Icon   Robin19 has not set their status

Posts I've Made

  1. In Topic: Form gets locked up when connecting to database

    Posted 19 Aug 2014

    It is best to get into the habit to always do those things correctly the first time. There are too many times a developer (including me sometimes) will "clean it up later" and end up never going back to clean it up.

    It doesn't look like anyone explained why you are getting the freezing problem. When you click a button the UI thread runs the handler method. A thread can only do one thing at a time. It needs to wait until the handler method finishes before it can go on to handle other events like listening for any new mouse or button events. If you have a method that could take some time to finish your UI thread will wait the entire time. That is why you should push it off to a background worker/thread. If the task is going to take 100 ms, say create and run a worker thread, you can usually not care that the UI thread was frozen for that amount of time.
  2. In Topic: Methods and arguments

    Posted 4 Aug 2014

    Here's a "real world" example that I hope helps make it clearer for you.

    You have a car. You name it "herbie".
    Car herbie = new Car();
    herbie.Drive(me);
    

    Your car breaks down and you take it to the shop.
    localRepairShop.Fix(herbie);
    

    The repair shop fixes lots of cars. The mechanics don't keep track of each car name. They have a standard name for any car that pulls in.
    public void Fix(Car carInLift2)
    {
       carInLift2.FixEngine();
       carInLift2.CheckFluids();
    }
    

    When they got a car they always refer to it as carInLift2. So your car is still called herbie by you, but the shop calls it by a different name. Your herbie and their carInLift2 are the same. A week later when kitt comes in to be fixed it will also be called carInLift2 by the shop. Now your herbie and their carInLift2 are not the same. A different argument was passed to the method.
  3. In Topic: employers want many many skills just to do one job (advice?)

    Posted 31 Jul 2014

    I've seen postings asking for 20+ years experience of .NET development. I doubt they will find anyone with 20+ years experience in a technology 12 years old. This is usually the hiring manager saying they need a .NET developer and HR adding the 20+ years experience because anyone that was coding in 1994 is obviously good at coding today.
  4. In Topic: Asynchronous call from view

    Posted 18 Jul 2014

    An async method means the method will return later. This works well in a WPF environment like your tutorial. This doesn't work well when a web server is trying to deliver a page. Your web server needs to take the cshtml and turn it into a text file to deliver. That is the nature of the internet. The server has trouble doing that when the cshtml says "I'll get back to you". I can think of two ways around this.

    Put your async call in the controller. The controller will need to await the async function to finish. This syncronizes the function and could cause a time-out if the async call takes too long.

    Use AJAX. The A stands for Async, which kind of hints at this being a possible solution.
  5. In Topic: Who has worked with/written software that runs in automobiles?

    Posted 27 Jun 2014

    There is still a worry about effecting the engine stuff. The control systems all talk to each other. A coworker helped me jump my car last year. The first time he plugged it in he had it wrong. I started having odd behavior from the car a couple of months later. Things not running when they were supposed to or turning off for no reason, including the engine. It ended up that the lights controller had been fried and the bios was bad. That controller would misinterpret signals and send bad signals back though the bus. These signals would sometimes get interpreted by the other controllers to do something. The car repairman had to wipe the memory and re-install the factory image of six of them to get them talking to each other correctly.

My Information

Member Title:
D.I.C Addict
Age:
Age Unknown
Birthday:
June 15
Gender:
Programming Languages:
C#, Java, C++, VB.NET, WPF, XNA

Contact Information

E-mail:
Click here to e-mail me

Friends

Comments

Page 1 of 1
  1. Photo

    ni44ko Icon

    23 Nov 2010 - 19:19
    thanks. i want to be your apprentice.
Page 1 of 1