<baseAddressPrefixFilters>

        <add prefix=https://www.myhost.com/ />

      </baseAddressPrefixFilters>

    </serviceHostingEnvironment>

Alvaro

Scenario: Tested my application and post that I decided (for some reasons not relevant here) to change the namespace of the classes in my silverlight project. As part of this, I changed the namespace of the App class in the App.xaml.cs file.

As soon as i ran the application again, it started giving me this error.

Solution: It turns out that when we change the namespace of the App class, the "Startup Object" in the project properties doesn't get updated causing this error. When we update this in the project properties it starts working fine again.

Regards,

Alvaro

the PEX team has released on online version of their unit testing tool at https://www.pexforfun.com/

I found this to be a real fun way to explore and understand how Test Driven Development is all about.

having said that, i'd like to add that PEX is much more than the above site. for more details on PEX, you can go to their main site @ https://research.microsoft.com/en-us/projects/pex/

Regards,

AlD

public class MyClass
{
    public int myField = 4;
 
    public MyClass()
    {
        this.myField = 5;
    }
}

 when we compile this class, we get an assembly with IL in it. The parameterless constructor gets converted into a method with the name .ctor

Now, if we see the IL that gets generated for this .ctor method, we might expect it to have IL opcodes to assign the value 5 to the myField field of the class. 

However, we can see that there is a lot more in there.

First of all, we see IL commands to assign the value 4 to myField, then the .ctor method of System.Object gets called. Finally, we see the code within the MyClass’s constructor.

When we write code to instantiate this class using the new operator (i.e. MyClass myObject = new MyClass();) the following things happen in the given order: -

1.       Execution of the initializers of all the class’s fields

2.       Execution of the class’s base class constructor

3.       Execution of the code within this class constructor

Let us create another class MyDerivedClass and derive it from MyClass as below. 

public class MyDerivedClass : MyClass
{
    public int myDerivedProperty = 6;
 
    public MyDerivedClass()
    {
        this.myDerivedProperty = 7;
    }
}

When we instantiate MyDerivedClass, by the same flow as earlier, the following things happen in order

1.       myDerivedProperty gets initialized to 6

2.       the constructor of MyClass gets called

a.       MyClass.myField gets initialized to 4

b.      The constructor of System.Object gets called

c.       MyClass.myField is assigned the value 5 due to the code in MyClass’s constructor

3.       myDerivedProperty is assigned the value 7 due to the code in MyDerivedClass’s constructor

Addendum
Thought, I'd the IL that gets generated for the constructor.
Looking at the C# code written in the constructor, we might expect to see code somethign like below
.method public hidebysig specialname rtspecialname 
        instance void  .ctor() cil managed
{
  // Code size       17 (0x11)
  .maxstack  8
  IL_0000:  ldarg.0
  IL_0001:  ldc.i4.7
  IL_0002:  stfld      int32 ConsoleApplication5.MyDerivedClass::myDerivedProperty
  IL_0007:  nop
  IL_0008:  ret
} // end of method MyDerivedClass::.ctor 
 However, what we see is something like below
.method public hidebysig specialname rtspecialname 
        instance void  .ctor() cil managed
{
  // Code size       24 (0x18)
  .maxstack  8
  IL_0000:  ldarg.0
  IL_0001:  ldc.i4.6
  IL_0002:  stfld      int32 ConsoleApplication5.MyDerivedClass::myDerivedProperty
  IL_0007:  ldarg.0
  IL_0008:  call       instance void ConsoleApplication5.MyClass::.ctor()
  IL_000d:  nop
  IL_000e:  nop
  IL_000f:  ldarg.0
  IL_0010:  ldc.i4.7
  IL_0011:  stfld      int32 ConsoleApplication5.MyDerivedClass::myDerivedProperty
  IL_0016:  nop
  IL_0017:  ret
} // end of method MyDerivedClass::.ctor
i.e. first the variable initializer gets executed, then the base constructor gets called and finally we have the IL corresponding to the C# code written in the class constructor
 

    class Program

    {

        static void Main(string[] args)

        {

            using (SqlConnection connection = new SqlConnection())

            {

                connection.Open();

                connection.Close();

            }

        }

    }

the IL that gets generated for the above program looks something like below...

        [0] class [System.Data]System.Data.SqlClient.SqlConnection connection)

    L_0000: ldnull

    L_0001: stloc.0

    L_0002: ldloc.0

    L_0003: callvirt instance void [System.Data]System.Data.Common.DbConnection::Open()

    L_0008: ldloc.0

    L_0009: callvirt instance void [System.Data]System.Data.Common.DbConnection::Close()

    L_000e: leave.s L_001a

    L_0010: ldloc.0

    L_0011: brfalse.s L_0019

    L_0013: ldloc.0

    L_0014: callvirt instance void [mscorlib]System.IDisposable::Dispose()

    L_0019: endfinally

    L_001a: ret

    .try L_0002 to L_0010 finally handler L_0010 to L_001a 

On analyzing this IL what we realize is that this code is nothing but syntactic sugar for the try-finally block shown below

SqlConnection connection = new SqlConnection();

try

{

    connection.Open();

    connection.Close();

}

finally

{

    if(connection != null)

        connection.Dispose();

} 

Overall a pretty neat feature to have...

Till my next post,

Regards,

AlD

1.       Enable port sharing by either adding an attribute in your code like below

Or by setting in the app.config like below=

2.       Enable and configure the Net Tcp Port Sharing Service – which involves the following

a.       Enable the Application Server role with the TCP Port Sharing selected

b.      Update the app.config for SmSvcHost.exe with the below config - https://msdn.microsoft.com/en-us/library/aa702669(VS.100).aspx **

c.       Restart the “Net.Tcp Port Sharing Service” from services.msc

** One GOTCHA:  Though the link says to go to “C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation”, for .NET 4, you would need to update the app.config in the below locations based on the bitness of the box and the .NET Build.

a.       C:\Windows\Microsoft.NET\Framework\v4.0.30128 ** for .NET 4 RC – x86 CPU

b.      C:\Windows\Microsoft.NET\Framework64\v4.0.30128 ** for .NET 4 RC – x64 CPU

You can confirm the correct location to update the app.config by going to services.msc and checking the executable path in the properties of the Net.Tcp Port Sharing Service.

Collection<DataEndpoint> myObjects = new Collection<DataEndpoint>();

var dataExtensions = from c in dataContext.ETDataExtensions

                     join d in dataContext.RequestTypeDatas on c.RequestTypeID equals d.RequestTypeID

                     where d.RequestType == requestType.ToString()

                     selectOrDo myObjects.Add(c);

Till my next post, adeus.

Regards,

AlD

Thread.Sleep(500);

SendKeys.SendWait("run");

Thread.Sleep(1000);

SendKeys.SendWait("{ENTER}");

Thread.Sleep(500);

String currentRecepients = "<your To List>";//Enter all emails separated by semi colons

SendKeys.SendWait("mailto:" + currentRecepients + ";";//+ WindowsIdentity.GetCurrent().Name.Split('\\')[1]);

Thread.Sleep(500);

SendKeys.SendWait("{ENTER}");

Thread.Sleep(500);

SendKeys.SendWait("treat from me at barista... today 4:30pm");

SendKeys.SendWait("{TAB}");

SendKeys.SendWait("no particular reason... just for the heck of it");

SendKeys.SendWait("%(s)");

What it does is pretty simple actually. It opens outlook and sends a mail from the guy running this code to the intended recepients.

Now how can you get your target user to run this code? Well, thats upto you to figure out.

Complements of the season,

Some time back I got thinking... everytime I start reading mails in the C# discussion alias at my company or Eric Lippert's explanations of why the supposedly peculiar behaviour is in fact logical... the first thing I do is open up my very extensively used "ExperimentalConsoleApplication" solution in Visual Studio, comment out the existing main function in the console app project for future reference and start writing a new one... and it is kind of a pain to do this.. so I thought that it's time to get it automated.. so I wrote a snippet to do that for me.

Below is the code for that: -

<?xml version="1.0" encoding="utf-8" ?> <CodeSnippets xmlns="https://schemas.microsoft.com/VisualStudio/2005/CodeSnippet">     <CodeSnippet Format="1.0.0">         <Header>             <Title>mainfn</Title>             <Shortcut>mainfn</Shortcut>             <Description>Code snippet for 'Main' function</Description>             <Author>Alvaro Rahul Dias</Author>             <SnippetTypes>                 <SnippetType>Expansion</SnippetType>                 <SnippetType>SurroundsWith</SnippetType>             </SnippetTypes>         </Header>         <Snippet>             <Declarations>                 <Literal>                     <ID>expression</ID>                     <ToolTip>Code in main method</ToolTip>                     <Default>Console.WriteLine("Hello World!");</Default>                 </Literal>             </Declarations>             <Code Language="csharp"><![CDATA[ public class MyClass             {                 public static void Main()                 {                     $expression$                     $selected$ $end$                 }             }]]>             </Code>         </Snippet>     </CodeSnippet> </CodeSnippets>

Most of the fields above are self explanatory. I'll explain a few important ones.
The <Shortcut> tag specifies what you need to type in VS to use this snippet.
<SnippetTypes> - where you can use this snippet, Expansion, Surround With or both.
<Code Language="csharp"> - the actual code to be inserted

Interesting thing to note is that all the variable items are marked with $ signs. The $selected$ attribute signifies where the selected code should go in case you use this code as a sorround with snippet.
The $end$ attribute signifies where the cursor should go once you're finished with the snippet.

Hope the above helps in your coding adventures.