Maybe one of you guru's out there can help me with this one. I am in need of creating a new list definition that has all of the core functionality found in an issues list. This is one list type that I have not extended in the past and find there is a lot of base code. What I don't understand is where and how SP brings list specific and base code together; which I can duplicate in a custom list definition as a starting point. Once I have a base custom list definition with all of the features of an issues list (history is the key), I can take it from there. Anyone care to shed some light on this for me?
About bmixon
I have been working in the technology industry since the early 1980's. I started my career with goals of designing circuits and computers but quickly learned I had a gift for software development. I spent the first 7 years writing software for embedded systems in the robotics industry. Afterwords I moved into applying technology to solve business problems; I have been doing so ever since.
I am currently the principal owner of Mixon Consulting, providing training and technology solutions for SharePoint, Collaboration, Intranets, Extranets, eBusiness, Knowledge Management and Business Process Management (BPM).
I have extensive skills with design, architecture and the implementation of Windows SharePoint Services (WSS) 2003, SharePoint Portal Server (SPS) 2003, Windows SharePoint Services (WSS) v3, Microsoft Office SharePoint Server (MOSS) 2007 and related Microsoft Client/Server technologies. Other core technical competencies include development experience in C/C++, C#, .NET, ASP.NET, Web Services, Windows Workflow Foundation, MSMQ, and other leading Microsoft developer platforms/technologies.
In January 2007, I was honored with my second annual Microsoft Most Valuable Professional (MVP) award for my continued efforts and dedication to growing and helping the SharePoint community.
More on:
www.BobMixon.com/about