Idea#3: Calendar Control with Exchange 2003 Backend

Now this is an idea that I am actually doing to try and develop over the next little while. What I think would be really cool is a calendar control similar to the one on the right that is created from data that comes from an Exchange calendar. It would also need the ability to drill down deeper and just show the appointments/events for a single day or list of days.

Read more

Idea#2: RunAsHelper

At the organization that I work for we are required to use under-privileged accounts for all tasks except where admin rights are necessary. For this we are to use the RunAs feature of windows. Now in the course of a day, especially if I am debugging or developing something, I often end up doing a RunAs and typing my username and password a dozen or so times. What would be really hand is an application that you can RunAs once which in turn is able to launch other processes when needed. Ideally it would live in the system tray and you could right-click to display a list of application that you can run with elevated credentials. You’d also want some means for the program to allow addition/deletion of programs and a portable way to store the list of applications.

This actually has a lot of potential because you could design it in such a way that would make it very modular. What I am thinking is this, create an Interface called ITask with definitions for a Run method. Then we can have different tasks implement this interface for say running programs or mapping a network drive, etc. As a minimum ITask would also want some properties for say Name and location/file or something like that. The the sky’s the limit! Keep a collection of ITask object that correspond to items in the menu and you’ve got yourself a handy little app! Any thoughts?

Read more

Idea#1: .net CDP Reader

I always have these idea that seem like they would be really useful and cool but just never have the time or knowledge to implement them. So why not blog about them and let some other smart dude with lots of time figure it all out.

My first idea is to have a small application that a user can fire up that will start monitoring there network connection. The program will ignore all data except cisco CDP packets. Once a packet is received then the program would be able to display what port of what switch the user is connected to. Now this might not seem immediately useful but we often find that it is useful to find out which port a user is plugged into which means having to go down a match up wall ports with switch ports. If you had a small program to do it then you’ve just saved yourself a trip. And it’d just be cool.

Read more