Html.DropDownFor Alternative:

<select>
<%
foreach (var Order in Model.Orders)
{
%>
<option value="<%: Order.Id%>"><%: Order.OrderName%></option>
<%
}
%>
</select>

This is the easiest way to add or change the attributes of  TextBoxFor Html helper.
I was attempting to change the type from "text" to "email" so the IPhone would detect this field as an email adress.

And so it begins.  My epic journey into the Microsoft Model View Controller.  This is not new technology,  other languages (see Ruby on rails) have used this model for a while,  and now Microsoft has adopted it in the new ASP.NET 4.0 Frame work.

Browser sends a request Controller. 
The Controller the processes the URL request. 
Control is then sent to the Model, asks the model for information probably from a database.
Once the Model has finished it's work it sends control back to the Controller. 
The Controller can then go back to the Model if it needs to, doing as much work as it needs before it finally renders the View.
The view is contructed using the data passed from the Model by the controller back to the User.

 jquery value in and value out

  $('#ControlID').val(“This is the string to set”); 

alert($('#ControlID').val());   

C#  CodeControl1.Text = Control2.Text;  

jquery Equivlent$('#ControlID1').val($('#ControlID2').val())); 

public Hashtable searchHash = new Hashtable();
System.Reflection.FieldInfo[] fields = [myStructName].GetType().GetFields();
foreach (System.Reflection.FieldInfo field in fields)
{
searchHash.Add(field.GetValue([myStructName]).ToString(), "|");
}

Great book by Eric Evens discussing the domain driven approach to software design.

Finishing up this book...a book review will be comming soon...

What does all that nerd lingo mean?

Basically I have some data I need to take out of the database and pass it to another server for processing in a service oriented architecture.
When this remote process is complete it will pass me back the results that I will save in the database.
The transport mechanism we will use is WCF or windows communication foundation.  To use this on the client side, which happens to be a database process. We will create a proxy class.
SQL SSIS is SQL Server's new DTS on steroids performance enhanced DTS. SSIS allows scripting in VB.net only (don't ask), and to use outside compiled dll's you have to register them in the Global Assembly Cache with a strong name, this is just a fancy way of making sure your dll's are unique.
This will happen on a timed interval.  Seams pretty simple huh?

In order to leverage windows communication foundation within SQL Server SSIS there are a number of things you have to do to make this happen. 

Build your client proxy WCF service model bindings from WCF service.

1. Build an assembly that will wrap the logic for your WCF call.
2. Sign the assembly with a strong name. (sn.exe or VS IDE).
3. GAC your new assembly on the SQL box by copying into C:\WINDOWS\assembly.
4. Merge your proxy app settings into DtsDebugHost.exe.config and DTExec.exe.config.
5. Welding in custom assemblies in SSIS with configuration variables.

 Make sure your dll is GAC'ed and refernced in your SSIS script project.

 Make sure your dll is added to your Package.dtsx.

This particular feature will get ya ! if your not aware of it.

When using the SvcUtil.exe and specifying shared collectionTypes;

