A few weeks ago, I’ve started my first solo .net project. It’s a issue management system with workflow functionality for keeping track of issues regarding to some projects of an IT company. These are the main requirements:
- Must control issues by project and customer.
- The users from the customers can only see the issues related to themselves (they can’t see all the issues from the project).
- Transition control: the system must do some tasks when the issues state change in a flexible manner. Eg.: when some issue status change from <any> to closed, the system must send an e-mail notification to the customer or user that created it.
- All issue information must be filtered for customers: they can’t see technical related information (this is important only for the tech staff), even in the system or e-mail notifications.
- And something more that justity the development of a customized system and don’t adopting a popular issue management system like BugZilla! or Scarab (the company was using this system before the new one).
There are two main objectives with this project: the first, I always wanted to develop a project that uses workflow concepts, and the second, I was wating for a chance to increase my .NET knowledge.
So, let’s see what happens!
Finding references in Visual Studio - an annoying problem « DevInstance said
[...] A good tool from Visual Studio 2005 is the “Find all references” in the context menu. However, it has a annoying behavior in a common situation within my project. [...]