Friday, July 20, 2012

Slow Visual Studio 2010

Visual Studio 2010 on Windows 7 is Running Extremely Slow.

A few days ago my Visual Studio (VS) was taking a long time to compile/run (F5) and then it took a long time to close an application. In previous VS versions I would correct the problem by Cleaning the Solution (menu: Build/Clean Solution) and Rebuild the Solution. However, this time this procedure did not fix the slow problem.


I queried the internet for “Slow Visual Studio 2010” and found the solution from this link  N3WJACK'S BLOG


Basically, the Windows 7 JumpList needed to be cleared as follows:

1. Right-click the Start button
2. Choose Properties
3. Uncheck both checkboxes under the Privacy group
4. Click the Apply button
5. Re-check both checkboxes
6. Press OK



Tuesday, May 22, 2012

Example Framework for Addressing Issues

Development and Testing Environment This is the Topic Title


MAXCON is modified and tested on the MAXCON production server. This is the Condition.



Some modifications to the existing applications can be problematic with unforeseen consequences and partially with unstable applications. This is the problem and example.



A MAXCON Development and Testing environment needs to be established to ensure modifications were implemented correctly and that no side effects have occurred. However production releases will require slightly more time than making changes directly on the production server. This is the Solution with Positives and Negatives.



We estimate that we need 10 hours to setup a Virtual Machine (VM) and run some initial test. This is the Level of Effort (LOF)



The text in italics is to explain the content and is not to be shown to the client.



It is important to be precise and clear. In other words, write as simple as possible. Additionally be consistent with nomenclatures, such as writing MAXCON in all upper-case. And always spell out abbreviations the first time mentioned in a document, for example: Virtual Machine (VM)



Also keep the associated Condition, Solution and LOF grouped together. And have a (Sub) Topic Header for each group.



Monday, May 21, 2012

Framework for Addressing Issues

A typical problem is communication between technologist (programmers, DBA, and etc.) and clients (typically managers). In that realization I developed a simple framework for breaking down the Area of Concern into elements. The goal was to ensure constancy with simplicity.

[Topic Title] Area of Concern

Situation  Describe association between Condition (state), Problem (issue) and Examples/Scenarios
        [What is the Condition?]


        [Why it is a Problem?]


        [Provide Examples and/or Scenarios]


Recommendations  Describe possible solution(s) with positives and negatives

          [Recommend Solution(s)]

          [Explain the Pros and Cons for each solution]


Schedule  Define estimated LOF within a timeframe

          [Provide Level of Effort (LOF)]

          [Suggest a Time Line if practical – Reference each Solution]