The expression in the collectionType switch for a shared collection is followed by a back quote (`) and a 1.
For generic types, you must specify the number of generic parameters with a back quote followed by the number of generic parameters.
Do not confuse the back quote (`) with the single quote (').

"c:\Program Files\Microsoft SDKs\Windows\v6.0\Bin\SvcUtil"
      /language:cs
      /out:ServiceClient.cs 
      /namespace:*,ShareTypes.Client
      /noconfig
      /reference:..\ShareTypes.Common1\bin\Debug\ShareTypes.Common1.dll
      /reference:..\ShareTypes.Common2\bin\Debug\ShareTypes.Common2.dll
      /collectionType:ShareTypes.Common.SharedCollection1
      /collectionType:ShareTypes.Common.SharedCollection2`1
      net.tcp://localhost:9042/Service/mex

Great article here on this topic...

http://www.codeproject.com/KB/WCF/WCFCollectionTypeSharing.aspx

If you download zipped up Visual Studio project files and extract them with out Unblocking the zip file first, you will get an error.

Right click on the zip and Unblock -> press apply before extracting.

Speaking of untrusted zones ....

Coming soon...

learning Object Oriented Programming...

      OR

OOP ! I did it again !!! - A lesson in object cloning...

At the end you will be able to snatch the pebble from my hand...

You down with  OOP ! - Yeah You Know Me !!!

The ability to access a member in the global namespace is useful when

the member might be hidden by another entity of the same name.

In this example, the namespace System is used to include the class TestClass therefore, global::System.Console must be used to reference the System.Console class, which is hidden by the System namespace. Also, the alias mcLovin is used to refer to the namespace System.Collections; therefore, the instance of a System.Collections..::.Hashtable was created using this alias instead of the namespace.

Thread t = new Thread (...);

t.SetApartmentState (ApartmentState.STA);

class Program {

  [STAThread]

  static void Main() {

  ...

• it will marshal over to a single-threaded apartment
• it will crumble and fail.

Need more cow bells ?

Except for the guys that work at a R&D software think-tank most of us have a business need that drives our software development, which in turn drives our paychecks.

To turn your back on business value is to bite the hand that feeds you.

Remember middle managment needs to look important also !!!

 This is a simple example of how to wrap your LINQ db.DataContext SubmitChanges() in a Transaction.

This is much like using transaction in SQL Server.

I used a simple add function to outline the pattern to use when wrapping your LINQ commits in transactions.

*Add a ref to System.Transactions;

New LINQ the home verion. now you and your friends can play "Map that Relational Object" on a Friday Night !!!

* Some assembily required.

   (database not included)

  using System.Transactions;

 Welding in custom assemblies in SSIS with configuration variables. 

(I will pop a GAC in your CACHE !!!!)

Pre-requisites

SQL Server 2005 (including SSIS), Microsoft Visual Studio 2005 / 2008, .NET Framework v2.0-3.5

Prep the Assembly

Adding a reference to the Assembly in SSIS script designer

 Intuitively one would think your next step is to open your SSIS script editor and within your project explorer simply add a reference to your newly GAC’ed assembly.  However when you right click on References -> Add Reference and browse the list of available assemblies - yours is not there.I will not spend time trying to explain the intricacies of why this is, instead I will focus on how to get your .dll registered so you can get up and working.  The bottom line is your going to have to modify the Package.dtsx manually edit the *.dtsx script file to add additional paths to look for your defined assemblies. For example:  Open the file and first search for “<Build>”.

Add yours to the end of the ReferencePath attribute. 

<Build>         
ReferencePath = "C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ScriptTask\9.0.242.0__89845dcd8080cc91\;
C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ManagedDTS\9.0.242.0__89845dcd8080cc91\;
C:\WINDOWS\assembly\GAC_MSIL\ myAssembly \1.0.0.0__5d6caf3fc6396ac3\"

Then you can define you assemblies in the References Tags a little further down: 

<References>           
<Reference Name=" myAssembly " AssemblyName=" myAssembly " /> 
            *Next time you fire up the script in Visual Studio of Applications it will be referencing Next Search for “<References>”.  

<References>               
            <Reference Name = "myAssembly" AssemblyName = " myAssembly "/> 
</References>

Using a configuration varibles.

LINQ Books

Books on LINQ

LINQ in Action by Fabrice Marguerie, Steve Eichert, Jim Wooley, and Matt Warren

Pro LINQ: Language Integrated Query in C# 2008 by Joseph C. Rattz

Professional LINQ (Programmer to Programmer) by Scott Klein

LINQ Quickly by Satheesh, N Kumar

LINQ for VB 2005 by Fabio Claudio Ferracchiati

Books that Feature LINQ

C# 3.0 in a Nutshell: A Desktop Quick Reference by Joseph Albahari

Pro C# 2008 and the .NET 3.5 Platform, Fourth Edition (Pro Series) by Andrew Troelsen

C# 3.0 Cookbook by Jay Hilyard and Stephen Teilhet

Pro ASP.NET 3.5 in C# 2008, Second Edition by Matthew MacDonald and Mario Szpuszta

ASP.NET 3.5 Unleashed by Stephen Walther (Hardcover - Jan 7, 2008)