So .NET does some funny things sometimes. Mr. Hanselman has already explained what is going on in a little detail. I added a little something from this bytes.com post.

Seems like it will be the way to go!

string filePath = Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "Person.dll"
AssemblyName an = AssemblyName.GetAssemblyName(filePath);
Assembly dll = Assembly.Load(an);

Type t = dll.GetType("Plugin.Person");
var instance = t.InvokeMember(String.Empty,BindingFlags.CreateInstance, null, null, null);
Person p = (Person)instance;

Go straight to Post

Iz nice… works with multiple monitors to select the main screen.

public MainForm()
{
    InitializeComponent();

    Rectangle r = Screen.PrimaryScreen.WorkingArea;
    StartPosition = FormStartPosition.Manual;
    Location = new Point(Screen.PrimaryScreen.WorkingArea.Width - Width,
        Screen.PrimaryScreen.WorkingArea.Height - Height);
}

Go straight to Post

After discovering that my development machine was getting bogged down like you wouldn’t believe, I decided that I could trim some of the processes and services down. One of the biggest offenders was Sql. I don’t need to have sql running ALL the time. So why have it start when I log in?

I first created a few batch files using the net start and net stop commands. I then created this little app that will run in the system tray and read the contents of a folder and create a context menu item for each batch file. Then when I right click the icon in the tray and choose an entry it kicks off the selected batch file giving me quick access to start and stop my processes (or run any command or shortcut for that matter).

I am cleaning up the project and I will put a good clean build up here soon.

Download Batch Tools 1.0

Go straight to Post

© 2010 iDevelop Suffusion theme by Sayontan Sinha