http://www.thescarms.com/dotnet/ExcelObject.aspx

http://support.microsoft.com/kb/302084/EN-US/

Connector/Net 6.0 http://dev.mysql.com/downloads/connector/net/6.0.html

DBLinq http://code2code.net/DB_Linq/

http://stackoverflow.com/questions/76488/using-mysql-with-entity-framework

http://www.mysql.com/news-and-events/on-demand-webinars/display-od-204.html

Using MySQL with Entity Framework and ASP.NET MVC  http://pattersonc.com/blog/index.php/2009/04/01/using-mysql-with-entity-framework-and-aspnet-mvc-%E2%80%93-part-i/ http://pattersonc.com/blog/index.php/2009/04/20/using-mysql-with-entity-framework-and-aspnet-mvc-part-ii/

Home http://expression.microsoft.com/en-us/default.aspx

Expression Design tutorial http://www.lynda.com/home/DisplayCourse.aspx?lpk2=339

Integrating 3D into Expression Blend with ZAM 3D http://expression.microsoft.com/en-us/dd567847.aspx

(From http://mikehadlow.blogspot.com/2009/05/what-i-look-for-in-code-review.html)

 

I recently put this bullet point list together for the team I’m currently working with.

Naming Conventions

• Naming conventions. We will follow Microsoft’s standard C# naming conventions. http://blogs.msdn.com/brada/articles/361363.aspx. Ignore the bit about putting using statements inside the namespace declaration.

General Principles

• The core imperative is to organise complexity.
• Clarity and readability is central. “Intention Revealing”
• Do not prematurely optimise for performance.
• Do not repeat yourself. Never copy-and-paste code.
• Decouple.
• Always try to leave the code you work on in a better state than before you started (the ‘boy scout’ principle)

Keep the source clean

• Always delete unused code. Including variables and using statements
• Don’t comment out code, delete it. We have source control to manage change.

Naming things

• The name should accurately describe what the thing does.
• Do not use shortenings, only use well understood abbreviations.
• If the name looks awkward, the code is probably awkward.

Namespaces

• Namespaces should match the project name + path inside the project. This is what VS will give you by default.
• Classes that together provide similar functions should be grouped in a single namespace.
• Avoid namespace dependency cycles.

Variables

• Use constants where possible. Avoid magic strings.
• Use readonly where possible
• Avoid many temporary variables.
• Never use a single variable for two different puposes.
• Keep scope as narrow as possible. (declaration close to use)

Methods

• The name should accurately describe what the method does.
• It should only do one thing.
• It should be small (more than 10 lines of code is questionable).
• The number of parameters should be small.
• Public methods should validate all parameters.
• Assert expectations and throw an appropriate error if invalid.
• Avoid deep nesting of loops and conditionals. (Cyclomatic complexity).

Classes

• The name should accurately describe what the class does.
• Classes typically represent data or services, be clear which your class is.
• Design your object oriented schema deliberately.
• A class should be small.
• A class should have one responsibility only.
• A class should have a clear contract.
• A class should be decoupled from its dependencies.
• Favour composition over inheritance.
• Avoid static classes and methods.
• Make the class immutable if possible.

Interfaces

• Rely on interfaces rather than concrete classes wherever possible.
• An interface is a contract for interaction.
• An interface should have a single purpose (ISP)

Tests

• All code should have unit tests if possible.
• Test code should have the same quality as production code.
• Write code test-first wherever possible.

Error Handling

• Only wrap code with a try..catch statement if you are expecting it to throw a specific exception.
• Unexpected errors should only be handled at process boundaries.
• Never ‘bury’ exceptions.

http://www.wpftutorial.net/WPFIntroduction.html

http://marlongrech.wordpress.com/2008/12/13/attachedcommandbehavior-v2-aka-acb/

2 new features

- Support for Collection of binding to commands
- Support for Light weight Commands or as I call them Action

http://www.ageektrapped.com/blog/staticresource-does-not-mean-static/

http://wpfwonderland.wordpress.com/2007/08/11/mixing-external-mergeddictionaries-with-local-resources-in-appxaml/

Adding local application resources

Even though it is easy to add external resources it’s likely that you’ll want to have a style or other resource that you don’t intend to shared across applications.  You could isolated these resources within a single page (Page.Resources) or element (DockPanel.Resources)  But what if you want to add  them to <Application.Resources> tag?  You can do it as long as you know the correct location. They have to go between the </ResourceDictionary.MergedDictionaries> and </ResourceDictionary> tags.

    <Application.Resources>
      <ResourceDictionary>
        <ResourceDictionary.MergedDictionaries>
          <ResourceDictionary Source="WorkshopHelpers/MainResources.xaml"/>
        </ResourceDictionary.MergedDictionaries>
        <!-- Place here...-->
        <Style TargetType="Rectangle" >
          <Setter Property="Width" Value="100"/>
          <Setter Property="Height" Value="80"/>
        </Style>
      </ResourceDictionary>
    </Application.Resources>
  </Application>

-Walt Ritscher

  1: m_DispatcherTimer = new DispatcherTimer()
  2: {
  3: Interval = TimeSpan.FromSeconds(0.25),
  4: IsEnabled = true
  5: };
  6: 
  7: m_DispatcherTimer.Tick += delegate
  8: {
  9: CommandManager.InvalidateRequerySuggested();
 10: };
 11: 

http://robburke.net/2008/04/23/wpf-command-pattern-when-does-it-query-canexecute/

http://blog.schuager.com/2009/01/line-count-in-visual-studio.html

Select Edit -> Find & Replace -> Find in files... or just press CTRL+SHIFT+F
Check Use and select Regular expressions.
Type the following as the text to find:

^~(:Wh@//.+)~(:Wh@\{:Wh@)~(:Wh@\}:Wh@)~(:Wh@/#).+

Select where you want to do the search/count: file, project or solution.

http://www.hardcodet.net/2009/01/combinding-wpf-validation-rules-and-idataerrorinfo-to-validate-conversion-errors

Related:

http://karlshifflett.wordpress.com/mvvm/input-validation-ui-exceptions-model-validation-errors/

http://www.hardcodet.net/2008/04/wpf-custom-binding-class

http://joshsmithonwpf.wordpress.com/2008/11/14/using-a-viewmodel-to-provide-meaningful-validation-error-messages/

 

http://blogs.msdn.com/wpfsdk/archive/2007/01/16/someone-s-been-sitting-in-my-chair-property-changed-detection-mechanisms-in-wpf.aspx

Part1: http://blogs.msdn.com/wpfsdk/archive/2007/03/16/how-do-i-programmatically-interact-with-template-generated-elements-part-i.aspx

part2: http://blogs.msdn.com/wpfsdk/archive/2007/04/16/how-do-i-programmatically-interact-with-template-generated-elements-part-ii.aspx

http://www.xamltemplates.net/

http://www.nukeation.com/

Listing on Price Comparison Site http://paler.com/listing_on_price_comparison_sites.html

Google Base Help http://base.google.com/support/bin/answer.py?hl=en_US&answer=73932

CPC Strategy http://www.cpcstrategy.com/cses.html

OsCommerce Shopping.com Data Feed (Feature Set)http://www.magneticone.com/store/osCommerce.Modules/osCommerce.shopping..com.Data.Feed     http://www.magneticone.com/store/osCommerce.Modules/osCommerce.Data.Feeds