Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From the sounds of it you have a opportunity during the "post-mortem"to present some solutions. I would create a presentation outlining your ideas and present them at this meeting. Before that I would recommend that you set up some solutions and demonstrate it during your presentation. Some things to do -</p> <ol> <li><p>Evangelize component based programming (A good read is <a href="http://rads.stackoverflow.com/amzn/click/0596102070" rel="nofollow noreferrer">Programming .NET Components - Jubal Lowy</a>). Advocate the DRY (Don't Repeat Yourself) principle of coding.</p></li> <li><p>Set up a central common location in you repository for all your re-usable code libraries. This should have the reference implementation of your re-usable code library.</p></li> <li><p>Make it easy for people to use your code libraries by providing project templates for common scenarios with the code libraries already baked in. This way your colleagues will have a consistent template to work from. You can leverage the VS.NET project template capabilities to this - check out the following links <a href="http://msdn.microsoft.com/hi-in/vsx/cc677252(en-us).aspx" rel="nofollow noreferrer">VSX Project System (VS.Net 2008)</a>, <a href="http://www.codeproject.com/KB/dotnet/krevera_template_manager.aspx" rel="nofollow noreferrer">Code Project article on creating Project Templates</a></p></li> <li><p>Use a build automation tool like MSBuild (which is bundled in VS2005 and up) to copy over just the components needed for a particular project. Make this part of your build setup in the IDE (VS.NET 2005 and up have nifty ways to set up pre-compile and post-compile tasks using MSBuild)</p></li> <li><p>I know there is resistance for open source solutions but I would still recommend setting up and using a continuous automation system like <a href="http://confluence.public.thoughtworks.org/display/CCNET/Welcome+to+CruiseControl.NET" rel="nofollow noreferrer">CruiseControl.NET</a> so that you can leverage it to compile and test your projects on a regular basis from a central repository where the re-usable code library is maintained. This way any changes to the code library can be quickly checked to make sure it does not break anything, It also helps bring out version issues with the various projects. </p></li> </ol> <p>If you can set this up on a machine and show it during your post-mortem as part of the steps that can be taken to improve, you should get better buy since you are showing something already working that can be scaled up easily.</p> <p>Hope this helps and best of luck with your evangelism :-) </p> <p>I came across this set of frameworks recently called the <a href="https://github.com/chucknorris" rel="nofollow noreferrer">Chuck Norris Frameworks</a> - They are available on NuGet at <a href="http://nuget.org/packages/chucknorris" rel="nofollow noreferrer">http://nuget.org/packages/chucknorris</a> . You should definitely check them out, as they have some nice templates for your ASP.NET projects. Also definitely checkout <a href="http://nuget.org/" rel="nofollow noreferrer">Nuget</a>.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload